Traffic from Google dropped? Find the cause before you change anything

When search traffic falls, the first job is to find out what changed and when, not to fix anything. Google lists several common causes of search traffic drops, and they tend to leave different patterns in Search Console. If you change titles, apps and content in the same week you are trying to diagnose, you lose the ability to tell which change helped or hurt.

A useful diagnostic order: confirm the drop is real, find where it is, note the date it started, and only then look for a cause that matches that date.

Is the drop real?

Analytics and Search Console measure different things. Your analytics tool counts visits that loaded its tag; Search Console counts clicks from Google results, whether or not the tag fired. So compare the two before anything else.

• Analytics down, Search Console clicks flat: the problem is probably tracking. A new theme, a cookie banner, a checkout change or a removed app can stop the tag from firing. Search traffic did not fall; your measurement did.
• Both down from the same day: the drop is real. Continue below.
• Search Console shows a sudden gap for a day or two: check Google's Data anomalies page first. Google lists reporting and logging issues there, and a drop can be a data processing change rather than lost visitors.

Where is it, and when did it start?

Open the Performance report in Search Console, set the date range to the last 16 months and compare the recent period with the previous period and with the same period last year. Google's own guide to debugging traffic drops recommends this, because a year-over-year comparison is what separates a real loss from a seasonal dip.

Then answer three questions:

1. Whole site or a group of pages? Switch to the Pages tab, sort by the change in clicks and see whether the loss is spread across the site or sits in one section: product pages, blog posts, one category.
2. Which country, device or search type? Filter by each. A drop only on mobile, or only in one country, narrows the search a lot.
3. What date? Look for the first day the line bends. Write it down. Every possible cause gets checked against this date.

Also look at position, not only clicks. Google's guide separates small moves (position 2 to 4) from large ones (dropping out of the top results for a wide range of terms). It says small fluctuations can happen at any time and can reverse on their own; a large drop is a reason to assess the whole site, not single pages.

The causes Google lists, and what each looks like

A few notes on reading this table.

Technical issues. In the Page indexing report, a fall in indexed pages with a matching rise in non-indexed pages can mean something now blocks Google: a robots.txt rule, a noindex tag added by a theme or app, or a login wall. Inspect a couple of affected URLs with URL Inspection and test the live version.

Migrations. Google says pages can fluctuate in ranking while it recrawls and reindexes a site with changed URLs, and that a medium-sized site can take a few weeks for Google to notice the change. If a drop starts the week of a platform move, a domain change or a new URL structure, check the move first. The things to check are boring and decisive: does every old URL redirect to its closest new equivalent, and are the new URLs indexed? If you are planning a move rather than recovering from one, the guide to moving a website to new hosting covers the order of steps.

Demand. Put your main queries into Google Trends. If searches for "garden furniture" fell everywhere in October, your traffic falling in October is not a problem to fix.

Check your own changes before blaming Google

Several of the causes above can come from changes you made, sometimes without noticing. Before you read about algorithm updates, list everything that changed on the site in the weeks before the drop date:

• theme or template changes;
• new, removed or updated apps and plugins;
• URL changes, redirects, a new domain or platform;
• new languages, markets or currency versions (these can create new URLs and change which version Google shows);
• removed or merged pages, changed navigation;
• robots.txt, noindex settings, password protection left on after a redesign;
• large edits to titles or descriptions.

If something on this list lines up with the drop date, start there. It is the cause you can confirm and reverse.

Was it a Google update?

Only if the dates match. Google publishes ranking updates with start and end dates on the Search Status Dashboard. Treat an update as a possible cause only when your drop starts inside that window and no change of your own explains it better.

As an example of what to check: on 1 October 2026 the dashboard lists the September 2026 spam update as started on 24 September 2026 and still in progress. A drop that began on 10 September cannot be that update. A drop that began on 25 September might be, but the dashboard will not tell you whether your site was affected; your position data will.

Two cautions. Updates take days or weeks to roll out, so judge the effect only after the dashboard lists the update as complete; for core updates, Google recommends waiting at least a full week after completion before analysing your data. And Google says there is no guarantee that changes you make will produce a noticeable effect in search, with recovery taking anywhere from days to several months. Rewriting the whole site in the week of an update rarely tells you anything.

Rankings or impressions up, clicks down

This pattern confuses people because it looks like success. Google's guide describes the case where impressions stay the same but clicks fall: the title and snippet may no longer be the most attractive result on the page, for example if competitors now show rich results.

Average position can also rise while clicks fall if you start appearing for new, less relevant queries where nobody clicks. Check by filtering the Performance report to the queries that used to bring clicks, not the site total.

Then search those queries yourself and look at the page. What appears above your result now? More ads, a product carousel, a different competitor with star ratings? That is observable, and it tells you whether the fix is your snippet or nothing at all.

Where a rank tracker helps

Search Console is the primary source because it is Google's own data about your site. A third-party tool adds two things it lacks: competitors' positions, and position history in a form that is easier to compare by keyword.

Semrush can help at this stage, after the free checks. Its Position Changes report in Organic Research groups a domain's keywords into new, improved, declined and lost, with history going back up to two years, which is useful for seeing whether a competitor gained exactly where you lost. These are Semrush's estimates from its own data, not your Search Console figures. Its Position Tracking tool records daily positions for keywords you choose, but only from the day you set up the project, so it cannot reconstruct the period before your drop; it is for watching recovery. Its Site Audit crawls your site with Semrush's own bot, which helps find broken redirects or noindex tags after a migration, but it does not show what Google has indexed.

If the drop lines up with a change you made, you probably do not need a paid tool to diagnose it.

What not to do while diagnosing

• Do not change several things at once. Fix the cause you found, note the date, and watch.
• Do not delete or merge pages because they lost traffic, until you know why.
• Do not buy a "recovery package" from anyone who names a cause before seeing your Search Console data.
• Do not rewrite all your content because an update is running, unless its timing and your position data actually point there.