Why did my website traffic drop? A step-by-step checklist to find the cause

Step 1: confirm the drop is real

Before anything else, check that the traffic actually fell and not just the measurement. A surprising share of “traffic drops” are an analytics tag removed in a redesign, a consent banner change, a new filter, or a seasonal dip that happens every year.

• Compare two independent sources. If your analytics tool shows a drop but Search Console clicks are flat, the problem is tracking, not Google. If both fell together, the drop is real.
• Check for site changes on the day. A theme update, a new cookie banner or a tag manager publish on the same date as the drop is the first suspect.
• Compare year over year. Google's own traffic drop guide suggests selecting the last 16 months in the Performance report to see whether the same dip happens every year, and checking your main queries in Google Trends to see whether interest in the topic itself fell.

A gift shop that loses half its clicks in January has not been penalised. A gift shop that loses half its clicks in the first week of December has a problem.

Step 2: find the shape of the drop in Search Console

Use the Performance report's compare mode to see exactly which part of the site lost clicks. The shape of a drop tells you more than its size.

1. Compare periods

   Open Performance → Search results, choose Compare, and pick “last 3 months to previous period” or “last 3 months year over year”, or a custom range either side of the drop date.

2. Click through every tab

   Look at Queries, Pages, Countries, Devices and Search appearance in turn. Sort by the clicks difference. Google's guide recommends checking whether the change is limited to specific queries, URLs, countries, devices or search appearances.

3. Name the pattern

   Site-wide and sudden points to a technical issue or a manual action. One folder or page type points to a template or indexing change. Many pages sliding a few positions over two weeks points to a ranking update. Clicks down but impressions and position steady points to a changed results page.

Read clicks and impressions before average position. Google says small fluctuations in position can happen at any time, and the core updates page says a move from position 2 to 4 needs no drastic action.

Step 3: check Google's ranking updates

If many pages lost rankings gradually, compare the dates with the official Search Status Dashboard ranking history, not with forum rumours. Google lists every confirmed core, spam and other ranking update there with its start and end date.

Two rules from Google's core updates documentation save a lot of wasted work: confirm the rollout has finished, then wait at least a full week after it completes before analysing your site. Rankings move around during a rollout. If a core update is the cause, there is no single thing to “fix”; Google points you to a self-assessment of whether your content is helpful, reliable and people-first, and says confirming improvements can take several months, sometimes until the next core update. Our 2026 Google updates article covers the policy changes from the same year.

Step 4: rule out manual actions and security issues

Open Security & Manual actions in Search Console and check both reports; it takes one minute and settles two causes for certain.

• Manual actions. A person at Google has found a spam policy violation. Part or all of the site can be demoted or removed. The report names the issue and the affected pages, and you can request reconsideration after fixing it.
• Security issues. Hacked content, malware or phishing pages can trigger warnings in search results that stop people clicking. Hacked sites often show a burst of odd new pages and queries in the Performance report too.

“No issues detected” in both reports means you can stop worrying about a penalty and move on.

Step 5: check indexing and the Page indexing report

If pages disappeared from Google rather than sliding down, the Page indexing report will show it. Look for a jump in “Not indexed” around the drop date and read the reasons: “URL marked ‘noindex’”, “URL blocked by robots.txt”, “Alternate page with proper canonical tag”, “Page with redirect”, “Server error (5xx)”, “Not found (404)”.

Then take two or three of your biggest losing pages from Step 2 and run them through URL Inspection. It shows whether the page is indexed, which canonical Google chose, and the last crawl. If Google picked a different canonical than yours, that page's traffic is now credited elsewhere.

Step 6: look for robots, noindex, canonical and redirect mistakes

A sudden, site-wide cliff that starts the day after a release is almost always a technical mistake, not Google. These are the usual ones:

• A staging robots.txt with Disallow: / pushed to production.
• A noindex meta tag or X-Robots-Tag header left on from development, or added to a template by a plugin setting.
• Canonical tags pointing every page at the home page, at the staging domain, or at the http version.
• A migration or URL change without one-to-one 301 redirects, or redirect chains and loops.
• Content moved behind JavaScript that no longer renders the main text in the HTML.

Google notes that after a site move or URL change, rankings can fluctuate while it recrawls, which can take weeks for medium-sized sites. That is expected; missing redirects are not.

Step 7: check server errors and speed in Crawl stats

Open Settings → Crawl stats and look for spikes in server errors or response time around the drop. The Crawl stats report shows total crawl requests, average response time, crawl responses by type, and host status for robots.txt fetching, DNS resolution and server connectivity. Google says “Server error (5XX)” responses cause availability warnings and should be fixed. A firewall or bot-protection rule that started blocking Googlebot looks exactly like this. The report is available only for root-level properties.

Slow pages are rarely the cause of a sudden drop, but a hosting change that doubled response time can slow crawling. Our Core Web Vitals guide explains how much page speed actually matters for rankings.

Step 8: check whether the results page changed

If impressions and average position held steady but clicks fell, the results page probably changed around you. Search your top losing queries yourself, logged out, on mobile. Look for:

• An AI Overview answering the question above the results. Google's AI features documentation says clicks and impressions from AI Overviews and AI Mode are reported inside the Performance report's “Web” search type, so they do not appear separately.
• More ads, a map pack, a shopping block, videos or a “People also ask” box pushing the first organic result down the page.
• A lost rich result. Check the Search appearance tab: if a rich result type stopped showing, its clicks go with it. FAQ rich results, for example, stopped appearing in 2026.

You cannot undo a changed results page, but you can choose to aim at queries where a click is still worth earning.

Steps 9 and 10: competitors and lost links

When one group of queries slipped a few positions with no technical cause, look at who now ranks above you, and whether you lost links that mattered.

For competitors, search your main lost queries and open the pages that overtook you. Did they publish something newer, more complete or more specific? Is a big brand or a forum thread now ranking where a small blog used to? That is not something to fix in your code; it is a content question. For links, check the Links report in Search Console for top linking sites, and use a backlink tool to see if an important referring page was removed or changed. A single lost link rarely explains a site-wide fall, but it can explain one page.

Symptom, likely cause and where to check

Match what you see to the most likely cause, then go to the report that confirms it.

How MrKeyword catches a drop early

MrKeyword's traffic drop alerts run Step 1 and Step 3 for you every day, from your own Search Console data. Each time a new day of data arrives, it compares the latest 7 days of search clicks with the weekly average of the 4 weeks before them. If clicks fell by 30% or more from a usual week of at least 50 clicks, it emails the workspace owners, and posts to Slack if you connect a webhook.

• The alert names any Google ranking update from the Search Status Dashboard that overlaps the week, or ended in the 7 days before it.
• It lists the pages that lost the most clicks, with their usual weekly clicks and this week's.
• It sends at most one alert a week per site, so a slide that lasts several days is one message.

What it does not do: it does not alert sites under 50 clicks a week, because small sites swing too much week to week; it does not read your analytics tool, so a tracking change will not trigger it; and it does not tell you the cause. It tells you when to start this checklist, and which pages and update to start with.

Questions and answers