Rank
Why Did My Website Traffic Suddenly Drop?
Traffic falls off a cliff and nothing looks different. Usually it's technical, usually it's fixable, and usually nobody's looked. Here's where to look.
Sudden traffic drops are usually technical, not algorithmic. The common causes are: a change that blocked indexing, broken canonical tags, a botched migration, a manual penalty, or a compromise adding pages you didn't create. Genuine algorithm updates cause gradual decline across a whole category, not a cliff for one site. sosSTEVIE finds the actual cause before recommending anything — because "we were hit by an update" is the story people tell themselves while a fixable problem quietly runs for a year.
Key takeaways
- A cliff is technical. A slope is algorithmic. The shape of the graph tells you which conversation you're in.
- The most common causes are self-inflicted and reversible — usually a setting nobody knew existed.
- "It must have been an update" is the most expensive assumption in this business.
- A site can be completely healthy to every human who looks at it and entirely absent from search.
- If your traffic drop coincides with a site change, that's not a coincidence. It's the answer.
The story
The most expensive words in this industry are “it must have been an algorithm update.”
I’ve watched people say that sentence and then do nothing for fourteen months. It’s a comforting explanation. It’s out of your control, it’s happening to everyone, it’s the weather. You can’t be blamed for the weather. So you wait for it to pass, and it doesn’t, because it was never weather.
Here’s a real one. A firm lost 70% of their organic traffic across about three weeks and concluded they’d been hit by a core update. They’d read the forums, everyone said the same thing, so they hunkered down and waited it out. Fourteen months of waiting.
What actually happened: a plugin update had changed how their canonicals were generated. Every page on the site was now telling Google “don’t index me, index the homepage instead.” The site was politely, methodically deleting itself from search, exactly as instructed. Google was doing precisely what it had been asked.
Nobody looked, because there was nothing to see. The site looked perfect. It loaded fine. It was, from any human vantage point, a completely healthy website that had simply stopped existing.
It took a morning to fix. Fourteen months to notice.
Read the shape of the graph
Before anything else, look at your analytics and ask what shape the drop is.
A cliff — traffic falls off in days or a couple of weeks, and stays down. Almost always technical or a penalty. Something happened. Something you did, something a plugin did, or something an attacker did. This is good news: it has a cause, and causes can be found and reversed.
A slope — steady decline over months. Could be algorithmic, could be competitors improving, could be your content going stale, could be buyers moving to AI answers and never opening a results page at all. This is a strategy conversation, not a bug hunt.
A cliff you didn’t notice for months — you’re looking at a slope in the data and a cliff in reality. This is the worst case and it’s more common than you’d think.
Most people diagnose a cliff as a slope. They see the drop, reach for “algorithm update,” and start a slow expensive content programme aimed at a problem that was a broken setting in the CMS.
The shape tells you which room you’re in. Look at it before you buy anything.
The five causes
I have never once found a sudden drop that wasn’t on this list.
1. You told Google not to index you. A staging site pushed live with noindex still on. A robots.txt change. A plugin update that rewrote canonicals. This is the most common cause of catastrophic drops and it’s almost always accidental. It’s also usually a one-line fix, which is either wonderful or infuriating depending on how long it ran.
2. A migration went wrong. New site, new URLs, no redirects — or redirects that chain, loop, or point at a 404. Every bit of authority you’d built for a decade, disconnected in an afternoon. Migrations are the highest-risk routine thing anyone does to a website and they’re consistently under-planned.
3. A manual action or penalty. Real, checkable, and nobody checks. Search Console tells you outright, free, in plain English. I regularly find manual actions that have been sitting unread for over a year, in an account nobody logs into, notifying an email address that belongs to a developer who left.
4. You’ve been compromised. Spam pages get injected, Google notices, your domain trust collapses. Your traffic dies for reasons that look algorithmic and aren’t. This is what happened to me. My rankings didn’t fall because of an update. They fell because thirty thousand pharmacy pages appeared under my domain and Google drew the obvious conclusion. Check this before you check anything else — because if it’s this, everything else you do is wasted.
5. Your site got slow or broken on mobile. A theme update, an unoptimized hero image, a script that hangs. Rarely causes a cliff on its own; frequently the accelerant on a slope.
Notice that four of the five are things that happened — with a date. Which means the single most useful diagnostic question in this whole discipline is: what changed the week the traffic fell?
Nine times in ten, somebody knows. They just never connected it, because the change and the consequence didn’t look related.
What AI actually does here
Let me be honest about this rather than sell you a story.
AI is genuinely excellent at: crawling a site at scale and flagging anomalies, spotting patterns across thousands of URLs no human would review, comparing your structure against competitors, sifting log files, and catching the class of error that’s obvious once seen and invisible before.
AI is useless at: knowing that you migrated hosts in March, that your developer left in April, that the marketing manager “cleaned up” the sitemap in May. The cause is nearly always a fact about your business, and no crawler knows any facts about your business.
The tools find the anomaly. A person finds the cause. Anyone selling you an automated SEO audit is selling you the first half and charging for both — and you’ve had one of those PDFs. Forty-seven pages, red triangles, no answer.
I use AI heavily to do in an hour what used to take three days. Then I ask what changed in March. The second question is the one that finds it.
The Drop Protocol
1. Date the drop precisely. Not “around spring.” The week. Everything hangs on this.
2. List what changed that week. Deployments, plugin updates, host migrations, redesigns, staff departures, DNS changes. Ask everyone, including the person who says nothing changed. Something changed.
3. Rule out compromise first. site:yourdomain.com, Search Console security tab, admin user list. If you’re hacked, nothing else matters until that’s dealt with. Start here instead.
4. Check the free stuff nobody checks. Manual actions. Coverage report. Robots.txt. Canonicals on your top pages. Fifteen minutes, and it solves a startling share of cases at zero cost.
5. Crawl it properly. Now bring the tools in — indexability, redirect chains, canonical conflicts, structure. You’re looking for what corroborates the date.
6. Match cause to date. The real cause will line up with the week. If your best theory doesn’t fit the timeline, it’s the wrong theory, however much you like it.
7. Fix, then wait properly. Recovery isn’t instant even when the fix is. Google has to re-crawl, re-evaluate, re-trust. Weeks, sometimes months. The hardest part of this work is the interval between fixing it and seeing it work.
Somebody has to look
That firm waited fourteen months for weather that was never coming, while their site quietly followed the instruction it had been accidentally given.
Nobody looked, because there was nothing to see. That’s not incompetence. It’s just what invisible failures are like — and I have a particularly personal reason for knowing how long you can stare straight at one without seeing it.
Date the drop. List what changed. Look.
Find out what actually happened — $997 Diagnostic →
About Stevie
My traffic didn’t drop because of an algorithm update. It dropped because someone else was publishing thirty thousand pages under my domain and Google drew the obvious conclusion. It took me weeks to work that out, and by then it was too late.
I don’t accept “it must have been an update” any more. There’s always a cause. It always has a date.
sosSTEVIE — for when your digital presence is broken, invisible, or about to be. (754) 302-4631
Frequently asked questions
Why did my website traffic suddenly drop?
If it fell off a cliff over days or weeks, it's almost certainly technical rather than algorithmic — most often an accidental noindex, broken canonical tags, a botched migration, a manual penalty, or a compromise. Real algorithm updates produce gradual decline across a whole category of sites, not a cliff for one. Start by dating the drop precisely and listing everything that changed that week.
Was I hit by a Google algorithm update?
Probably not, if the drop was sudden and specific to you. Algorithm updates are widely reported, affect many sites in a sector at once, and typically produce a slope rather than a cliff. "It must have been an update" is the most expensive assumption in this industry because it's unfalsifiable and it justifies doing nothing. Check the technical causes first — they're fixable, and updates aren't.
How do I check if Google has penalised my site?
Google Search Console tells you directly, free, in the Manual Actions section, in plain English. Most business owners have never looked, and I regularly find actions sitting unread for a year in an account nobody logs into. If there's nothing there, you haven't been penalised — which is genuinely useful to know, because it redirects you to the real cause.
My site looks completely fine. Can it still have a serious SEO problem?
Yes, and this is the central trap. A site can render perfectly for every human who visits while telling search engines not to index a single page. The visitor experience and the crawler experience are different things, and nothing on your screen reports the difference. My own site looked immaculate while it was being deleted from search, and I found out from the silence.
How long does recovery take after you fix the problem?
It depends on the cause and how long it ran. A noindex caught in a fortnight can recover in weeks once removed. A compromise that ran for months, or a migration that severed years of authority, can take many months, because Google has to re-crawl and rebuild trust on its own schedule. The fix is usually fast. The recovery isn't, and anyone promising otherwise is guessing.
Also in Rank
Stop guessing.
Five days. One diagnosis. A ranked list of what's broken, what it's costing you, and what to do in what order — yours to keep whether you hire me or not.
The Backstory
Three years ago my own website was taken over. It looked completely normal in my browser while tens of thousands of spam pages ran underneath it. I found out when the calls stopped, and I had to take the whole thing down.
I diagnose before I quote, because I know exactly what it costs to be certain about the wrong thing. The whole story is here.