The playbook
Core Web Vitals: Checklist
Use this Core Web Vitals checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect field experience by page group. Check an actual page or query record; a box marked complete without evidence does not show that the customer journey works.
Put the task in context
Largest Contentful Paint concerns loading the main visible content, Interaction to Next Paint concerns responsiveness, and Cumulative Layout Shift concerns visual stability. Investigate the responsible element or interaction. Use field observations for real-user conditions and laboratory tests to diagnose particular changes.
Before you use the checklist
Name the exact item being checked and its purpose. Gather template, metric, field period, change. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Review field data separately from laboratory tests | A dated observation showing how template was verified | SEO lead |
| Find the page elements contributing to poor experiences | A dated observation showing how metric was verified | content or development owner |
| Test focused changes without breaking functionality | A dated observation showing how field period was verified | analytics owner |
Check the failure path
- Look specifically for this failure: treating a single lab score as a complete user-experience measure.
- Compare representative field results and functional checks over time. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check change.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Review field data separately from laboratory tests,” a meeting about the subject is not the evidence itself. Retain the relevant template and metric, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents evaluate real-user loading responsiveness and visual stability on important page types deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow field experience by page group using a consistent definition so later reviews can connect execution quality with useful results.
Keep page purpose visible throughout the work. A technically valid page can still fail to answer the reader’s question. Separate access and discovery problems from content problems so that the assigned action matches the cause.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now