Dated drop timeline
Exactly when the decline began, correlated against known algorithm updates and your own deployment and content history. The timing usually names the cause.
The four causes, and why they get confused
A drop has four possible causes: a manual action, an algorithmic update, a technical fault, or something your own team changed. Only the first appears in Search Console. The other three are inferred from timing and pattern, and misdiagnosis means months spent fixing something that was never broken.
Manual actions are the easiest case because Google tells you. Open Search Console, read the message, and you know what was found and roughly what is required. If there is no manual action listed, you do not have one, and any agency proposing penalty removal without checking that first is selling a remedy for a condition you have not been diagnosed with.
Algorithmic suppression is more common and harder. There is no notification, so it is inferred from the date the drop began matching a known update, and from which pages and query types lost most. That pattern analysis is most of the diagnostic work, and it is why the first deliverable is a timeline rather than a fix list.
Technical faults produce the most dramatic and most recoverable drops. A stray noindex shipped to production, a robots file blocking the site, a rendering change that hid the content, a migration executed badly. These are frequently fixed in an afternoon once identified, and they are the first thing worth ruling out.
The fourth cause is the one clients least expect and it is common: somebody changed something. Content consolidated, pages removed in a redesign, internal links restructured, a template altered. Nobody connects it to the traffic drop six weeks later because the two events feel unrelated, and reconstructing the change history is often what solves the case.
What the diagnosis produces
The diagnosis produces a dated timeline correlating the drop against updates and your own deployments, an identification of which pages and query types lost, a verdict on which of the four causes applies, and a remediation plan scoped to that cause rather than to all of them.
Loss pattern analysis
Which pages, templates and query types lost most. Broad uniform loss, a single template collapsing and long-tail-only decline all point at different causes.
Manual action check
Whether one actually exists, which takes minutes and rules out an entire category of expensive remediation nobody needed to buy.
Change reconstruction
What your own team shipped in the relevant window. Frequently the answer, and frequently the thing nobody thought to mention during the briefing.
A cause-specific plan
Remediation scoped to what the diagnosis found, rather than a broad programme covering every possible cause because nobody established which applied.
Realistic recovery expectations
What can be restored, over what period, and what probably cannot. Some losses are permanent because competitors have consolidated the positions.
How the engagement runs
The engagement runs diagnosis first and remediation only afterwards: check for a manual action, rule out any technical faults, reconstruct your own change history, correlate the timing against known updates, then scope the remediation to whichever cause the evidence actually supports.
- 01
Check for a manual action
Minutes of work that eliminates an entire category of remediation. If none is listed, you do not have one, whatever a previous agency may have implied.
→ A definitive manual action verdict
- 02
Rule out technical faults
Noindex directives, robots blocks, rendering failures, redirect problems. The most dramatic drops are frequently the most trivially fixable ones.
→ A technical fault assessment
- 03
Reconstruct what changed
Your own deployments, content edits and template changes in the window before the drop. This solves more cases than algorithm analysis does.
→ A reconstructed change timeline
- 04
Correlate against updates
Where nothing internal explains it, match the drop date and loss pattern against known algorithmic updates to establish what was likely reassessed.
→ An algorithmic correlation verdict
- 05
Scope remediation to the cause
A plan addressing what was actually found, with honest expectations about what recovers and what does not. Broad remediation without diagnosis wastes quarters.
→ A cause-specific remediation plan
The four causes and how to tell them apart
All four look similar in a traffic graph, which is why misdiagnosis is so common and so expensive. The distinguishing evidence is different in each case, and establishing which applies takes days rather than the months that broad remediation consumes.
| Cause | How you identify it | Typical recovery |
|---|---|---|
| Manual action | Reported in Search Console | Weeks after a successful reconsideration request |
| Algorithmic update | Drop date matches a known update | Months, and often only at the next update |
| Technical fault | Crawl, index or rendering evidence | Days to weeks once fixed |
| Self-inflicted change | Your own deployment history | Weeks, once reversed or corrected |
Signals you need this now
You need this when organic traffic fell sharply and nobody can explain why, when a previous agency proposed penalty removal without checking whether a penalty exists, or when remediation has been running for months with no recovery and no diagnosis behind it.
- Organic traffic fell sharply and nobody can explain why
- An agency proposed penalty removal without checking Search Console
- Remediation has run for months with no recovery
- You inherited a site with an unexplained historic drop
- A previous agency built links you have never audited
- Traffic fell weeks after a redesign nobody connected to it
- You are about to buy a site and want its history assessed
What clients see
Technical causes recover fastest, sometimes within days of the fix. Manual actions recover weeks after a successful reconsideration. Algorithmic suppression is slowest and least certain, frequently only lifting at a subsequent update — and we say that before the engagement rather than after.
Where this fits
Related SEO services
Common in these sectors
The adjacent disciplines
Deciding between options
Questions about Google penalty recovery
Each answer is written to stand alone in 40 to 60 words — the shape an AI Overview or Perplexity citation lifts. Ships with FAQPage schema.
How do we know if we have a Google penalty?
Check the manual actions report in Search Console. If nothing is listed, you do not have a manual action. Most sudden drops are algorithmic, technical or self-inflicted, and any agency proposing penalty removal without checking this first is worth questioning.
Our traffic dropped overnight. What is most likely?
A technical fault or something your own team shipped. Overnight drops rarely indicate algorithmic reassessment, which tends to roll out over days. A stray noindex, a robots block or a bad migration accounts for most of the sudden cases we see.
How long does recovery take?
It depends entirely on the cause. Technical faults can recover within days of the fix. Manual actions take weeks after a successful reconsideration request. Algorithmic suppression is slowest and least certain, sometimes only lifting at a subsequent update months later.
Should we disavow links after a drop?
Only with evidence of a link-related manual action or a clearly manipulative profile. Disavowing on suspicion removes authority you were benefiting from and is a common way to make a recoverable situation worse. We advise against it far more often than for.
Can all lost traffic be recovered?
Not always, and we will say so during diagnosis rather than after months of work. Where competitors have consolidated the positions you lost, some of it is gone. Setting that expectation early is more useful than an optimistic scope nobody can deliver.
Why start with diagnosis rather than fixing things?
Because the four causes need entirely different responses, and remediating the wrong one costs quarters. Diagnosis takes days. Broad remediation without it is how sites spend six months rebuilding content when the actual problem was a rendering change.
Find out whether this is your constraint.
Thirty minutes with a senior strategist. We pull your live visibility while we talk and tell you plainly whether a Google penalty recovery is what you need — or whether your problem sits somewhere else.