Why did my organic traffic drop? How to find the change behind it

Why did my organic traffic drop?

Most organic drops come from one of six causes, and Google's own guide to debugging Search traffic drops lists them: algorithmic updates, technical issues, security threats, spam violations, seasonality or changing interest, and site moves. Your job is to find which one applies before you change anything.

The trap is that several of these happen at once. A core update rolls out the same week your developer ships a new template, while a cookie banner change cuts what GA4 records. If you react to the wrong cause, you undo a good change and keep the bad one.

So treat a drop as a question with a short list of suspects:

• Google changed: a core update or another ranking system update.
• Your site changed: a migration, new URLs, redirects, robots.txt, noindex tags, templates, titles, internal links, removed pages, server errors.
• Your measurement changed: GA4 tag, consent setup, filters, channel grouping.
• Demand changed: seasonality, a news event, fewer people searching the topic.
• Something is wrong: a manual action or a security issue.

The rest of this article is the order in which to rule each one in or out.

Is the drop real or a tracking problem?

Check Search Console before GA4. Search Console counts impressions and clicks on Google's side, so a broken analytics tag, a consent change or a new filter does not change it.

1. Open the Performance report in Search Console for the same dates as the GA4 drop.
2. If Search Console clicks are flat but GA4 organic sessions fell, the visitors are still arriving. Look at tracking: tag removed from a template, consent banner change, GA4 data filters, or channel grouping edits. Our article on GA4 traffic drops walks through those checks.
3. If both fell on the same day, the loss is real. Continue with the steps below.

One more detail: Google says sites that appear in AI features such as AI Overviews and AI Mode are counted in the Performance report under the Web search type. You cannot split those clicks out there, so don't assume a fall in Web clicks is only classic rankings.

How do I tell a Google update from my own site changes?

Compare the drop date with the Google Search Status Dashboard and with your own change history. If the drop starts inside an update's rollout window and nothing on your site changed, the update is the lead suspect. If it starts the day after a release, start with the release.

Google makes broad core updates several times a year. Its core updates documentation recommends waiting at least a full week after an update completes before analysing your site in Search Console, and says recovery after improvements can take anywhere from a few days to several months.

The shape of the drop also tells you a lot:

The position examples come from Google's guide, which describes a move from 2 to 4 as a small drop and 4 to 29 as a large one, and advises against radical changes when pages still perform well.

Which site changes most often cause an organic traffic drop?

The changes that do the most damage are the ones that change what Google can crawl, index or understand. These are worth checking line by line against the drop date:

• Migrations and URL changes: new domain, HTTPS move, new URL structure, merged sections. Google's site move guide says you may see ranking fluctuations while Google recrawls, that medium-sized sites can take a few weeks or more to show the new URLs, and that you should keep redirects for generally at least one year.
• Blocking changes: a robots.txt rule or a noindex tag copied from staging to production.
• Redirect changes: redirects removed, chained, or pointing to the home page instead of the matching page.
• Template changes: new titles, headings, or content moved behind tabs or scripts across a whole page type.
• Internal links: a menu or footer redesign that removed links to important categories.
• Content pruning: pages deleted or merged without redirects.
• Server and hosting: downtime, slow responses or errors that show up in the Crawl stats report.

Most of these are made by developers, SEO consultants or a CMS plugin update, not by the person who reports on traffic. That is why the cause is often invisible to the marketer who sees the drop.

How do I isolate the cause of an organic traffic drop?

Put every change from the days before the drop on one timeline, rule out tracking first, then test one hypothesis at a time. This is the same method we use for any metric in our root cause analysis guide.

1. Pin the start date. In the Performance report, find the first day clicks or impressions fell, not the day someone noticed.
2. Collect changes from the 14 days before it. Site releases, CMS and plugin updates, redirects, robots.txt edits, content removed, hosting changes, tracking changes, plus Google updates from the Search Status Dashboard and any external event.
3. Rule out measurement. Search Console versus GA4, as above.
4. Segment the loss. Filter by page, query, country, device and search type. A drop limited to one folder points to a change in that folder. A drop across every page type points to Google or a site-wide change.
5. Match segment to change. If only blog URLs lost impressions and the blog template changed on that date, that is your first hypothesis.
6. Test one hypothesis. Use URL Inspection on a few affected pages, check the live robots.txt, follow the redirects. Fix one thing, note the date, and watch the affected segment.

Example: a site loses 30% of organic clicks over two weeks. Search Console confirms it, so it is not tracking. The loss sits in /products/ URLs only. The timeline shows a category filter release on day one that added a noindex to filtered pages and, by mistake, to the main category pages. Removing the tag from category pages is the single fix to test first. (Illustrative example.)

If you need to explain the drop to a client while you investigate, our guide on how to explain a conversion drop to a client has a structure that works for traffic too.

How do I use Search Console to narrow down an organic traffic drop?

Use the date range, Compare and filters in the Performance report, then mark the change dates with annotations. Google's debugging guide suggests these views:

• Last 16 months: shows whether the same dip happened last year (seasonality).
• Compare: last 3 months against the previous period, or year over year.
• Filters: search type, page, query, country and device, and the average position metric, to see where the loss sits.

Then check the Page indexing, Crawl stats, Manual actions and Security issues reports for anything that started near the drop date.

Search Console also lets you add custom annotations to Performance charts. According to Google's help page, notes can be up to 120 characters, a property can hold up to 200 annotations, they are shared with every owner and full user, and annotations older than 500 days are deleted automatically. They also don't show in comparison mode. Use them, but don't rely on them as your only record. For analytics, the same idea is covered in our GA4 annotations guide.

How do I prevent the next unexplained traffic drop?

Make every change that can affect organic traffic visible to the person who reports on it, on the day it happens. Most drops take days to diagnose because nobody can say what changed.

• Log site releases, redirects, robots.txt and template changes with date, owner and reason.
• Add Google update start and end dates to the same log.
• Include tracking changes, so you can rule them out in minutes.
• Review the log every time clicks move more than your normal weekly range.

A shared marketing change log does this job. Changeline keeps SEO, site, tracking and ad changes for each client on one to-scale timeline, so the question "what changed before the drop?" has an answer. It is free while in early access: start a change log in Changeline.