Diagnosing a Traffic Drop

Diagnosing a traffic drop is a procedure that separates "it fell because of us" from "it fell everywhere" and from "it's just the season". The main rule is the same as in Google's guide: a drop in organic Search traffic can happen for several reasons, and it may not be straightforward to understand what exactly happened. So first a diagnosis from data, then the treatment. Below: the causes Google names, how to read the chart in Search Console and in which order to check.

The basis is Google's guide to debugging traffic drops. Related lessons: core updates, manual actions, the crawling and indexing audit and Search Console.

The causes Google names

The guide lists the main causes of drops in organic traffic. It is not "four causes", as is often written, but more:

• An algorithmic update. A large drop after a core update; see the list of ranking updates and the lesson on core updates;
• Technical issues. Errors that can prevent Google from crawling, indexing or serving pages: server availability, robots.txt fetching, "page not found". They can be site-wide or page-wide, such as a misplaced noindex. Check the Crawl Stats and Page indexing reports for a spike in issues;
• Security issues. Malware or phishing: Google may warn users before they reach your site. See the Security Issues report;
• Spam policy violations. Automated systems and human review; see the Manual Actions report and the lessons on manual actions and spam policies;
• Seasonality and changing interests. Demand for queries changes with a trend or the time of year;
• Site moves and migrations. If you changed URLs, fluctuation is possible while Google recrawls and reindexes; for a medium site that is a few weeks. See the lesson on migrations;
• A reporting glitch. Check the Search Console Data Anomalies page: the drop may be tied to a change in data processing or a logging error.

"Competitors' actions" from the familiar scheme is not a separate cause in the documentation: Google says results are dynamic because the web is constantly changing, and new and updated content causes both gains and drops. And "Semrush sensors" and similar volatility indexes are third-party estimates; per the documentation the reference points are Google's list of updates and the Search Status Dashboard.

Step 1: read the main chart

The best way to understand what happened is to look at the main chart in the Performance report. Google distinguishes two cases:

• Both impressions and clicks dropped. Go through the list of causes above;
• Impressions stayed the same but clicks dropped. Perhaps the title and snippet are not the best and users don't understand the content of the page, or other sites had a more appealing rich result. See the lesson on Search Console and CTR.

Step 2: narrow the data

1. Choose "last 16 months". This shows the drop in context and tells you whether it recurs every year because of a festivity or a trend. Beyond 16 months you can pull data through the API or bulk export;
2. Compare with a similar period. The Compare tab: the last 3 months with the previous period or with the same period last year. Click all tabs: did it drop only for specific queries, URLs, countries, devices, search appearances;
3. Split the search types: web, images, video, news. That shows where it dropped;
4. Don't fixate on absolute position. Google: impressions and clicks are ultimately the measure of success; but if you see a dramatic, persistent drop in position, self-assess your content for helpfulness and reliability;
5. Look for patterns in the pages. Sort the pages table by the clicks difference to see what lost the most. Did the whole site drop, a group of pages or one important page?

If the whole site dropped, open the page indexing report; if a group of pages, check a few with URL Inspection. For comparing periods there is wins and losses, for overlaying update dates the update monitor, and for a bulk status check the URL audit. Look at analytics data (sessions, engagement) per the lesson on GA4: with it you see whether only the organic channel fell.

Step 3: external causes

If you suspect seasonality or changing interests, pick the queries with the most traffic one at a time and check them in Google Trends: did the drop happen only for your site or throughout the web. The example from the guide: queries about turkey are strongly seasonal and peak in November, chicken is less seasonal and coffee is almost stable. That also shows that a drop "in January" is normal for some topics. It is also useful to compare the top queries of a region with those you get traffic from: if some are missing, check whether the site has content on the subject and whether it is crawled and indexed.

Step 4: technical checks

• The page indexing report: are there new problems?
• robots.txt and noindex: is the site or a section blocked by mistake? An example: a developer blocked a section in robots.txt "temporarily" at deploy and did not revert. With an accidental noindex, Google says, the drop is slower: the rule takes effect only after Google has crawled the page. More in the lesson on robots.txt and meta robots;
• Mass 404s and redirect chains; a URL structure change without redirects. The crawler helps find them;
• The Crawl Stats report: is there a spike in server errors.

If the cause is an update

If the date matched a core update, do not hurry. Google writes: with a small drop in position no drastic action is needed, and for a large sustained drop assess the whole site; wait at least a week after the update ends and compare that week with the week before it started. Details are in the lesson on core updates, and the order of fixes in the lesson on prioritization.

What is not in the documentation

• A division of causes into "four": Google names more and includes seasonality, security, spam and reporting glitches;
• "Competitors' actions" as a separate cause and a third-party Sensor or MozCast as a diagnostic tool;
• The conclusion "only brand queries fell, so it is reputation": that is a hypothesis to be checked;
• Recovery timelines such as "traffic came back in 2 weeks": after changes an effect can show in days or months, and there is no guarantee.

Checklist

1. The main chart is read: both impressions and clicks fell, or only clicks.
2. The 16-month window is on and seasonality checked.
3. The comparison is with a similar period or last year.
4. Search types, countries, devices and pages are analyzed separately.
5. Indexing, robots.txt, noindex, 404s and redirects are checked.
6. Security, manual actions and data anomalies are checked.
7. The date is matched against the list of updates and the status dashboard.
8. External causes are checked through Google Trends.
9. Changes are made one at a time, with the date recorded.

Mistakes

• Changing a lot at once without understanding the cause.
• Analyzing data before the update has finished.
• Looking only at position.
• Forgetting seasonality and not turning on the 16-month window.
• Treating any drop as an "update" or a "penalty".

What comes next

The audit course ends here. The next step is prioritization: how to turn a cause you have found into an order of work.