In short
A traffic drop is a symptom, not a diagnosis: first prove it is real, then find exactly what dropped, then match the pattern to a cause. Most drops fall into a few groups Google itself names: tracking or reporting problems, seasonality and changing interest, technical issues, algorithmic updates, spam and security problems, migrations, and changes to the results page. Work through them in order, write down the evidence, and fix only what the evidence points to.
What Google officially says
Google has a dedicated guide to debugging drops in Search traffic. It starts with a realistic warning:
“A drop in organic Search traffic can happen for several reasons, and it may not be straightforward to understand what exactly happened to your site.”
Google Search Central — Debugging drops in Google Search trafficThe guide shows four sketches of traffic charts, each labelled with the kind of cause that typically produces that shape: “Large drop from an algorithmic update, site-wide security or spam issue”, “Seasonality”, “Technical issue across your site, changing interests” and “Reporting glitch”. The figure below redraws those four shapes so you can compare your own chart with them.
The guide then walks through the main causes: algorithmic updates, technical issues, security issues, spam issues, seasonality and changing interests, and site moves and migrations. A few sentences from it set the tone for the whole method:
“If you suspect a drop in traffic is due to an algorithmic update, it's important to understand that there might not be anything fundamentally wrong with your content.”
Google Search Central — Debugging drops in Google Search traffic“Keep in mind that positions aren't static or fixed in place.”
Google Search Central — Debugging drops in Google Search traffic“Impressions and clicks are ultimately the measure of success for your site.”
Google Search Central — Debugging drops in Google Search trafficIn other words: some movement is normal, the Performance report in Search Console is your main instrument, and you should not rewrite good pages because of a small dip.
Step 1: is the drop real?
Before you look for an SEO cause, make sure you are not looking at a measurement problem. Many “drops” are a broken tag or a changed report, not lost visitors. Google's guide asks you to check the Search Console Data Anomalies page as well, because “The drop might be related to a change in the data processing or a logging error.”
The quickest test is to put two sources side by side: Search Console clicks and organic sessions in your analytics tool, usually GA4. They never match exactly, because they count different things in different ways, so compare the trend, not the totals.
- Both dropped at the same timeThe loss is probably real. Go on to Step 2.
- GA4 dropped, Search Console is flatIt is almost always tracking: the search engine is still sending the same clicks.
- Search Console dropped, GA4 is flatCheck the property, the date range and search type first; then treat it as a real visibility change that analytics does not yet show.
Typical tracking causes to rule out when GA4 alone dropped:
- The tag is missing on some templates. A release replaced a header or a new template was launched without the GA4 snippet or tag manager container. View the source of a few affected pages.
- The consent banner changed. A new consent platform, a different default or a changed consent mode setup lowers the number of sessions GA4 records, while Search Console clicks are unaffected.
- Filters, channel groups or referral settings changed. A new data filter, an edited channel grouping or a payment provider added to referral exclusions can move traffic out of the Organic Search channel without any visitor being lost.
- Cross-domain or redirect changes. A new domain in the journey, or a redirect that strips parameters, can split or relabel sessions.
Also check that the newest days are complete. Search Console's help notes: “Preliminary data: The newest data can be preliminary, meaning it's still being collected and might change in the next few hours.” A “drop” in yesterday's numbers is often just data that has not arrived yet. How to set up GA4 so these checks are easy is covered in the lesson GA4 for SEO.
Step 2: compare the right periods
A drop only exists in comparison with something. The wrong comparison creates drops that are not there, or hides real ones.
- Look at 16 months first. Set the Performance report date range to the last 16 months. Google explains: “This will help you analyze the traffic drop in context and make sure it's not a drop that happens every year due to a festivity or a trend.” If you need a longer history, store data through the Search Analytics API or bulk export.
- Use previous period to see the change, year over year to judge it. Previous period shows when the drop started and what changed. Year over year shows whether the same months were also weaker last year.
- Compare whole weeks. Traffic usually differs between weekdays and weekends. Compare Monday to Sunday with Monday to Sunday, and avoid comparing a holiday week with a normal one. Weekly or monthly granularity smooths those swings out.
- Check demand in Google Trends. Take the queries that lost the most clicks and look them up one by one. If interest fell everywhere, the drop is not about your site.
- Around an update, wait for the dates to settle. For core updates Google says: “We recommend waiting at least a full week after a core update completes before analyzing your site in Search Console.” and “After a week, try comparing this week with a week before the core update started rolling out”.
Step 3: segment the drop
A total line tells you that something happened. Segments tell you where. Google's guide puts it directly: “For example, one important factor is finding out if the drop happened across the whole site, a group of pages, or even just one very important page in your site.” When comparing periods, it adds: “Make sure to click all tabs to find out if the change happened only for specific queries, URLs, countries, devices, or search appearances”.
In the Pages table, compare the two periods and “Select Clicks Difference to order it based on pages that lost the most traffic.” Then work through the checklist below. Regex filters and comparisons in the Performance report are explained in detail in the lesson Performance report: filters, regex, comparisons.
| Segment | How to cut it | What a concentrated loss suggests |
|---|---|---|
| Page groups | Page filter by folder or regex: /blog/, /product/, one template | A template, a section or one release; check those URLs in URL Inspection |
| One key page | Pages tab, Clicks Difference | That page changed, lost indexing, or a competitor replaced it |
| Brand vs non-brand | Query regex with your brand names and misspellings, then the inverse | Brand down: demand, reputation or offline factors. Non-brand down: rankings or the results page |
| Query types | Regex for intent words: price|buy, how|what, product names | A shift in one intent or a SERP feature that took over one query type |
| Device | Devices tab, mobile vs desktop | Mobile-only issues: mobile template, interstitials, mobile results layout |
| Country | Countries tab | Local demand, a hreflang or geo-redirect problem, a local competitor |
| Search appearance | Search appearance tab | Lost rich results: structured data errors or eligibility changes |
| Search type | Search type filter: web, image, video, news | The loss is in one surface, for example Google Images only |
Remember how the report counts. The chart is aggregated by property, while “Data grouped by Pages or Search appearance is aggregated by page.” So page-level totals can be higher than the chart total. That is expected, not a second drop.
Step 4: read the shape of the metrics
Turn on all four metrics in the Performance report: clicks, impressions, CTR and average position. How they move together is the most useful single clue. Google gives two rules: “If both impressions and clicks dropped, check the list of the most common reasons that could have caused it.” and “If your impressions remain the same but your clicks drop, you might not be generating the best page title and snippet that you could, and so users don't understand the content of your page, or perhaps other sites had a more appealing rich result.”
| Clicks | Impressions | Position | Likely reading |
|---|---|---|---|
| Down | Down | Down | Ranking loss: update, technical problem, competition |
| Down | Down | Stable | Less demand (season, interest) or pages dropped out of the index |
| Down | Stable | Stable | CTR loss: snippet, rich results of others, AI Overviews or new SERP features |
| Down | Stable or up | Slightly down | Small position drop at the top, for example from 2 to 4 |
| Stable | Down | Up | Usually harmless: you lost low-value impressions deep in the results |
Google separates small and large position changes. A small drop is “dropping from position 2 to 4”, and in that case “In Search Console, you might see a noticeable drop in traffic without a big change in impressions.” Its advice: “In fact, we recommend avoiding making radical changes if your page is already performing well.” A large drop is falling out of the top results for a wide range of terms, such as from position 4 to 29. Then: “In cases like this, self-assess your whole website overall (not just individual pages) to make sure it's helpful, reliable and people-first.”
Average position is an average of your topmost result across all queries. If you start ranking for many new, distant queries, the average gets worse even though nothing was lost. Read position per query or per page, not only as a site-wide number.
Technical causes
Google defines them broadly: “Technical issues are errors that can prevent Google from crawling, indexing, or serving your pages to users.” Its examples include server availability, robots.txt fetching and “page not found” errors. The shape of the drop depends on the scope: “Note that the 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).”
Where to look first: the Crawl stats report and the Page indexing report, for a spike in errors that starts around the same date as the drop. Google adds: “If it's a site-wide issue, check the Page indexing report.” If only a group of pages is affected, inspect a few of them with the URL Inspection tool.
For each of your top lost pages, run the same fast checks:
- Status code. Does the URL still return
200, or a404,5xxor unexpected redirect? See the lesson Status codes, soft 404, 410. - robots.txt. Was a
Disallowrule added for the folder, or does robots.txt itself fail to load? See robots.txt and AI crawlers. - noindex. Look in both the raw and the rendered HTML, and in the
X-Robots-Tagresponse header. See Meta robots and X-Robots-Tag. - Canonical. Did a template start pointing canonicals to the wrong URL? URL Inspection shows the user-declared and Google-selected canonical.
- Redirects. After a release or migration, check old URLs redirect in one hop to the right new URL. See Redirects and site migrations.
- Rendering. Use the URL Inspection live test to confirm that the main content and links appear in the rendered page.
Migrations deserve a separate note. Google says: “If you change the URLs of existing pages on your site, you may experience ranking fluctuations while Google recrawls and reindexes your site.” A dip right after a well-executed move is normal; a drop that does not recover usually points to broken or missing redirects. The statuses you will see in the indexing report are explained in Page indexing report: every status.
Algorithmic causes: core updates and spam updates
Google describes core updates like this: “Several times a year, Google makes significant, broad changes to our search algorithms and systems.” and “These changes are broad in nature, and don't target specific sites or individual web pages.” Spam updates target practices that break Google's spam policies. How the ranking systems and update types work is covered in Ranking systems, core updates and spam policies.
The diagnostic question is timing. Open the Google Search Status Dashboard at status.search.google.com. It shows the status of four Search systems (Crawling, Indexing, Ranking and Serving) day by day, marks each as available or affected by an incident, and keeps an incident history with the start and end of ranking updates. Google explains: “The dashboard shows issues that affect many sites or users, so if you see an annotation in the dashboard, it may be related to the change in your site's performance.” If nothing is listed, that does not clear you: “The issue may be isolated to your web pages, or it may be impacting a limited number of searchers or websites.”
If the drop starts inside an update window:
- “Confirm that the core update has finished rolling out.” Note the start and end dates.
- Wait a full week after it ends, then compare a week after with a week before the rollout started.
- Decide whether the drop is small or large, as in Step 4. Small: leave the pages alone. Large and site-wide: self-assess the site as a whole.
- Avoid quick fixes. Google warns: “Deleting content is a last resort, and only to be considered if you think the content can't be salvaged.”
- Expect a slow response. “If it's been a few months and you still haven't seen any effect, that could mean waiting until the next core update.”
The full recovery process, from self-assessment to what to change and how long to wait, is the subject of the next lesson, After a core update.
Manual actions and security issues
Two Search Console reports should be opened in every investigation, because they turn a guess into a fact within a minute.
Manual actions Check every time
Google detects spam through automated systems and, when needed, human review. “If your site doesn't comply with the Spam policies for Google web search, your content might rank lower in results or not appear in results at all.” The Manual Actions report says whether a reviewer applied an action, to which part of the site, and why. Fix the issue on all affected pages, then request a review.
Security issues Check every time
Malware, phishing and hacked content hurt traffic even when rankings hold, because “Google may alert users before they reach your site with warnings or interstitial pages, which may decrease Search traffic.” The Security Issues report lists what Google detected. Clean the site, close the hole that let the attacker in, and then request a review.
Algorithmic spam demotions do not appear in the Manual Actions report. If that report is empty but the drop matches a spam update on the Status Dashboard, review your site against the spam policies anyway.
Seasonality and changing interest
Not every drop is your fault. “Sometimes changes in user behavior will change the demand for certain queries, either due to a new trend, or seasonality throughout the year.” Google adds: “This means your traffic may drop as a result of external influences.” and “Different industries have different levels of seasonality.”
The test is simple. Filter the Performance report to one high-traffic query at a time and compare year over year. Then look up the same queries in Google Trends. If interest in winter tyres falls every spring on the web as a whole, your spring drop on example.com/winter-tyres/ is demand, not rankings.
Changing interest is the slower, permanent version of the same thing: people “may start searching for different queries, or using their devices for different purposes.” A product line replaced by a new model, a technology that went out of use or a topic people now ask about in different words all reduce traffic without any loss of position. The answer here is content planning, not technical fixes: find the queries that grew and check whether you have pages for them.
SERP changes and competition
Sometimes your position, your pages and the demand all stay the same, and clicks still fall. The cause is then on the results page itself.
- AI Overviews and AI Mode. When an AI-generated answer appears above the results for a query, some searchers get what they need without clicking. The typical sign is falling CTR and clicks with stable impressions and position on informational queries.
- New or bigger SERP features. Video blocks, People also ask boxes, product grids, local packs or images can push the first organic result further down the page.
- Other sites' rich results. Google names this directly: “perhaps other sites had a more appealing rich result.”
- Your own lost rich results. Check the Search appearance tab and the structured data reports; a broken markup template removes stars or other enhancements at once.
Always check the live results page for your main lost queries, in the country and device that lost the traffic. Search Console cannot show you what the page looks like. The different result types are described in Classic results, AI Overviews, AI Mode, Discover.
Competition is the last common cause. Positions are relative: a competitor that publishes a better, fresher or more complete page moves you down without anything changing on your side. Google's guide is honest about this: “If there's more deserving content, it will continue to rank well with our systems.” Look at who now ranks above you for the lost queries, and compare their pages with yours on substance, not on word count.
| Cause | Typical evidence | Where to confirm | Fix |
|---|---|---|---|
| Tracking | GA4 down, Search Console flat | Page source, tag manager, consent and filter change log | Restore the tag or settings; annotate the gap |
| Reporting glitch | One-day gap, then normal | Search Console Data Anomalies page | None; exclude the gap from comparisons |
| Seasonality | Same dip last year | 16 months view, Google Trends | None; plan content and budgets around it |
| Site-wide technical | Sharp drop on a date, all segments | Crawl stats, Page indexing, server logs | Fix availability, robots.txt or the release |
| Page-level technical | Slow decline in one page group | URL Inspection on samples, a crawl of that section | Remove wrong noindex, canonicals or redirects |
| Migration | Drop after URL changes that does not recover | Redirect map, old URLs in Page indexing | One-hop 301s from every old URL to its equivalent |
| Core update | Drop starts during the rollout window | Search Status Dashboard, week vs week | Self-assess the site; improve, do not quick-fix |
| Manual action | Drop on the site or a section | Manual Actions report | Fix all cases, then request a review |
| Security issue | Warnings shown to users | Security Issues report | Clean, secure, then request a review |
| SERP change | CTR down, position and impressions stable | Live SERP check for lost queries | Better titles and snippets; target queries with clicks left |
| Competition | Others moved up on your lost queries | Position by query, competitor pages | Make your page genuinely better for that query |
Write the diagnosis down
A written diagnosis forces you to separate what you know from what you suspect. It also makes it easy to hand the fix to a developer or a writer and to check later whether the fix worked. Keep it short and fill every line.
# Site: example.com Written: 2026-10-30
What dropped Organic clicks to /guides/ (non-brand, mobile, UK)
Since when 2026-10-08, comparing 7 days vs the 7 days before
How much clicks -38%, impressions -5%, position stable (illustrative)
Is it real? yes: Search Console and GA4 both down; no data anomaly
Scope one page group (/guides/), rest of site stable
Evidence CTR down on how-to queries; AI Overview now shown
Ruled out tracking, season (YoY), indexing errors, manual action
Cause SERP change Confidence medium
Fix rewrite titles and snippets; extend pages for follow-up questions
Owner content team Re-check 2026-11-27Rule out technical causes fast
OurSEO Tools runs a 69-point checklist, including indexation, redirects and rendering, and crawls up to 1,000 pages with the status code, canonical, indexability and load time of every URL, so you can see quickly whether a drop has a technical cause.
Common mistakes
- ✕Starting with fixesRewriting pages before you know what dropped and why.
- ✕Trusting one data sourceCalling a GA4 dip a ranking loss without checking Search Console clicks.
- ✕Comparing the wrong periodsA holiday week against a normal week, or a month against the previous month in a seasonal niche.
- ✕Analysing an update mid-rolloutDraw conclusions only after the update has ended and a full week has passed.
- ✕Reading only the site totalA small site-wide change can hide a large loss in one section or one country.
- ✕Obsessing over average positionThe site-wide average moves when you gain new distant queries; clicks and impressions matter more.
- ✕Deleting content as a first responseGoogle calls deletion a last resort.
- ✕Never checking the live results pageA CTR loss caused by new SERP features looks like a mystery from inside Search Console.
FAQ
How do I know if a traffic drop is real or a tracking error?
Compare Search Console clicks with GA4 organic sessions over the same dates. If Search Console is flat and only GA4 fell, it is tracking: look for a missing tag, a consent change or a new filter. If both fell together, the loss is real.
How long should I wait after a core update before analysing it?
Until the update is marked complete on the Search Status Dashboard, plus at least a full week. Then compare a week after the rollout with a week before it started.
Impressions are stable but clicks fell. What does that mean?
Your visibility is the same but fewer people click. Check the live results page for AI Overviews, new features and competitors' rich results, and review your titles and snippets for the affected queries.
Should I compare with the previous period or with last year?
Both. The previous period shows when the change started and what changed. Year over year shows whether it is seasonal. In a seasonal niche, only the year-over-year view tells you whether you actually lost ground.
Nothing is listed on the Search Status Dashboard. Can it still be an update?
The dashboard lists notable updates and widespread issues. Google also makes smaller updates that are not announced, and some problems affect only your site. An empty dashboard rules out a widespread incident, not every algorithmic cause.
My traffic dropped slowly over months. Where do I start?
A slow decline points to page-level technical problems such as a noindex spreading through a template, to changing interest, or to competitors gradually overtaking you. Segment by page group, check Page indexing trends, then compare demand in Google Trends.
Sources
- Google Search Central — Debugging drops in Google Search traffic
- Google Search Central — Google Search's core updates and your website
- Google Search Console Help — Performance report (Search results): Overview and basic setup
- Google Search Central — Using the Google Search Status Dashboard
- Google Search Status Dashboard
Quotes checked against the official pages on 30 October 2026.