Part of the Search Performance series. For the full picture, start with How to use Google Search Console for SEO: a practical guide.
A traffic drop is stressful mostly because it’s vague: the line goes down and every possible cause seems equally likely. It isn’t. Most drops have a recognisable shape, and a few checks, done in order, usually narrow it down to one or two causes within an hour.
This guide walks through that order, based on Google’s own guide to debugging Search traffic drops.
What causes organic traffic to drop?
Google lists six main causes:
| Cause | What Google says | Typical shape |
|---|---|---|
| Technical issues | Problems preventing crawling, indexing or serving pages, site-wide or on specific pages | Sudden; often site-wide or one template |
| Security issues | Malware or phishing can trigger warnings that “may decrease Search traffic” | Sudden; whole site |
| Spam issues | Content not complying with policies may “rank lower in results or not appear in results at all” | Sudden; whole site or sections |
| Algorithmic updates | “Google is always improving how it assesses content and updating its search ranking and serving algorithms” | Over days, around an announced update |
| Search interest | Seasonality and changing user behaviour | Gradual, or repeats each year |
| Site moves | URL changes can cause “ranking fluctuations while Google recrawls and reindexes” | After a migration |
Step 1: Is the drop real?
Before investigating, rule out measurement problems:
- Is it branded or non-branded? Brand searches move mostly with marketing and PR. See branded vs non-branded traffic.
- Is it in Search Console, or only in Analytics? If Search Console clicks are steady and Analytics sessions fell (check the GA4 landing page report), look at tracking: a broken tag, a consent banner change, or a new channel definition.
- Compare with the previous period and the same period last year. In the Performance report, use the date comparison with weekly or monthly granularity, which Google recommends to neutralise day-of-week effects. A drop that also happened last year is likely seasonal.
- Check impressions and position, not just clicks. Google’s guide notes that “impressions and clicks are ultimately the measure of success”, but position tells you whether rankings moved.
| Clicks | Impressions | Position | Likely meaning |
|---|---|---|---|
| Down | Down | Steady | Less demand, or fewer results shown: check seasonality and Google Trends |
| Down | Down | Down | Rankings lost: technical, update or competition |
| Down | Steady | Steady | Fewer clicks per view: SERP changes or a weaker snippet |
Step 2: Where is the drop concentrated?
Break the comparison down by each dimension and sort by the Difference column:
- Pages: one page, one section, one template, or everything?
- Queries: a few head terms, or the long tail?
- Devices: mobile only can point to mobile rendering or Core Web Vitals problems.
- Countries: one country can point to hreflang or a local competitor.
- Search appearance: a lost rich result shows up here. See Search Console search appearance.
A drop concentrated in one template or directory almost always has a cause specific to it. A drop spread evenly across the site points to something site-wide: a technical change, a security or spam issue, or an update.
Step 3: Did something change on the site?
This is the most common cause, and the easiest to fix. Look for:
- Pages that now return errors or redirect
- A noindex or canonical change shipped with a release
- A robots.txt change, or a CDN or firewall blocking Googlebot
- Title or content changes on the pages that dropped
- Internal links removed in a navigation or template change
Crawling the site and comparing it with an earlier crawl shows these directly. In Crawlens, Compare lists URLs whose status code changed, that became non-indexable, that are no longer found by following links, and whose title changed, along with new and fixed issues. With Search Console connected, two checks name the pages where it hurts most: Pages with search traffic return errors and Pages with search traffic are not indexable. With Analytics connected, Landing pages with visits return errors covers every channel.
If you don’t have a crawl from before the drop, start one now and schedule regular crawls, so the next comparison is possible. Server logs fill the gap: Googlebot gets errors shows what Google actually received. See log file analysis.
Also check Search Console itself: the Page indexing report for a jump in excluded URLs, and the Security issues and Manual actions reports.
Step 4: Was there a Google update?
Check the Google Search Status Dashboard for ranking updates around the date the drop started. If a core update lines up and nothing changed technically, it’s the likely cause.
Google’s guidance on core updates is worth reading before reacting: a drop doesn’t necessarily mean something is wrong with the pages; other content may now be judged more helpful. Google recommends an honest assessment of whether the content is “helpful, reliable, and people first”, not quick fixes, and says improvements may take “several months for our systems to learn”, sometimes until the next core update.
Step 5: Did demand or the results page change?
If impressions fell with steady positions, check whether people are searching less. Google’s debugging guide suggests Google Trends to see whether interest dropped across the industry. Also search your main queries: new AI Overviews, ads, video or shopping results can take clicks without changing your position. See how to track AI search traffic for what Search Console reports about AI features.
Step 6: Fix, then measure
| Cause | Fix |
|---|---|
| Errors, redirects, noindex, robots.txt | Revert or fix, then request indexing for key URLs |
| Lost internal links or content | Restore them on the affected template |
| Site move | Check every old URL redirects to its equivalent; see the site migration checklist |
| Core update | Improve content quality across the affected sections; expect months, not days |
| Seasonality or demand | Nothing to fix; plan content around the cycle |
| SERP changes | Improve snippets and structured data; see organic CTR |
After technical fixes, re-crawl and compare to confirm they’re live, then watch Search Console for recovery as Google recrawls. For the wider Search Console workflow, see how to use Google Search Console for SEO.
Checklist
- Drop confirmed in Search Console, not just Analytics
- Compared with the previous period and the same period last year
- Clicks, impressions and position read together
- Drop located by page, query, device, country and search appearance
- Site compared with an earlier crawl: status, indexability, titles, links
- Pages with traffic that now error or aren’t indexable fixed first
- Page indexing, Security issues and Manual actions reports checked
- Search Status Dashboard checked for updates around the start date
- Google Trends and the live results page checked for demand and SERP changes
- Fix confirmed with a re-crawl; recovery tracked over the following weeks
Frequently asked questions
Why did my Google traffic suddenly drop?
Google lists six common causes: technical issues that stop crawling or indexing, security issues, spam policy problems, algorithm updates, seasonality or changing search interest, and site moves. A sudden drop across the whole site often points to a technical change; a gradual or section-specific drop more often to rankings or demand.
How do I know if a Google update caused my traffic drop?
Check Google's Search Status Dashboard for updates around the date the drop started. If the timing matches and there's no technical problem, the update is the likely cause. Google says pages that drop after a core update aren't necessarily doing anything wrong; other pages may simply be judged more helpful.
How long does it take to recover from a traffic drop?
Technical problems can recover within days or weeks once fixed and recrawled. After core updates, Google says improvements can take several months to be reflected, and some only show at the next core update.
Should I compare with last month or last year?
Both. The previous period shows when the drop started; the same period last year shows whether it's seasonal. Search Console keeps 16 months of data, which is enough for a year-over-year comparison.
Can a drop in traffic be caused by fewer searches rather than lower rankings?
Yes. If impressions fell but average position held steady, people are searching less, or Google is showing your result less often. Google Trends helps confirm whether interest in your topic fell generally.