Forensic SEO

SEO Recovery: Find What Broke, Fix It, Prove the Comeback

When traffic collapses, guessing is expensive. I find the root cause, brief your leadership in plain English, and direct your developers through the fix until the comeback shows in the data.

Root cause firstFixed-fee diagnosisSince 2004

What SEO Recovery Is (and How It Differs From an Audit)

SEO recovery is forensic work: tracing a traffic or indexation collapse back to its root cause, directing the fix, and proving the comeback against a baseline. A routine audit surveys everything a site could improve. A recovery engagement answers one question: what exactly broke, and when.

The distinction matters because a collapsing site does not need fifty recommendations. It needs the one that ends the bleeding. If nothing has collapsed and you want the broad survey, you want an SEO audit. If clicks or indexed pages fell off a cliff, you are in the right place.

Guessing is what makes traffic drops expensive. Teams rewrite content, buy links, and switch agencies while the actual cause sits in a redirect map nobody has opened in years. I have been finding these causes since 2004, and the pattern repeats: the symptom is recent, the cause usually is not.

Symptom check

Five Signals This Is a Recovery Problem

If any of these look familiar in your Search Console, the problem is diagnosable. These are the five I see most.

Indexed pages keep falling

Search Console's indexed count slides week over week while nothing obvious changed. Google is quietly losing confidence in whole sections of the site.

A traffic cliff on a known date

Clicks fell off a cliff on a date you can point to. That date is evidence: whatever shipped, migrated, or expired that week is suspect number one.

Crawled, currently not indexed

Google fetches your pages and declines to keep them. When that status grows, Google increasingly sees the site as not worth indexing.

Soft-404 floods

Pages returning 200 that Google reads as empty. Common with app shells that render blank for crawlers, and every one erodes sitewide trust.

From a real diagnosis

Anatomy of a Collapse (and the Comeback)

Tap the numbered markers. This is the shape of a real recovery: a B2B SaaS whose indexation flatlined for reasons that started two years before the drop.

organic clicks2 yrs before the dropday 0the comeback
Based on a real engagement: a B2B SaaS whose indexation flatlined. The root cause was a migration two years earlier.

The 5-Step Recovery Method

Five steps, always in this order. Diagnosis before prescription, evidence before invoices.

01

Timeline Reconstruction

Date the break precisely. Search Console, analytics, deploy logs, and archived crawls narrow the collapse to a week, often to a day. The date is the single most valuable clue in the whole engagement.

02

Root-Cause Tracing

Crawls plus redirect and canonical archaeology (the cause is often years older than the symptom). I follow the evidence backward until the explanation accounts for the whole curve, not just part of it.

03

Executive Briefing

A written diagnosis in plain English, addressed to the CEO rather than the dev team: what broke, when, why, what it is costing, and the fix in dependency order. No jargon, no fifty-item list.

04

Directed Remediation

Your engineers ship the fixes. I set the order, review each change, and verify it landed the way Google needs it to. Nobody rebuilds anything that does not need rebuilding.

05

Recovery Proof

Indexation and click curves tracked against the pre-drop baseline until the comeback is visible in the data. You get proof, not a promise that things feel better.

Why Forensic Beats Guessing

2004

the year I started diagnosing ranking collapses. The failure patterns repeat; the platforms just rename them

2 yrs

how far back the root cause hid in the featured SaaS case before the symptom ever showed

1

root cause per collapse, almost every time. Everything else on the list is a symptom

Fixed-fee diagnosis, quoted before we start. Monitoring the comeback afterward is an optional retainer.

Who Recovery Is For

You run the business and need a straight answer

Most recovery clients are founders, CEOs, and marketing leads who have already heard three theories from three people and cannot tell which one to fund. What you get from me is a diagnosis in plain English you can take to a board, and a fix directed to completion instead of a report that dies in a drawer.

Your developers are good, but this is not their specialty

I do not replace your engineering team. I direct it: what to fix, in what order, and how to verify each change landed the way Google needs it to. Search forensics is a different discipline from building features, and it should not be learned on a live emergency.

The drop followed a redesign or migration

This is the most recoverable category there is, because the causes are mechanical and they leave fingerprints. It is the same discipline my website migration SEO service applies before a launch, pointed backward at one that shipped unprotected.

How the engagement is priced

The diagnosis is a fixed fee, quoted after a short scoping call. If you want the comeback watched through to completion, monitoring afterward is an optional retainer. No percentage of ad spend, no lock-in, and no invoice for guessing.

Frequently Asked Questions

Straight answers about traffic drops and what it takes to come back.

Why did my website traffic suddenly drop?
Because something specific changed, and it is findable. The usual suspects: something shipped (a redesign, a migration, a template change), something expired (redirects, certificates, tracking), or Google reweighted something (an algorithm update). The date of the drop narrows the field fast, which is why recovery starts with timeline reconstruction rather than opinions.
Was it an algorithm update or something we broke?
Check the date first. If the drop lines up with a documented update, the answer is strategic. If it lines up with a deploy, the answer is mechanical, and mechanical problems recover faster because you control the fix. The self-inflicted kind is more common than teams expect, which is good news: you do not have to wait for Google to change its mind.
Can a site recover from being deindexed?
Usually, yes, once the cause is removed. Deindexation is Google declining to keep pages, not a permanent sentence. When the blocker disappears (a stray noindex, a soft-404 flood, blank responses to crawlers), pages come back. What determines the speed is how long the problem ran and how much crawl trust it burned. The case featured on this page came back from a full indexation flatline.
How long does SEO recovery take?
Diagnosis is the fast part; the comeback depends on what broke and how long it ran. A fresh mechanical cause recovers on a very different curve than redirect debt that compounded for two years, like the SaaS case above. What I commit to is the sequence: root cause first, fixes in dependency order, then the curve tracked against baseline until the recovery is provable.
Do I need an audit or a recovery engagement?
If traffic is stable and you want to know what could be better, you want an SEO audit. If traffic or indexation collapsed and you need to know what broke, you want recovery. The deliverables differ too: an audit is a prioritized improvement plan, a recovery is a diagnosis, a directed fix, and proof of the comeback against your baseline.
My rankings dropped right after a redesign. What now?
Stop changing things, preserve the evidence, and date the drop. Post-redesign losses are usually mechanical: lost redirects, changed URLs, rewritten metadata, or a new stack rendering empty to crawlers. All of those leave fingerprints, which makes this the most recoverable category I see. The same protocol described under website migration SEO is the map for undoing the damage.

Every Week Undiagnosed Is Compounding Loss

Send me a screenshot of your Search Console performance curve and I will tell you on the first call whether the drop looks mechanical, algorithmic, or structural, and what a diagnosis would take. No retainer required to find out what broke.