TL;DR
The call always has the same shape. Traffic fell off a cliff, nobody changed anything, and it must be Google. In fifteen years it has almost never been Google. Check whether the drop is real before anything else, then ask what shipped that week, and ask the developer rather than the marketer.
The call always has the same shape. Traffic fell off a cliff, nobody changed anything, and it must be Google.
In fifteen years it has almost never been Google. Here is the order I work through, which is roughly the order of how likely and how cheap each explanation is.
1. Is the drop real, or is it the tracking?
First, always, and it resolves a meaningful share of these calls in ten minutes.
A consent banner change, a tag manager container republished, a plugin update, a migration that dropped the analytics snippet from one template. Any of those produces a vertical cliff in analytics with nothing whatsoever happening in search.
The test: does Search Console agree? If clicks in Search Console are flat while analytics has collapsed, you have a measurement problem, not a traffic problem. If both fell, keep going.
2. What shipped that week?
Before touching anything, get the exact date from Search Console and ask what happened in the days before it. A release, a theme update, a plugin, a migration, a robots.txt edit, a new SEO plugin with opinionated defaults.
“Nobody changed anything” is said in good faith and is wrong more often than it is right, because the person saying it did not personally change anything. Ask the developer, not the marketer.
3. Is something blocking or noindexing at scale?
The catastrophic causes are few and quick to rule out. A staging Disallow: / that shipped. A noindex applied at category level. A canonical pointing somewhere wrong across a template.
Check the raw source and the HTTP headers, because X-Robots-Tag does the same job invisibly. This is the same sequence I run for pages that dropped out of the index, and on a sitewide drop it is the first thing that would explain the shape.
4. Did impressions fall, or only clicks?
This is the diagnostic split people skip, and it separates two completely different problems.
Impressions fell. You lost visibility. Rankings, indexing, or a competitor.
Impressions held and clicks fell. You are still appearing and fewer people are clicking. That is a result-page change, not a ranking change, and it is increasingly the answer. SparkToro’s analysis of Similarweb’s US clickstream found AI Overviews now appearing on over 20% of searches and cutting click-through by roughly 60% where they appear.
A site can hold every position it had and lose a third of its clicks. No amount of technical work fixes that, and diagnosing it as a ranking problem wastes a quarter.
It is the same split that separates the four causes of a high-impression, low-click row. There the question is why one query underperforms; here it is why the whole site did. Same two columns, same discipline: read them apart before you read them together.
5. Read the position column properly
Average position is not what most people think it is. Google’s own documentation defines it as the topmost position your property occupied, averaged across queries where you appeared, and states plainly that it is “a complex metric that can be misleading if you don’t understand the subtleties.”
Two consequences that matter during a drop. Losing rankings on weak queries can make average position improve, because the bad ones stopped appearing. And a position that appears stable can hide a large change in which queries produced it.
Compare query sets, not averages.
6. Only now, consider Google
A core update, or an algorithmic change. Real, and last on the list because it is the explanation people reach for first and it is rarely correct.
The tells: it started on a date Google has confirmed, it affected a category of pages rather than the whole site, and competitors moved too. If your drop is sitewide, overnight, and your competitors are unchanged, that pattern does not look like an update. It looks like something you shipped.
What I would not do in week one
- Rewrite content. If the cause is a header directive, a month of writing changes nothing and you will conclude content does not matter.
- Mass-resubmit for indexing. It treats a symptom and tells you nothing.
- Panic-disavow. Almost never the answer and occasionally makes things worse.
The short version
- Check the tracking first. Does Search Console agree with analytics?
- Ask what shipped that week, and ask the developer, not the marketer.
- Rule out sitewide noindex, robots block and canonical faults. Check headers too.
- Impressions or clicks? Different problems entirely.
- Clicks alone can fall from AI Overviews, on 20%+ of searches, cutting CTR ~60%.
- Average position is topmost-position-averaged and Google warns it misleads.
- Consider a core update last. Sitewide and overnight usually means you shipped something.
If a site should be ranking and it isn’t, that’s the work I do. SEO recovery covers diagnosing drops and what realistically comes back. If you’re not sure which of several plausible problems is costing you, that’s what an SEO audit is for.
