Traffic dropped 80% overnight: triage before theories.
No manual action. No warning email. The dashboard just fell off a cliff, and everyone around the table has a theory. Payroll does not care about theories. The first fifteen minutes should be spent ruling things out, not arguing.
The 15-minute triage
- Minute 1–3 — Is it real? Check a second data source. If analytics says zero but the server logs show visitors, your tracking tag broke — celebrate and fix the tag.
- Minute 3–6 — Search Console. Coverage report and manual actions. A spike in “excluded” pages points to indexing; an empty manual-actions tab rules out the scariest option.
- Minute 6–9 — Fetch your own homepage the way a crawler does. Status code, robots.txt, noindex tags. Site migrations leave landmines: a staging robots.txt shipped to production is a classic.
- Minute 9–12 — Check the SERP by hand. Search your brand. Still there? Then rankings dropped for non-brand terms — algorithm territory. Gone entirely? Indexing or penalty territory.
- Minute 12–15 — Check the weather. Was a core or spam update rolling out? If yes, the response is analysis, not panic edits — changing everything mid-update destroys the evidence of what actually hurt you.
When “wait and see” becomes negligence
Waiting is correct while an update settles. It stops being correct the moment you have a confirmed technical cause — a bad canonical, a noindex, a hacked section. The skill is knowing which situation you are in, and that is exactly what the triage tells you.
Questions people ask
Why did my website traffic drop overnight?
The usual suspects: broken analytics tracking, an indexing or robots.txt error, a redirect mistake after a migration, a security flag, or an algorithm update. Each leaves a different fingerprint in Search Console and server logs.
Should I make changes during a Google core update?
Generally no. Large mid-update changes destroy your ability to see what the update actually affected. Diagnose first; act on confirmed technical causes immediately, algorithmic ones deliberately.
How do I know if the drop is a tracking problem?
Compare a second source - server logs, CDN analytics or Search Console clicks. If they show normal traffic while your analytics shows zero, the measurement broke, not the visibility.
Why did my website traffic drop overnight?
The usual suspects: broken analytics tracking, an indexing or robots.txt error, a redirect mistake after a migration, a security flag, or an algorithm update. Each leaves a different fingerprint in Search Console and server logs.
Should I make changes during a Google core update?
Generally no. Large mid-update changes destroy your ability to see what the update actually affected. Diagnose first; act on confirmed technical causes immediately, algorithmic ones deliberately.
How do I know if the drop is a tracking problem?
Compare a second source - server logs, CDN analytics or Search Console clicks. If they show normal traffic while your analytics shows zero, the measurement broke, not the visibility.
Scenarios are composites built from real, common situations — not client stories. We publish no metrics we cannot prove.