Fix it

Traffic dropped overnight: Google update or your own change?

Most explanations for a drop can be tested against a date. This page gives an order of checks, a worksheet for lining up your changes with Google's published update dates, and the cases where the honest answer is that nobody can say.

By Adem ÇakalPublished 3 sources6 min read
Short answer

Pin the exact day clicks fell, then rule out causes from cheapest to most expensive: tracking, a site-wide technical fault, something you changed, seasonality, and only then a Google update. Update dates live on the Google Search Status Dashboard at status.search.google.com. Match your drop date to those dates and to your own change log. Expect some drops to stay unexplained.

The triage tree

Decision tree: check tracking, then Search Console clicks, then site-wide faults, then own changes, then seasonality, then Google updates Did Search Console clicks fall? No: analytics only Tags, consent, filters Yes: whole site or some pages? Sort Pages by clicks difference Whole site, abrupt Server, robots, noindex, hack Some pages Own edits, cannibalization Nothing changed Season, demand, update Work left to right; stop at the first cause you can prove.
Order follows the investigation steps in Google's traffic-drop guide.

Step by step

  1. Confirm the drop is real. Compare Search Console clicks with analytics. Google's guide also points to the Data anomalies page.
  2. Set a long window. Use 16 months and compare year over year, so a seasonal dip does not pass for a penalty.
  3. Find the scope. Sort the Pages table by clicks difference. A single folder or template points to your site; a drop spread evenly across everything points to technical or ranking causes.
  4. Check the cheap faults. Crawl Stats, Page indexing, Manual actions and Security issues are named in Google's guide. A misplaced noindex tag tends to produce a slower decline because pages must be recrawled; test one with the noindex checker.
  5. Check Google Trends for your top queries to see whether demand fell for everyone.

Aligning dates: the worksheet

Build a table with one row per date and three columns: your own changes (deploys, plugin updates, redesigns, title rewrites), the Search Status Dashboard ranking incidents, and the day clicks fell. Google's dashboard lists each ranking incident with its start date and duration, so you can see whether a rollout was still running on your drop date.

DateSourceEventClicks vs prior 7 days
Day -3Your logTheme update deployedFlat
Day 0Search ConsoleClicks fallDown
Day 0 to +13Status DashboardUpdate listed as rolling outCompare

Dashboard entries show a start date and a duration. When we accessed it, the newest ranking entry was a November 2026 core update dated 10 November 2026 with no duration yet, so a drop beginning around that date overlaps a rollout in progress. That overlap is a lead, not a diagnosis. Re-check the dashboard rather than relying on this snapshot.

How to read the match

PatternPoints toNext step
Drop the day after your deployYour changeDiff the change; use the before and after calculator
Drop inside an update window, nothing changedPossible ranking updateWait a few weeks, then review content quality site-wide
Slow slide over months, older articlesContent decayRun the content decay finder
Sharp cliff, all pages, same dayTechnical or manualCheck robots.txt, server errors, Manual actions

Honest limit: Google does not tell individual sites which update affected them, and no public data shows why a given page moved. A date match narrows suspects; it cannot convict one. After a core update Google says to review helpfulness and reliability across the site, and warns that recovery is not guaranteed. If the drop followed a rebuild, read traffic after a redesign or migration.

Questions people ask

How do I know if a Google update caused my drop?

Compare the date your clicks fell in Search Console with the start and duration of updates listed on the Google Search Status Dashboard. A match is a hint, not proof, because your own changes and seasonality can fall on the same dates. Google's own guidance is that nothing may be fundamentally wrong with the content after an update.

Should I change things while an update is rolling out?

Google's guide says to wait a few weeks before reanalysing after an update, since effects can take days to months to show. Fix real faults you find, such as a broken redirect, but avoid broad rewrites based on a guess.

Is the drop in Search Console or only in analytics?

Check both. If Search Console clicks are steady and analytics fell, suspect tracking, consent or a tag change. If both fell, move on to indexing and ranking.

Will recovery be guaranteed if I fix the cause?

No. Google says there is no guarantee that site changes will produce noticeable gains after an algorithmic drop.

Sources

  1. Google Search Central: Debugging drops in Google Search traffic, accessed 2026-11-12.
  2. Google Search Status Dashboard: Ranking incidents, accessed 2026-11-12.
  3. Search Console Help: Performance report (Search results), accessed 2026-11-12.