Content revised 21 October 2026.
A traffic-drop investigation starts with the affected dates, pages and search types. Build the evidence before choosing a technical repair or content change.
Locate the pattern
Compare a suitable previous period and check whether the decline affects the whole site or a smaller group. Break down queries, devices and countries. Keep seasonal demand and reporting changes in view.
Check availability and releases
Review outages, server responses, migrations, redirects, canonicals and robots instructions. Inspect important URLs and compare the deployed content with its earlier version. A single verified technical fault can explain a focused loss.
Review search context
Check relevant Google status information and update guidance when the timing supports it. Compare current results and customer needs without assuming a competitor caused the drop. A correlation alone does not establish a penalty.
Record the next step
List confirmed findings, unresolved questions and the planned verification. Make a scoped change and allow a suitable observation period. Recovery timing and positions cannot be guaranteed.
Official guidance: Google traffic-drop debugging.