Organic traffic dropped? A step-by-step way to find the cause

A drop in organic traffic creates urgency, and urgency leads to guesswork: rewrite the homepage, disavow links, blame the latest algorithm update. Most drops have a specific, findable cause, and the fastest way to it is a calm, methodical investigation.

Google publishes its own guide to debugging drops in Search traffic. The steps below follow the same logic, in the order that eliminates the most likely causes first.

Step 1: confirm the drop is real

Before investigating search, rule out measurement:

• Compare analytics with Search Console. If analytics shows a drop but Search Console clicks are stable, the problem is probably tracking: a consent banner change, a broken tag, a new analytics setup or a redirect that strips parameters.
• Check for reporting issues. Search Console occasionally has data delays or logging issues, which Google notes in its reports.
• Check the date range and comparison. A drop against a seasonal peak may not be a drop at all.

Step 2: describe the shape of the drop

Write down the pattern before forming a theory:

• Sudden or gradual? A cliff on a specific day points to a change. A slow decline points to competition, demand or content aging.
• Sitewide or specific? All pages, one section, one template, or a handful of URLs.
• Impressions or only clicks? If impressions are stable and clicks fall, visibility hasn't changed but people are clicking less.
• All queries or some? Branded and non-branded searches behave differently. A drop in branded traffic often reflects demand, not SEO.

Step 3: check what changed, on your side and Google's

List everything that happened around the start of the drop:

• site releases, template changes, CMS or plugin updates;
• redesigns, migrations, URL or navigation changes;
• robots.txt, noindex, canonical or redirect changes;
• hosting, CDN, firewall or bot-protection changes;
• confirmed Google updates, which are listed on the Google Search Status Dashboard.

If a release lines up with a sudden drop, start there. It is the most common cause of sudden drops, and the easiest to fix.

Step 4: segment in Search Console

Open the Performance report, set a comparison and slice the data. Google recommends several of these views specifically:

• Extend the date range to the last 16 months to see whether the pattern repeats every year.
• Compare periods: the last three months against the previous period, and against the same period last year.
• Filter by search type: web, image, video and news traffic can move independently.
• Sort the pages table by click difference to see whether the loss is spread across the site or concentrated in a few pages.

Then break it down further by query, country and device. A loss limited to one country, one device type or one group of pages narrows the cause dramatically.

Step 5: check the technical and security reports

In Search Console, look at:

• Page indexing: did important pages move from indexed to not indexed?
• Crawl stats: did server errors, response times or crawl requests change?
• Manual actions and Security issues: rare, but decisive when present.
• URL Inspection on a few affected pages: can Google fetch and render them, and which canonical did it select?

Step 6: look at the results pages themselves

Search your most important affected queries and look at what has changed:

• New features such as AI Overviews, video carousels, forums or shopping results can reduce clicks even when your position is unchanged.
• New competitors or a competitor's improved page.
• A different kind of result ranking, for example guides instead of product pages, which means Google has changed its reading of the search intent.
• Your own title or snippet being rewritten in a less compelling way.

Step 7: check demand

Search interest changes. Seasonality, news events, economic shifts and changing behavior all move traffic without anything being wrong with your site. Google Trends shows whether interest in your main topics fell. If the whole market is down, your share may not be.

Match the pattern to the likely cause

Pattern	Likely cause	First place to look
Sudden sitewide drop to near zero	Noindex, robots.txt block, server outage, manual action or security issue	Page indexing, robots.txt, Manual actions, Security issues
Sudden drop in one section or template	A release changed that template	Recent deployments, rendered HTML, canonicals
Drop starting on a confirmed update date, across many pages	Google reassessing quality or relevance	Content quality and helpfulness across the site
Gradual decline over months	Competition, content aging or demand	Competing results, freshness, Google Trends
Impressions steady, clicks down	Results page changes, or a less compelling title	The live results page, CTR by query
Drop only in one country or device	Localized technical or search changes	Country and device filters, mobile rendering
Drop that repeats every year	Seasonality	16-month view, year-on-year comparison

Act in proportion to the cause

• Technical and security causes: fix them immediately, verify with URL Inspection, and use Validate fix in the relevant report.
• Small position changes: Google advises against radical changes in response to small fluctuations. They are normal.
• Large drops after an algorithm update: Google suggests stepping back and assessing the site's helpfulness and reliability as a whole. Improve content where it genuinely falls short. Rewriting everything overnight rarely helps and makes it harder to learn what worked.
• Demand changes: adjust expectations and reporting, and look for adjacent topics where demand is growing.

Record what you find

Whatever the cause, write it down with dates: what happened, what you changed and when. The next time traffic moves, that record turns a stressful investigation into a quick comparison.