Help & Documentation
Browse the full documentation index · Press Esc to close
Cross-signal

CTR Opportunities × Web Vitals

Stops you over-attributing CTR drops to copy when the landing page experience is the real culprit. The CTR Opportunities report tells you to rewrite the title. This report tells you whether that's actually the right fix.

Why it matters

A page-1 query with weak CTR usually triggers a "rewrite the title" recommendation. But if the landing page is failing Core Web Vitals, real users may be tapping the result, hitting a slow / janky page and bouncing — which Google increasingly factors into ranking and snippet selection. Rewriting the title alone won't recover that traffic; the page experience is the bottleneck.

How it's built

  1. Take the standard CTR Opportunities cohort — page-1 queries (avg position ≤ 10) with at least 100 impressions and CTR < 1%.
  2. Join each query to its top landing URL via the 90-day query × page snapshot.
  3. Look up that URL's latest field-data Core Web Vitals (LCP, INP, CLS).
  4. Bucket each row into a verdict — Poor CWV (any metric Poor), Needs Improvement, Good CWV, or Unknown (no field data).

Action column meanings

  • Fix page first — CWV is failing. The snippet rewrite is secondary; the page experience is the primary blocker.
  • Fix page + rewrite — Borderline CWV. Pair the title rewrite with an LCP / INP audit.
  • Title rewrite — Page is healthy. The snippet is the real bottleneck — go ahead and rewrite.
  • Run PSI first — No field data for this URL yet. Schedule a PSI run before deciding.

Data requirements

  • GSC gsc_query_day + gsc_query_page_snapshot_90d.
  • PSI ingestion including the field-data CWV table (PSIFieldMetric) for at least some landing URLs. URLs without enough CrUX traffic will surface as "Unknown CWV".