// PROBLEM 02 — INDEX STATE: SUPPRESSED
Traffic Didn't Dip.
It Fell Off a Cliff.
A 60% overnight drop is not seasonality. It's a manual action, a core-update reappraisal, or inherited domain baggage. Each has a different recovery path — and treating the wrong one burns months.
Diagnosis sequence
- D-01
Manual action check
Search Console first. A manual action means a human reviewer flagged a specific violation — the notice tells you the class of problem, and recovery runs through a reconsideration request backed by real remediation.
- D-02
Update-timeline correlation
No manual action? Map the drop date against Google's update calendar. Core updates reappraise quality sitewide; spam updates target link schemes and scaled content. The overlap tells you what got reassessed.
- D-03
Domain history audit
If the site is on an acquired or aged domain, its past is your present: previous spam usage, toxic backlink inheritance, dark years. We scan registration and archive records before assuming the problem is your content.
The resolution
Recovery is forensic, not cosmetic: isolate the trigger, remediate it completely (link disavowal, content consolidation, structural cleanup), then rebuild the quality signals that survive future updates. The goal isn't just recovery — it's a site architecture that core updates strengthen instead of punish.
// OUTCOMEAlgorithm-proof: growth that survives every core update →FAQ
How do I know if it's a manual action or an algorithmic drop?
Manual actions appear in Search Console under Security & Manual Actions — if that panel is empty, you were hit algorithmically. Algorithmic drops cluster around documented update dates; compare your traffic-drop date against Google's update timeline.
Can a domain be penalized before I even own it?
Manual actions can persist through ownership changes, and a toxic backlink profile or spam history transfers with the domain. This is why we scan domain history before any acquisition or migration.
How long does recovery take?
Manual action reconsiderations resolve in weeks once the violation is genuinely fixed. Core-update recoveries typically wait for a subsequent update cycle — months, not days. Anyone promising faster is guessing.