Published September 8, 2026.
A sharp movement in Search Console deserves attention, but not every movement deserves an edit. A one-page card keeps the first response evidence-led.
Define the anomaly
Record the property, report, search type, date range, comparison period, device, country, page, and query filters. Save clicks and impressions alongside CTR and position so the change has context.
Check reporting boundaries
Note data freshness, preliminary periods, anonymized queries, row limits, canonical aggregation, and time-zone differences. Compare the page view with the property view before assuming a missing row represents lost demand.
Route the next action
A broken route, noindex tag, or canonical mismatch belongs to technical review. A changed query mix may need editorial investigation. A short-lived fluctuation with no corroborating evidence should be watched, not “fixed.”
State what would disprove the working explanation and choose a recheck date. The card is a triage tool, not a causal analysis or a promise of ranking recovery.