A real SEO emergency is a problem that gets worse while you wait: a noindex tag shipped to production, a hack that’s adding spam pages by the hour, or a migration that went live without redirects. Those exist, and they’re rare. Most of what gets the label is an ordinary ranking drop that happened to get noticed, and you can usually tell the two apart in half an hour.
I went looking at what ranks for “SEO emergency” before writing this. The results are split between agencies selling emergency recovery retainers and advice about SEO for emergency plumbers, so Google can’t quite decide whether the phrase means anything either. The one substantial piece in there, Helen Pollitt’s at Search Engine Land, says she could count the genuine stop-everything moments of a 15-year career on one hand.1 So yes, they exist, and the list below is short.
What separates an emergency from a bad week?
The first question is whether the damage compounds while you wait. A noindex tag keeps doing damage: every time Googlebot recrawls another page, that page falls out of the index. A hacked site adds spam URLs all day long. A ranking drop from a core update, by contrast, already happened, and waiting until tomorrow doesn’t deepen the hole.
The second is whether the cause is something you control. A bad deploy is something you can revert tonight, while a core update leaves you nothing to roll back; Google’s guidance for update-related drops is to avoid radical changes and to expect any recovery to take months rather than days.2
If both answers are yes, start now. Anything else can wait until tomorrow without getting any worse.
The real ones
Google’s troubleshooting doc for traffic drops names the usual suspects: technical problems, security issues, manual actions, algorithm updates, seasonality, and site moves.2 Only a few of them pass both questions.
- A noindex tag or a stray Disallow rule shipped to production. It compounds with every crawl, and it’s embarrassingly common after a release.
- Your staging site got indexed. The wrong thing is in the index, and it gets more tangled the longer it sits.
- The site is down and staying down. An hour of downtime won’t move your rankings, but pages that can’t be fetched for days start dropping out.
- You’ve been hacked and Google noticed. Warnings on your listings suppress clicks right now, spam pages pile up under your domain, and both get worse the longer it runs.
- A migration went out without its redirect map. Every day the old URLs sit on 404s, more of their rankings leak away, and reconstructing the map gets harder. Keeping every URL alive was most of the actual work when I moved an 88-post blog off WordPress, and it’s the step I wouldn’t let anyone rush.
A manual action was the first thing I thought of when I started this post, and it belongs in a middle bucket. They’re rarer than the fear suggests: in Google’s last public webspam report, about 4.3 million of the 90 million Search Console messages it sent that year concerned manual actions, roughly one in twenty, and each one is a human reviewer flagging a specific guideline violation.3 When one lands, you fix the violation, file a reconsideration request, and wait weeks for a person to review it.1
The scariest recent example is GeeksforGeeks. In April 2025 the coding-tutorials site, which had been drawing something like 70 million monthly visits from Google, acknowledged its articles had vanished from the index and publicly told its users to search on Bing while it dug out.4 The removal was widely attributed to Google enforcing its site reputation abuse policy against years of off-topic content, birthday-wishes listicles and movie-download roundups on a programming site, though Google never said. The problem was years of content decisions, and no deploy was going to fix that.
The fake ones
Almost all of these start with a number on a dashboard.
Rankings moved a few spots. Google describes small position shifts as normal fluctuation and specifically recommends against radical changes to a page that was performing well.2
Traffic “fell to zero” but the site loads fine. Check the measurement first. Google’s doc even includes a sketch of what a reporting glitch looks like on a graph, a cliff that analytics shows and Search Console doesn’t.2 A Shopify store owner posted one of these: about 100 daily visits gone to zero, replies offering eleven possible causes from robots.txt to a broken pixel, and the thread ended without a diagnosis.5 Most of these turn out to be tracking, and plenty of the threads never find out which.
A core update dropped you. It hurts, but there’s nothing to hotfix. The work is assessment over weeks, and I covered how to tell a genuine shift from noise in how to spot a real SEO trend.
AI Overviews are eating your clicks. That one’s real too, but it builds over quarters. The answer is a strategy revision, which I laid out in AI Overviews vs classic SEO, and no part of it happens overnight.
A competitor passed you. Take a look at what they changed when you get a chance; nothing about it has to happen today.
| Situation | Emergency? | The clock |
|---|---|---|
| noindex or Disallow shipped to production | Yes | Every recrawl drops more pages |
| Hacked, warning on your listings | Yes | Warnings and spam pages stack up hourly |
| Migration lost its redirects | Yes | Old URLs shed rankings daily; the map gets harder to rebuild |
| Site down for days | Yes | Unfetchable pages don’t stay ranked |
| Manual action | Start today | Reconsideration takes weeks either way |
| Core update drop | No | Recovery is measured in months |
| Rankings slipped a few spots | No | Normal fluctuation |
| Analytics reads zero, site fine | No | Usually a broken tag |
The first half hour
When somebody messages you in a panic, this is the order I check things, fastest and most conclusive first.
- Search Console, the Manual actions and Security issues tabs. Two clicks, and it either names your problem or rules out the scariest ones.
- A site: search on your domain, then URL Inspection on the pages that earn the money. This separates “deindexed” from “ranking lower,” which are different problems on different timelines.
- View source on your key templates for a noindex that wasn’t there last week, and robots.txt for a new Disallow. Deploys change these more often than anyone admits.
- Confirm the site is actually up, from more than one location.
- Compare Search Console impressions against your analytics. If GSC looks normal while analytics reads zero, the problem is the measurement, and the fix is a script tag.
That’s maybe twenty minutes with no tools beyond what you already have. Most scares end at step one or two. Whatever gets through all five, start on it right away.
Should you pay for emergency SEO?
There’s a small industry aimed at exactly this moment: services with emergency in the name, penalty removal on retainer, response-time guarantees. I’d finish the half-hour checklist before calling anyone, because the diagnosis changes what help you need. A hacked site needs a security response, a botched migration needs a developer with the old URL map, and a manual action needs the violation gone before a reconsideration request means anything. None of that gets better because the invoice says emergency.
The cheap version of all this is prevention: an alert on noindex and robots.txt changes, uptime monitoring, and treating the redirect map as the deliverable on every migration. All three are quick to set up, and they cover almost everything on the real list.
Frequently asked questions
What counts as a real SEO emergency?
A problem that compounds while you wait and that you can fix: a noindex tag or robots.txt block shipped to production, a hacked site with warnings in search results, a migration that lost its redirects, or a site that stays down for days. Ranking drops and algorithm updates don't qualify.
My traffic dropped overnight. Is that an emergency?
Usually it's a measurement problem. Compare Search Console impressions against your analytics first; if Search Console looks normal while analytics reads zero, a tracking tag broke. Real ranking losses tend to move over days and weeks; an overnight zero is nearly always the tag.
Is a Google core update an SEO emergency?
No. There's nothing to hotfix, Google recommends against radical changes to pages that were performing well, and recovery from update-related drops takes months. Treat it as assessment and planning work over the following weeks.
How common are manual actions?
Rarer than people assume. In Google's last public webspam report, about 4.3 million of 90 million Search Console messages concerned manual actions, roughly one in twenty, and each reflects a human reviewer flagging a specific violation. Check the Manual actions tab in Search Console to know for certain.
My site was hacked. Is that an SEO emergency?
Yes. Security warnings suppress clicks on your listings immediately, spam pages accumulate under your domain, and neither stops on its own. Clean the site, close the hole, then request a security review through Search Console.
Should I hire an emergency SEO service?
Not before a basic diagnosis. Check Search Console's Manual actions and Security tabs, inspect your key pages, and verify tracking. Then hire for what you actually found: security help for a hack, a developer for a migration, a cleanup for a manual action. Skip anything that charges extra for urgency.
Keep going
More on telling real shifts from noise, and the migration habits that prevent the worst of this list.
Sources
-
Helen Pollitt, How to deal with SEO emergencies, Search Engine Land (October 23, 2024). ↩ ↩2
-
Google Search Central, Debugging drops in Google Search traffic. Source for the causes list, the normal-fluctuation and no-radical-changes guidance, the months-long recovery framing, and the traffic-graph shapes. ↩ ↩2 ↩3 ↩4
-
Figures from Google’s 2019 webspam report, as reported by Search Engine Journal, Google Finds Over 25 Billion Spammy Pages Every Day: more than 90 million Search Console messages, about 4.3 million related to manual actions. ↩
-
Hello Webmaster, GeeksforGeeks’ Removal from Google Search Index: An Investigative Report (April 2025). GeeksforGeeks acknowledged the removal on April 1, 2025 and pointed users to Bing; Google never confirmed the cause. ↩
-
Shopify Community, Website traffic suddenly fall into zero visitor. ↩
Working on this same shift?
I write about SEO, GEO, and getting found by AI search.
If this resonated, I'd love to compare notes.