Is a sudden drop more likely an update or a technical break, how to tell?
- Published November 6, 2026
- Linked from 4 answers
- In a cluster of 77
Neither is more likely by default; the evidence decides. Line up three things: the date of the drop against Google’s published update dates, your own reports for errors around that date, and anything that changed on your site that week. A technical break leaves traces in your data and your change log; an update leaves none on your side, and its dates are public.
Read the evidence side by side
| Evidence | Points to a technical break | Points to an update |
|---|---|---|
| Your change log | A deploy, CMS edit, DNS or hosting change, robots.txt or template change near the date | Nothing changed |
| Search Console reports | A spike in errors in Crawl stats or in excluded pages in Page indexing | Reports flat; pages still crawled and indexed |
| Dates | Any day, tied to your change | Inside a rollout window on the Search Status Dashboard |
| Which pages | Pages that share a template, folder or server | Pages across sections with no shared technical cause |
Rollout dates are listed on Google’s Search Status Dashboard. The second row counts above the others, because Google’s traffic-drop guide tells you to check the Crawl stats and Page indexing reports for a “corresponding spike” in issues when you suspect a technical cause.
A break is not always a cliff
The old rule of thumb that a break looks like a sudden cliff and an update looks gradual misses one case. Google notes that technical issues “can be site-wide (for example, your website is down) or page-wide (for example, a misplaced noindex tag, which would depend on Google crawling the page, meaning there would be a slower drop in traffic)”. A noindex pushed to a template therefore drains traffic as Googlebot reaches each page, which can look like an update spread over days. That is why the shape of the graph alone does not settle the question and the reports do.
When both happen at once
A deploy can land in the middle of a rollout. Check the technical side first anyway: a break is yours to fix today, and fixing it removes one explanation from the picture. If the reports are clean and the change log is empty, an update becomes the leading explanation, not a proven one: falling demand, a competitor’s gain, a change in the results page or a tracking fault can draw the same graph, so split the drop by query, device and country before settling on it. The next question is then which update matches your dates, and if you have not yet measured how wide the drop is, start with whether it is a page or a site problem. If the drop lines up with a season, rule that out with how to tell a seasonal dip from a real ranking problem. A drop with a spike in your reports is a break until proven otherwise.
Add a comment