When search traffic drops: a calm checklist
When search traffic drops, this guide works through it in a calm order, built from Google’s own debugging guide: rule out Google’s side (the Search Status Dashboard and Search Console’s data anomalies page), check your own site for manual actions, security issues, technical errors and recent changes, then read the shape of the drop in the Performance report. Keep calm while you do: Google’s own guide says a drop after an algorithm update may not mean anything is fundamentally wrong with your content.
Work down the list in order. Tick each line when you have an answer, even if the answer is “nothing here”.
General information, not business advice. This page explains Google’s published documentation in plain words. Google’s tools change: check Search Console Help, Google Search Central and web.dev for the current version, and ask a qualified professional about your own site.
06.1
Google’s side first
The Search Status Dashboard. It shows issues affecting many sites or users, and the latest ranking updates; Google says an annotation there may relate to a change in your site’s performance. When this page was checked on 7 October 2026, it listed the September 2026 spam update as active, starting 24 September 2026 (US Pacific time), affecting ranking.
The ranking history. Past updates stay on the dashboard’s history page for 5 years, so you can line up a drop with an update’s start and finish dates.
The data anomalies page. Google records known logging and processing issues there; a drop can be a change in how data was collected rather than in your traffic.
Nothing listed? The dashboard only shows widespread issues. An issue that isn’t there may be confined to your pages, or to a small number of sites.
06.2
Your side: warnings and errors
Manual actions report. A manual action is taken when a human reviewer at Google finds pages that don’t comply with its spam policies; affected pages may rank lower or be left out of results.
Security issues report. Hacked content, malware or social engineering can bring warning labels in search results or a warning page in the browser, which may cut traffic.
Page indexing report. Look for a spike in issues around the date of the drop. Google notes that some problems are site-wide, such as a site being down, while others are page by page, such as a misplaced noindex tag, which tends to bring a slower drop.
Crawl stats report. Check for server availability problems or failed robots.txt fetches at the same time.
URL Inspection on a few affected pages. If the drop touches only a group of pages, inspect some of them individually.
06.3
Your side: what changed
A site move or new URLs. Changing URLs can bring ranking fluctuations while Google recrawls and reindexes. Google says a medium-sized site can take a few weeks for Google to notice the change, and larger sites longer.
New titles, templates or content. Write down what changed and when. If impressions held but clicks fell, Google points first to page titles and snippets.
The measuring itself. A change of property, filter or search type can look like a drop. Make sure this month and last month are being read the same way.
06.4
Read the shape of the drop
Widen to 16 months. In the Performance report, set the date filter to the last 16 months to see whether the same dip happens every year.
Compare like with like. Use Compare for the last 3 months against the previous period, or year over year, and click through the queries, pages, countries, devices and search appearance tabs to find where the change sits.
Separate search types. Check web, image, video and news results one at a time.
Clicks and impressions together, or apart? Both down suggests one of the causes above. Impressions steady with clicks down suggests titles, snippets, or a more appealing result from another site.
Whole site, a section, or one page? Sort the Pages tab by the difference in clicks. A site-wide drop sends you to the Page indexing report; a group of pages, to URL Inspection.
06.5
If it lines up with a ranking update
| What you see | Google’s example | Google’s advice |
|---|---|---|
| Small drop in position | 2 → 4 | No need for drastic action; avoid changing content that already performs well. Small movements can reverse on their own. |
| Large drop in position | 4 → 29 | Self-assess the whole site, not just single pages, for whether it is helpful, reliable and people-first. |
For a core update, Google suggests confirming on the dashboard that it has finished rolling out, waiting at least a full week after it completes, then comparing a week after with a week before it began. Google warns against quick fixes, such as removing a page element because someone said it was bad for SEO, and calls deleting content a last resort. Improvements can take effect in a few days or take several months to show, and Google is plain that there is no guarantee changes will have a noticeable effect.
06.6
The wider web
Seasonality and changing interests. Demand for some searches changes with trends or the time of year. Filter the Performance report to one top query at a time and look it up in Google Trends to see whether interest dropped everywhere or only for your site.
Positions are never fixed. Google’s results change as the web changes, which can bring both gains and drops without anything being wrong.
If every line is ticked and the cause is still unclear, Google suggests asking in the Google Search Central help community, for issues that aren’t on the dashboard.