TL;DR Before you look for an algorithm update, check your data. Compare Search Console clicks with GA4 organic sessions for the same pages: if clicks held and sessions fell, the problem is tracking, not rankings. If both fell, segment the loss by page group, device, country and query until you can say what dropped and when, then match that pattern to a cause.
An organic traffic drop starts the same way everywhere: a chart goes down, someone asks why, and the team starts guessing. The guess is usually a Google update, because that is the story everyone has read. Often the real answer is less interesting and faster to fix: a tag that stopped firing, a consent banner that changed, a redirect that lost the referrer.
The order of the investigation matters more than any single check. Confirm the drop, rule out measurement, find where the loss is, and only then look for a search cause.
Step 1: confirm the drop is real
Search Console and GA4 measure different things. Search Console counts clicks on Google's results; GA4 counts sessions its tag records on your site. That difference is what makes them useful together.
| Search Console clicks | GA4 organic sessions | What it means |
|---|---|---|
| Down | Down | People stopped arriving from Google. A search problem. |
| Steady | Down | People still arrive; your tracking stopped counting them. A measurement problem. |
| Down | Steady | Rare. Check for a date range or filter mismatch, or traffic from other search engines filling the gap. |
Compare like with like: GA4 filtered to google / organic, the same pages, the same dates, and leave out the last few days, which both tools are still processing. Some gap between the two is always there; a sudden change in it is the signal. Search Console vs Google Analytics explains the normal reasons they differ.
Also open Security & Manual actions in Search Console. Manual actions are rare, but this is the only place Google tells you about one.
Step 2: rule out tracking
If GA4 fell and Search Console did not, stop the SEO investigation and look at the data. The usual causes:
- A template lost its tag. A release removes the GA4 tag or the tag manager container from product pages, blog posts or a whole subdomain. Those landing pages fall to zero; the rest of the site looks normal.
- A tag manager publish broke page views. A trigger changed, a tag was paused, a variable started returning empty. Check the container's version history for a publish on the day the drop started.
- Consent changed. A new banner, a new default or a broken Consent Mode setup reduces the share of visitors GA4 can measure. Every channel drops at once.
- Organic was reclassified. A redirect that drops the referrer, internal links with
utm_parameters, or a single-page app that loses the original source moves Google visits into Direct, Referral or Unassigned. Total sessions hold; organic shrinks. - Landing pages turned to (not set). Sessions without a page view lose their landing page, so your organic landing report loses rows. See what (not set) means in Google Analytics.
A quick test: if Direct rose by about what Organic lost, start with reclassification. If every channel fell on the same day, start with the tag or consent. If one group of pages fell to zero, start with that template.
Step 3: find where the loss is
If the drop is real, narrow it from "traffic is down" to a sentence you can act on: which pages, which devices, which countries, which queries, since when. In Search Console's Performance report, compare the period before and after the drop and break it down by:
- Page group. A single template change can take down hundreds of URLs that share a path or a layout. If the loss is concentrated in one directory or page type, you have your scope.
- Query type. Filter out your brand name. Non-branded queries falling while branded holds steady points to rankings or search features, not demand for your brand.
- Device. A mobile-only drop points to mobile rendering, Core Web Vitals or mobile-specific search features.
- Country. A drop in one market points to a local update, an hreflang problem or a regional CDN or redirect issue.
- Impressions versus clicks. Impressions down means you lost visibility. Impressions steady and clicks down means the results page changed around you.
Use year-over-year comparisons when the business is seasonal, so a normal summer dip does not start an investigation.
Step 4: match the pattern to a cause
| What you see | Likely cause | Where to check |
|---|---|---|
| Search Console clicks steady, GA4 sessions down | Tracking or consent | Tag on templates, tag manager history, consent rate |
| Organic down by about what Direct gained | Referrer lost or source overwritten | Redirects, internal UTMs, single-page app routing |
| Sudden site-wide drop on one date | Google update or a technical change | Google Search Status Dashboard, robots.txt, noindex, release notes |
| One directory or template down | Template change, canonical or noindex error | URL Inspection, the template's head, recent deploys |
| Pages leaving the index | Crawling or indexing problem | Search Console Pages report, sitemaps, robots.txt |
| Impressions steady, click-through rate down | Search features taking the click | The live results page for your top queries, AI Overviews |
| Slow decline over months | Content decay or stronger competitors | Query and page trends over 6 to 12 months |
| One country or device only | Local update, hreflang, rendering or performance | Country and device reports, Core Web Vitals |
Google updates. Check the Google Search Status Dashboard for a confirmed update within a few days of the drop. If one landed and the loss is spread across queries and pages rather than concentrated in a template, the cause is probably ranking.
Technical changes. Look at what shipped: a robots.txt edit, a noindex left from staging, canonicals pointing to the wrong URL, a migration with redirect chains or 404s. These show up as pages leaving the index in Search Console's Pages report, usually within days.
Search features. When AI Overviews or other features appear for a query, clicks can fall while your position holds. Look at the results page for your highest-traffic queries before you call it a ranking loss.
Content decay. A slow slide over months is rarely technical. It is pages going out of date or competitors publishing better ones, and the fix is editorial.
Step 5: write it down and fix in order
Put every event of the month before the drop on one timeline: releases, tag manager publishes, consent changes, content changes, migrations, Google updates. Put the traffic on the same timeline. The cause is usually the event that lines up with the first day of the drop and with the segment you found in step 3.
Then fix by impact: a noindex on a whole template goes first, a few decayed posts can wait. And mark the affected dates as incomplete in your reports, so nobody compares against them later as if they were real.
Catch the tracking causes the day they happen
Most of the measurement causes above are invisible until someone notices a chart a week later. Trackingplan watches them as they happen: it reads the hits your site sends, and its acquisition view shows your landing pages, referrers, sources and mediums from real visitors, independent of how GA4 processes them. You can set a warning on a landing page or a referrer, so a template that stops sending page views or a referrer that disappears shows up the same day, with the release or tag change that caused it still fresh.
When organic traffic drops, the first question is not what Google did. It is whether your data still tells the truth.
Frequently asked questions
How do I know if an organic traffic drop is real?
Compare Google Search Console clicks with GA4 sessions from google / organic for the same pages and dates. If both fall, people really stopped arriving from Google. If Search Console clicks are steady and GA4 sessions fall, the visitors are still coming and your tracking stopped counting them.
What causes a sudden drop in organic traffic?
On the search side: a Google update, pages dropped from the index by a noindex, robots.txt or canonical change, a migration with broken redirects, or a new search feature such as AI Overviews taking the clicks. On the measurement side: a missing analytics tag, a consent change, organic traffic reclassified as Direct or Referral, or a tag manager publish that broke page views.
Why is GA4 showing fewer organic sessions than Search Console clicks?
Some gap is normal, because the two tools count different things. A gap that grows suddenly is not: it usually means a template lost its tag, a consent change cut measured sessions, or organic visits are being classified as another channel.
How long does it take to recover from an organic traffic drop?
It depends on the cause. A tracking fix restores the data from the day it ships, although the missing days stay missing. A technical fix such as removing a stray noindex needs Google to recrawl the pages. A drop after a core update usually needs content changes and another update before rankings move.