A call about a traffic drop usually arrives with a plan attached: rewrite the content, disavow some links, revert the last release, blame the latest update. Sometimes one of those is right. More often the plan is a guess made before anyone has looked at the pattern. Google’s guide to debugging drops in Search traffic is a good counter to that, because it is organised by cause and tells you what to look at for each. This article walks through the causes Google’s guidance describes, with our own reading marked as such.
Start with the shape of the line, not the theory
Google’s guide begins with sketches of what different causes tend to look like on a graph: a large drop from an algorithmic update or a site-wide security or spam issue, a seasonal pattern, a technical issue across the site or changing interests, and a reporting glitch. It says the best way to understand what happened is to look at the main chart in the Search Console Performance report.
Two patterns are called out. If both impressions and clicks dropped, you work through the list of common causes. If impressions held but clicks dropped, the guide suggests your page title and snippet may not be helping users understand the page, or that other sites had a more appealing rich result. These are different problems with different fixes, which is why the shape comes before any decision. Our article on what the Performance report can and cannot tell you covers how the underlying numbers are counted.
Rule out the measurement problem and the calendar
The cheapest explanations come first. Google tells you to check the data anomalies page, because a drop might be related to a change in data processing or a logging error. If the anomalies page explains it, no work on the site is needed.
Next, set the date range to the last 16 months, so the drop is seen in context and checked against a festivity or trend that recurs each year. Google’s example chart shows a recent drop happening exactly as it did a year before. Then use the compare option to review the last three months against the previous period or the same period a year earlier, and click through the tabs to see whether the change is confined to particular queries, pages, countries, devices or search appearances. Analyse web, image, video and news separately, since a fall in one tab can look like a site-wide problem in the total.
For seasonality and changing interests, Google suggests filtering to your biggest queries one at a time and checking them in Google Trends, to see whether the dip is specific to your site or happens across the web.
Technical, security and spam causes
Google defines technical issues as errors that can prevent it from crawling, indexing or serving your pages, with server availability, robots.txt fetching and page-not-found errors as examples. They can be site-wide, as when a site is down, or page-wide, as with a misplaced noindex tag. The guide notes that a noindex problem depends on Google recrawling the page, so the traffic loss would be slower. It points to the Crawl Stats and Page indexing reports to look for a matching spike in issues.
Security problems, such as malware or phishing, can lead Google to warn users before they reach a site, which may reduce traffic; the Security Issues report is where to check. For spam, the guide says content may rank lower or not appear at all if a site does not comply with the spam policies, and points to the Manual Actions report. These checks are quick and have clear answers, so we would do them before spending time on anything that depends on judgement.
When the cause may be an algorithmic update
Google says it is always improving how it assesses content, and that core updates and smaller ones may change how some pages perform. It keeps a list of ranking updates for notable changes. The most useful point in the guide is the caution that if you suspect an update, there might not be anything fundamentally wrong with your content.
It splits the situation by size. After a small drop in position, such as moving from 2 to 4, Google says small fluctuations can happen at any time, can reverse without action, and that it recommends avoiding radical changes when a page is already performing well. After a large drop out of the top results for a wide range of terms, the advice is to assess the whole website, not just individual pages, for being helpful, reliable and people-first. It also warns that changes can take effect within days or take several months, that you will probably want to wait a few weeks before checking Search Console again, and that there is no guarantee changes will have a noticeable effect. In our reading, this is the part most often skipped under pressure: judging a remedy before it can possibly have been tested.
Site moves and the damage a release can do
If URLs changed, ranking fluctuations are expected while Google recrawls and reindexes. The guide gives a general rule that a medium-sized website can take a few weeks for Google to notice the change, and larger sites can take longer. A drop after a move that is not recovering sends you to the site move troubleshooting section for common mistakes. Releases that did not change URLs can still cause technical damage, as in the noindex example above. Our article on WordPress launch checks that protect rankings covers the checks that prevent these.
Narrowing it down inside the report
Once the cheaper causes are excluded, the guide moves to the detail. Look at average position, but Google says not to focus too much on absolute position, because impressions and clicks are ultimately the measure of success; a dramatic, persistent drop in position is the signal to self-assess content. Then review the Pages table to see whether the loss is across the whole site, a group of pages or one important page, sorting by clicks difference to find the biggest losers. A site-wide pattern sends you to the Page indexing report. A group of pages sends you to the URL Inspection tool for a sample. Finally, Google Trends and top queries in your region can show whether demand moved, and whether queries missing from your traffic have content that is being crawled and indexed.
Where this fits at Cultured Digital: finding the cause
The first step of how we work is to investigate, followed by diagnosing the real problems rather than treating symptoms, and a traffic drop is a case where that order matters. Our SEO audit is a focused investigation that finds the cause and then says what to do first, and it lists Google’s traffic-drop guidance among its further reading. Where the question is whether a plan is working, the Measure guide under SEO Strategy covers measurement design, and the crawling and indexing guide covers the technical side. Once the cause is known, the prioritisation article sets out how we think about what to do first. We do not promise rankings or traffic numbers; we set out the evidence, and measure against it.