Core Web Vitals and Headless Rendering SEO Checklist

Role: Principal Technical SEO Engineer & Web Performance Architect

Context

• Primary web framework: {{framework_stack}}
• Rendering configuration: {{rendering_strategy}}
• Target search engine bots: {{target_crawlers}}
• Strict performance budget: {{performance_budget_ms}}
• Observed LCP and layout shift issues: {{current_lcp_issues}}
• Edge and data caching layer: {{api_endpoint_caching}}

Task

Generate an exhaustive, audit-ready technical SEO checklist to identify, debug, and eliminate client-side rendering failures, hydration mismatches, and Core Web Vitals regressions across our software engineering platform.

Method

1. Analyze {{framework_stack}} against {{rendering_strategy}} to identify differences between the raw server-rendered HTML and client-side hydrated DOM.
2. Formulate specific test items verifying that critical metadata, canonical tags, and structured data render without executing post-hydration client scripts.
3. Establish audit steps for critical rendering path metrics (LCP, INP, CLS) based on the {{performance_budget_ms}} threshold.
4. Design verification checks to isolate DOM mutation causes identified in {{current_lcp_issues}}.
5. Construct validation steps for crawler-specific user-agent headers targeting {{target_crawlers}}.
6. Detail edge validation items to verify that {{api_endpoint_caching}} serves consistent cache-control and surrogate headers to bots.
7. Prioritize all checklist action items by rendering risk level and engineering implementation complexity.

Constraints

• Every checklist item MUST include a precise technical validation mechanism (e.g., specific CLI command, DevTools panel, or HTTP header assertion).
• MUST NOT provide generic marketing recommendations like "optimize images" without referencing specific compression formats, DOM attributes, or fetch priorities.
• All performance thresholds MUST align strictly with {{performance_budget_ms}}.
• Must distinguish between bot-only prerendering risks and end-user hydration penalties.

Output format

Provide a markdown checklist formatted into 4 distinct phases:

1. Server-Side Rendering & Hydration Parity (5-7 actionable check items)
2. Core Web Vitals & Asset Delivery Pipeline (5-7 actionable check items)
3. Edge Caching & Bot Delivery Integrity (4-6 actionable check items)
4. Post-Deployment Verification Commands (3-5 cURL or Node CLI commands) Each checklist item must follow this format: - [ ] **[Component]** Action statement | *Verification:* Technical verification method | *Severity:* [P0/P1/P2].

Self-review

• Ensure all 6 context variables are explicitly referenced and integrated into the technical logic.
• Verify that hydration and rendering checks are technically feasible within {{framework_stack}}.
• Confirm that no placeholder text or vague guidance exists in verification methods.