Why did my organic traffic drop overnight? A triage checklist
Organic traffic dropped overnight. Work the list: indexability, robots.txt, canonicals, status codes, sitemap, a search update, or a tracking break. How to check each in under a minute and what the result means.
Organic traffic can drop overnight for a mechanical reason: a noindex directive, a robots.txt rule, a changed canonical, a new 404 or redirect, or a broken tracking tag. It can also drop because a search update moved the rankings across many sites. The fastest way to tell which is to check the live page the way a crawler does, then work the checklist in order; each step takes under a minute.
Search Console reports on Google’s crawl-and-index schedule, measured in days. The page itself answers now. If a step finds a mechanical cause, you have a fix, not a mystery.
Is the page indexable right now?
Check the meta robots tag and the X-Robots-Tag header on the live page, the way a crawler reads them. Run the URL through the indexability checker, which reads both in one request; the X-Robots-Tag checker reads the header alone.
If either source says noindex, the drop has a mechanical cause: the page is out of the index for a real reason, not an algorithm reason. Fix it at the source, redeploy, and re-check until both read clean. The full fix sequence is in this guide.
Did robots.txt change?
A new Disallow line can remove a whole section from crawling overnight. Fetch the live robots.txt and check the effective permission for the dropped paths, not the raw text: a Disallow in a Googlebot group blocks Google while other crawlers keep going.
Fetch https://yourdomain.com/robots.txt directly and read the group that applies to Googlebot, then check whether the dropped path matches a Disallow line. If a permission flipped from allow to disallow, that is the cause. Robots.txt changes are a classic silent deindexer; remove the line and the section comes back on Google’s schedule.
Did canonicals change?
A wrong or changed canonical reroutes the page’s signals to a different URL. Check the canonical on the dropped URLs in view-source, under <link rel="canonical" href="...">.
The indexability checker shows it as well. A changed canonical is the page telling Google a different URL is the real one, so the rankings and the traffic move with it. A self-referencing canonical on the right URL is healthy; a canonical pointing elsewhere explains the drop.
Did status codes or redirects change?
A page that now returns 404, 410, or a redirect chain it did not have before will leave the index. Check the HTTP status and the chain on your money pages with curl -sI https://example.com/pricing, or use the indexability checker, which shows both in one request.
A 4xx or 5xx on a money page is a mechanical cause, not an algorithm change. Fix the status or shorten the chain, and the URL can re-enter the index on Google’s schedule.
Did the sitemap break?
Fetch the sitemap file directly and confirm it returns 200 and still lists the dropped URLs. If the URL list or the lastmod dates are stale, that is a discovery problem, not an indexing one.
There is no dedicated sitemap tool yet; checking the file yourself takes under a minute. A sitemap that 404s or drops URLs slows rediscovery, but it does not by itself deindex a page. If the pages are healthy and just missing from the sitemap, fix the sitemap and move on.
Is it a search update instead?
If none of the above changed, consider the index itself. A search update tends to move rankings across many sites at once; a change you caused hits your pages specifically.
Check whether the drop is concentrated on your site or looks uniform across the sites you manage. There is no number to prove this either way; reason from the pattern. Search Console shows impressions and positions on Google’s schedule, which is slower than the live page, so it confirms the direction, not the day.
Is it analytics rather than real traffic?
Before assuming organic loss, confirm the measurement. Did the tracking code or tag change? Does the analytics tool have a data gap? Does a second source, such as Search Console or the server logs, agree?
A tracking break makes traffic look gone while the site is fine. If the page is indexable, robots.txt allows it, the canonical is right, the status is 200, and two data sources disagree, the drop is a measurement problem, not a ranking problem.
The pages can break at 3am and the chart only shows it days later. stillindexed.com checks your pages’ SEO directives and alerts you on Telegram and email when something changes. Starter checks every 30 minutes, Agency every 15: https://app.stillindexed.com/auth/request