Why did my website traffic suddenly drop?
Diagnose a traffic drop by its shape before you guess at its cause. An overnight cliff to near zero is almost always technical — a stray noindex, a broken robots.txt, a failed migration, or a manual action. A clean step-down on a single date points at either a dated algorithm update or something you shipped that day, and a slow slide over weeks is usually decay and competition rather than an event at all. Check the causes you control first: they are both the most common and the fastest to reverse.
Read the shape of the drop before you guess the cause
A traffic drop is not one problem, and the chart tells you which one you have before you touch anything. Open Search Console, set the Performance report to the full 16-month range, and look at clicks and impressions on the same axis. The shape narrows the cause set enormously, and it costs you two minutes. Skipping this step is how founders end up rewriting titles for a problem that was a robots.txt line.
| What the chart looks like | Most likely cause | First thing to check |
|---|---|---|
| Overnight cliff to near zero | Technical or a manual action — not a ranking change | Manual actions report, then Pages → why URLs aren't indexed |
| Step down on one date, then flat | A dated algorithm update, or something you deployed that day | Your own deploy history for that date, before any update tracker |
| Impressions flat, clicks fell | You still rank; something above you is taking the click | The live results page for your top queries — an AI Overview or a new snippet |
| Slow slide over several weeks | Decay and competition, not an event | Whether the losing pages are old and haven't been revised |
| One page, one country, or one template | Page-level or template-level, not site-wide | What those URLs share — a template, an hreflang pair, a canonical |
Check what you changed before you check what Google changed
Self-inflicted drops outnumber algorithmic ones, and they are the only kind you can fix the same afternoon. Work through this list against your deploy history for the week before the drop, not the week of it — indexing changes surface with a lag.
- A noindex or a robots.txt rule that escaped staging The single most common cause of a cliff. A staging configuration promoted to production, or a CMS toggle flipped by someone who did not know what it did. Fetch your live robots.txt and view the source of a real page before you believe anything else.
- A migration or a redirect chain Changed URLs without 301s, redirects pointing at a redirect, or redirects landing everything on the homepage instead of the matching page. Each of those loses most of the signal the old URL had earned.
- A template edit Titles, headings and internal links usually live in a template, so one commit can change them across thousands of pages at once. If the drop is confined to pages sharing a layout, look at the layout.
- Canonical drift A template that hardcodes one canonical across every page tells Google your site is a single document. A canonical tag that points somewhere unintended consolidates your traffic onto the wrong URL, and the pages it points away from quietly stop ranking.
- New pages competing with your old ones Publishing several pages around one query splits the signal between them and can pull all of them down together. That is keyword cannibalization, and it looks like a mystery drop on pages you never touched.
Was it actually an algorithm update?
Two tests separate an update from everything else. First, is the loss spread across your whole site or concentrated in a subset? Core updates tend to re-evaluate a site broadly, while a technical fault usually clusters on whatever shares the broken thing. Second, do the dates line up with a confirmed rollout? Google announces core updates and gives start and end dates, and a rollout takes weeks, so a drop that happened between one day and the next is rarely one.
If it genuinely is an update, there is no switch to flip and no penalty to appeal. The recovery path is the slow one: improve the pages that lost the most, and expect the next update rather than a same-week rebound. That is a months-long horizon, which is the same one SEO works on generally — so it is worth being certain before you commit a quarter to it.
Make sure the drop is real before you act on it
Some drops are in the measurement, not the traffic, and those are the expensive ones to chase. A tag that stopped firing after a deploy, a consent banner that started blocking your analytics, a bot filter that changed, or a reclassification of where your visits came from can all move a chart without a single reader changing behaviour. Confirm the drop in a second, independent source — Search Console clicks and your analytics sessions should fall together — before you accept it.
This part is from operating agentceres.com rather than from documentation. When we joined our own Search Console data to our product analytics to find which organic pages actually produced signups, our first pass classified a session as organic by looking for Google in the referrer. That pattern also matches the Gmail app: every time someone opened one of our own login emails on a phone and tapped through, the visit was filed as Google organic. Removing those rows changed the shape of the chart, not only its total — and it would have looked like an organic collapse on any day we sent fewer emails. A second, smaller surprise from the same week: Search Console's site-wide total for a period runs a couple of percent above the sum of its per-page rows, because the two are aggregated differently rather than one being truncated. Two numbers from the same tool can legitimately disagree, so a small wobble is not a drop.
- Confirm it in two independent sources; a single chart is a claim, not a finding.
- Check the manual actions report first — it is the one cause with a formal appeal, and it takes ten seconds to rule out.
- Read your own deploy history for the days around the drop before you read any algorithm-update tracker.
- Compare like periods. A month against a month, not a partial current week against a full previous one.
- If impressions held and only clicks fell, you have a results-page problem, not a ranking problem.
FAQ
- How long does it take to recover from a traffic drop?
- It depends entirely on the cause, which is why diagnosing before acting matters so much. A noindex or robots.txt mistake usually recovers within days of being fixed and recrawled. A migration with broken redirects recovers over a few weeks once the redirects are corrected. A core-update loss is the slow case: there is no reversal to trigger, and improvement is generally seen around a later update rather than immediately after your edits.
- My rankings look unchanged but traffic still fell. What happened?
- That is the impressions-flat, clicks-down pattern, and it means you are still being shown but no longer being clicked. The usual causes are an AI Overview or a featured snippet answering the query above you, a new ad block pushing you below the fold, or a competitor with a more compelling title in the same position. Check the live results page for your top queries — the answer is normally visible in the first screenful.
- Should I use a third-party tool to confirm an algorithm update hit me?
- Use it second, not first. Rank trackers and volatility sensors describe the weather across many sites; they cannot tell you whether your own deploy broke something. Read your deploy history and Search Console's indexing reports first, because those speak about your site specifically. A volatility spike on the same date is corroboration once you have already ruled out your own changes, not a diagnosis on its own.
- How is this different from a site that never had traffic?
- Completely different ladders. A site that never ranked has an indexing, topic or authority problem and is diagnosed by walking from indexing to impressions to position to click-through rate — see why a website gets no traffic. A drop means the pages already proved they could rank, so the question is what changed since, and the change is usually datable.
Want this done for you?
AgentCeres is a managed AI marketing team — specialists draft the work, you approve what ships. 14-day free trial, from $39/month.