Guide

How to Diagnose a Traffic Drop in Google Search Console

Search Console shows you what Google recorded: which pages lost clicks, which queries went quiet, and whether anything broke in crawling or indexing. Read it in the right order and the cause usually narrows fast.

To diagnose a traffic drop in Google Search Console, open the Performance report, compare the weeks before and after the drop, and split the loss by page, query, country and device. Then check the Pages report for indexing problems and Security and Manual actions for penalties. The pattern of what fell tells you where to look next.

Start with the Performance report

Open Search Console, choose Performance, then Search results. Set the date range to Compare, and pick equal periods before and after the day traffic fell. Turn on clicks, impressions, average CTR and average position.

Two questions come first. Did impressions fall, or only clicks? And did the loss start on one date, or bleed out slowly?

What you seeWhat it usually points to
Impressions and clicks both fall on one dayA ranking change, an indexing problem, or a technical fault that started that day
Clicks fall, impressions holdLower positions, a changed results page, or weaker titles and snippets
A slow slide over weeksContent decay, stronger competitors, or a gradual crawl problem
One page or one folder collapsesA page level issue: noindex, redirect, canonical, or removed content
Every page falls by a similar shareA sitewide cause: a core update, a penalty, tracking, or a server problem
Reading the shape of a traffic drop

Split the loss to find where it sits

Use the Pages tab, sorted by the click difference. Note the pages that lost the most. Then open the Queries tab for the same comparison. Ask whether the lost queries cluster around one topic, one page type or one intent.

Add filters one at a time. Filter by country, then by device. A drop that only appears on mobile suggests a rendering or usability fault. A drop in one country can mean a regional change, or a hreflang or redirect fault.

Branded queries deserve a separate look. If searches for your own name held steady while everything else fell, demand is intact and you are looking at rankings. If branded searches fell too, demand itself dropped, which is a different problem.

Check indexing, crawling and penalties

Rule out the breaks

Where Search Console shows damage

Pages report

Look for a jump in Not indexed, Excluded by noindex tag, Blocked by robots.txt, or Page with redirect.

Crawl stats

Under Settings. A drop in crawl requests or a rise in server errors can mean Google could not reach the site.

Manual actions

Open Security and Manual actions. A listed action explains a sudden sitewide fall.

URL Inspection

Test a lost page. Check that it is indexed, the canonical is right, and the live page renders.

Sitemaps

Confirm the sitemap still loads and lists the pages that matter.

Core Web Vitals

A sitewide jump in poor URLs after a release can be a symptom of a bigger fault.

If any of these shows a change on the date of the drop, you have a lead. Many drops are self inflicted: a noindex tag left on after a launch, a robots.txt rule that blocks a folder, or a redirect that sends pages to the wrong place. Our technical SEO fixes work starts with exactly these checks.

Match the date to your own change log

Write down every change near the drop date: a redesign, a plugin update, a hosting move, a robots.txt edit, new templates, a migration. Then compare it with Google's public list of ranking updates on the Search Status Dashboard.

Both lists matter. A drop on the day of a deploy and not on an update date is almost always yours. A drop on an update date with no site changes is more likely a ranking reassessment. Our guide on seasonal dips versus algorithm hits shows how to separate normal demand swings from real losses.

Confirm it is not a measurement problem

Before you act, check that traffic really fell. Compare Search Console clicks with your analytics. If analytics dropped but Search Console did not, a tracking tag may have broken. Search Console and analytics will never match exactly, but they should move in the same direction.

Write down the evidence

Finish with a short record: the date, the size and shape of the loss, the affected pages and queries, what changed on the site, and what Search Console reported. That record is the diagnosis. Without it, any fix is a guess. For the wider list of causes, read why your website traffic dropped.

When to call for help

Call for help when the evidence points in two directions, when the site is so large that the report row limits hide the pattern, or when you have fixed the obvious fault and traffic has not moved. Our traffic drop recovery service starts from this same evidence. Send us what you have through a free SEO triage and we will tell you what the data shows and what to do next. If your question is about a sudden overnight fall, see our short answer on why rankings drop overnight.

FAQ

Questions owners ask us

How far back should I compare in Search Console?

Compare the same number of days before and after the drop. Then compare against the same dates a year earlier if you have the data, so a seasonal pattern does not fool you. Search Console keeps about 16 months of Performance data.

What if clicks fell but impressions did not?

Your pages still appear, but fewer people click. That points to lower positions, a change in the results page such as an AI Overview or new features pushing you down, or weaker titles. Check average position and click through rate by query before you assume anything is broken.

Can Search Console tell me which update hit me?

It cannot name an update. It gives you the date and the shape of the loss. You then compare that date with Google's published list of ranking updates. Our guide on how to tell if a Google update hit your site covers that step.

Get started

Tell us where it hurts.

Your site, what changed and when. We reply with a first read on the cause.