Why did my traffic drop: a diagnostic checklist in order

Work through the causes in order of likelihood and you will usually find a traffic drop within an hour. The order is: broken tracking, then the comparison window you chose, then a narrow loss on a few pages or queries rather than the whole site, then a change your own team shipped, then a change in how the results page looks for your queries, then a Google ranking update, then competitors, and last of all a manual action. Most drops land in the first four, and most people start at the sixth.

Before any of that, settle what dropped. Open Search Console and your analytics side by side and compare the same dates. The four combinations below point you straight at a cause.

What you see	What it points to
Sessions down in analytics, Search Console clicks steady	Tracking, or a different channel. Not search
Impressions steady, clicks down, position steady	The results page changed. You are still shown and chosen less
Impressions down, position steady	Fewer searches, or you lost a feature you used to appear in
Impressions down and position down	A genuine ranking loss. Now find out on which pages

1. Tracking

Start here, because it is the most common cause and the quickest to confirm. Check these in order: the analytics tag still present on the templates that changed in your last release, the consent banner and what it blocks, any new filters or bot settings, and whether a tag got dropped during a deploy or a theme update.

The fastest confirmation is the real time report with your own visit in it. If Search Console clicks are flat while analytics sessions fell, you have found your answer and the rest of this page is optional.

2. The comparison window

Compare the same length of period, the same days of the week, and the same point in your season. Many apparent drops are a month with fewer working days, a holiday week, a dashboard that quietly switched to last 28 days, or a comparison against an unusual spike. Pull a two year view of the same metric and look at the shape before concluding anything.

3. Narrow it before you theorise

Use the comparison mode in the Search Console performance report and run the same date comparison four times, grouped by page, by query, by country and by device. One of those four almost always isolates the loss.

What each pattern means: one page losing, with the rest flat, points to that page or its query. A template full of pages losing together points to a code change. One country falling points to a local competitor or a regional results change. Mobile falling alone points to a rendering or speed problem on mobile templates.

4. Your own changes

Get the deploy log for the two weeks before the drop and check it against this list. These are the changes that move traffic most.

• A noindex tag applied by a template, a plugin or a staging setting that shipped to production.
• A robots.txt rule blocking a directory. Confirm with the robots.txt report in Search Console.
• Canonical tags pointing at the wrong URL, often after a URL structure change.
• Redirects that became chains or loops, or a migration where some old URLs were never mapped.
• A navigation or footer change that removed internal links to a whole section.
• Pagination, filtering or faceted URLs changed, so a large set of pages is no longer linked.
• A speed or layout regression from a new script, measurable in your Core Web Vitals field data.
• A domain, protocol or subdomain change where Search Console is still reporting on the old property.

5. The results page changed

When impressions hold and clicks fall, you are still being shown and chosen less often. The usual causes are a new feature above you taking the click, your title or description rewritten in a way that reads worse, or a competitor winning a rich result for the same query. Check the queries that lost clicks, search them yourself, and look at what sits above you now.

6. A Google ranking update

Compare your drop date against Google's own records: the Search Status Dashboard for incidents and the ranking updates page for confirmed updates. A drop that starts on an announced update date, across many pages at once, is a systemic reassessment rather than a bug.

The response that works is the same either way: find the pages that lost, read them as a buyer, and make them specific, accurate and genuinely more useful than what now outranks them. Recovery comes from the pages improving, so that is where to put the effort.

7. Competitors and lost links

Search your main queries and look at who is new in the top results. Then check whether links you used to have are still live, since a site redesign elsewhere can quietly remove a link that was holding a page up. Ahrefs, Semrush and Moz all report lost referring domains, and any of them answers this question in minutes.

8. Manual actions and security

Last on the list because it is rare, and worth two minutes because it is unambiguous. Open the manual actions and security issues reports in Search Console. Both are usually empty, and when either is not, it names the problem precisely.

The one hour version

• Confirm the analytics tag is firing, with your own visit in the real time report.
• Compare Search Console clicks and impressions for the same dates. Decide whether this is a search problem at all.
• Run the Search Console comparison grouped by page, then by query. Write down what lost.
• Read the deploy log for the fortnight before the drop.
• Check the robots.txt report, and the manual actions and security reports.
• Check your drop date against the Search Status Dashboard and the ranking updates page.
• Search your three most valuable queries yourself and look at what is above you.

What this page covers, and what it leaves out

This page covers diagnosing a drop in organic search traffic in order of likelihood. For paid, email and social declines, go to each platform's own reporting first. For recovery work once you have found the cause, use a technical or content guide for that specific fix.

why did my traffic drop: asked and answered

How much of a drop is worth investigating?

Set the threshold against your own weekly variation. Pull a year of weekly data, see how much it normally moves, and investigate anything outside that band. A site with steady traffic should look at a ten per cent move. A small site swinging widely week to week should wait for a trend.

My rankings are the same but traffic fell. What happened?

Impressions steady with clicks down means the results page changed around you, so check what now appears above your result for those queries. Also check whether your titles and descriptions were rewritten, since that changes how often people choose your link.

How long does recovery take?

A technical fix such as a wrongly applied noindex tag recovers as soon as the pages are recrawled, which is days for important pages and you can request indexing to speed it up. Recovery from a ranking update follows the pages getting better, so treat it as a programme of work with monthly reviews rather than a wait.

Should I contact Google?

Reserve that for a manual action, where Search Console gives you a reconsideration request. For everything else, the answer is in your own data, and this checklist gets you to it faster.

Could my traffic drop be seasonal?

Check it directly. Compare the same weeks across two or three years in Search Console, and look at the query in Google Trends. Seasonality shows up as the same shape repeating in previous years.

When the drop is a question that moved

The checklist runs in order of likelihood: tracking, dates, indexing, updates. One more cause is slow and quiet. Some of your buyers now ask an assistant first and never click through, so visits fall even though rankings hold.

You can test for it. Take the queries that lost traffic and ask them as questions in three assistants, noting who is named. AI Knows Us runs that test on a schedule, which helps you tell a lost ranking from a changed way of asking.