When traffic falls off a cliff, most owners ask the same question: "Have I been penalised?" The better first question is: which kind of drop is this?
A manual action and an algorithmic drop look the same in your analytics. They have different causes, different fixes and completely different timelines. Get the diagnosis wrong and you can spend six months fixing the wrong thing.
I've been through a manual action from the inside, taking a penalised site back to position one for its core commercial term. That story is in my penalty recovery case study. This guide is the diagnostic step that comes before any of it.
Key takeaways
- A manual action comes with a notice in Search Console. An algorithmic drop comes with nothing.
- Manual actions are fixed and then reviewed by a person. Algorithmic drops are fixed and then reassessed by Google's systems over time.
- Penguin no longer issues penalties as such. It devalues spammy links in real time.
- A core update isn't a penalty. Treating it like one usually makes things worse.
- Rule out technical causes first. Plenty of drops that look like penalties are self inflicted.
Step zero: rule out the technical causes
Before you assume Google punished you, check you didn't do it to yourself. These all look exactly like a penalty in your traffic graph:
- A noindex tag left on after a redesign or migration
- A robots.txt file blocking Googlebot
- A migration with missing or broken redirects
- A canonical tag pointing every page at the homepage
- Your site going down, or the server blocking Googlebot by mistake
- Hacked content pulling the domain into spam territory
Open Search Console's Pages report and the URL Inspection tool. If your key pages are suddenly excluded or blocked, you have a technical problem, not a penalty. This check alone saves weeks.
How to tell which one you have
| Check | Manual action | Algorithmic drop |
|---|---|---|
| Manual actions report | Shows a listed issue | Says no issues detected |
| Notification | Email and Search Console message | None |
| Cause | A human reviewer saw a policy breach | Google's systems reassessed your site |
| Timing | Any date | Usually lines up with a confirmed update |
| Pattern | Partial (some pages) or sitewide | Often sitewide, or concentrated on one content type |
| Fix confirmed by | A person reviewing your reconsideration request | Systems recrawling and reassessing over time |
The key check is the date. Google keeps a public history of ranking updates with start and end dates for every confirmed core and spam update. Put your drop date next to that list. If it lands inside a rollout window and your Manual actions report is clean, it's almost certainly algorithmic.
Recovering from a manual action
A manual action is the more serious notice, but also the more certain one, because Google tells you what's wrong.
1. Read the notice properly
It names the issue type and whether it's sitewide or partial. The common types:
| Manual action type | What it usually means |
|---|---|
| Unnatural links to your site | Bought, exchanged or manipulative links pointing at you |
| Unnatural links from your site | You're selling or trading links |
| Thin content with little or no added value | Scraped, auto generated or doorway style pages |
| Pure spam | The site looks built for spam rather than users |
| Site reputation abuse | Third party content hosted to exploit your domain's trust |
| Hacked site | Spam injected by an attacker |
| Structured data issue | Schema markup that misrepresents the page |
2. Fix all of it
Partial cleanup is the most common reason requests get rejected. Reviewers want the problem gone, not reduced.
3. Document everything
For link actions, keep a spreadsheet of every link, every removal request and every outcome. Disavow only what you couldn't get removed.
4. Submit a reconsideration request
State what was wrong, what you did, and what stops it happening again. Specific beats apologetic every time.
5. Wait for the response
Reviews usually take days to a few weeks. A rejection tells you what's still outstanding.
6. Decide whether to restart instead
Sometimes the history runs so deep that a clean rebuild on a new domain is faster. That's what I did in my own case. Lifting the action only gets you back to zero either way, so plan the rebuild before you submit.
Recovering from an algorithmic drop
There's no request to submit and nobody to email. You fix the cause and wait for Google's systems to reassess. The fix depends on which update hit you.
Spam updates
Spam updates target sites breaking a specific spam policy: scaled content abuse, doorway pages, expired domain abuse and so on. If your drop lines up with one, match the pages that fell against the spam policies and remove or fix the violation. Recovery can take months while the systems learn your site now complies. My breakdown of the September 2026 spam update walks through the self audit.
Core updates
A core update isn't a penalty. Google reassesses how it judges quality and relevance across the whole web, and some sites drop because others got judged more helpful. Often there's nothing "wrong" to remove.
- Compare your dropped pages with the ones that now outrank you. What do theirs answer that yours don't?
- Strengthen expertise and firsthand experience on your key pages.
- Consolidate thin or overlapping pages into fewer, stronger ones.
- Fix user experience problems: slow pages, intrusive ads, buried answers.
Then wait. Core update drops often only reverse at the next core update, which can be months away. Mass deleting content in a panic is the most common way people turn a core update dip into a lasting loss.
Penguin and link related drops
People still search for "Penguin penalty recovery", but Penguin changed in 2016. It became part of the core algorithm and now works in real time, mostly by ignoring spammy links rather than penalising the whole site. Two things follow:
- If you lost rankings because bad links stopped counting, removing them won't bring the rankings back. The value was never real. You need genuine links to replace it.
- If the link problem looks deliberate enough, you're more likely to see a manual action for unnatural links than an algorithmic hit. Check the Manual actions report.
Disavowing is still worth doing for clearly toxic links you can't remove, especially where a manual action is involved. It's just not the fix it was a decade ago.
Recovery timelines, honestly
| Situation | Typical timeline |
|---|---|
| Technical cause (noindex, robots.txt, redirects) | Days to weeks after the fix |
| Manual action, clean first request | A few weeks |
| Manual action, rejected and resubmitted | One to three months |
| Spam update | Several months after fixing |
| Core update | Often the next core update, months away |
| Rebuild on a new domain | Three to six months to rank a competitive term |
Anyone promising a guaranteed fix in days for an algorithmic drop is selling you something.
The rebuild matters more than the fix
Whatever the cause, removing the problem doesn't put you back where you were. The old rankings were partly propped up by whatever got you hit. Once that's gone, you're rebuilding on cleaner foundations, which is the same work as good SEO from scratch. My SEO for small business playbook covers that order of operations.
If you've had a drop and can't tell which of these you're dealing with, my penalty recovery service starts with exactly this diagnosis, and I'll tell you honestly whether to fix, wait or rebuild.
FAQs
How do I know if Google has penalised my site?
Check the Manual actions report in Google Search Console. If it lists an issue, you have a manual action. If it's clean but traffic dropped sharply, compare the date with Google's confirmed updates and rule out technical faults like noindex tags or broken redirects.
What's the difference between a manual action and an algorithmic penalty?
A manual action is applied by a human reviewer at Google and comes with a notice in Search Console. An algorithmic drop happens when Google's automated systems reassess your site, and there's no notification.
How do I recover from a Google core update?
Core updates aren't penalties, so there's usually nothing to remove. Improve the helpfulness and expertise of the pages that dropped, compare them with what now ranks above you, and expect recovery to show at a later core update.
Is the Google Penguin penalty still a thing?
Not in its original form. Since 2016 Penguin has been part of Google's core algorithm and mostly devalues spammy links rather than penalising whole sites. Severe link manipulation is more likely to trigger a manual action.
How long does a reconsideration request take?
Google usually reviews requests within a few days to a few weeks. A rejected request tells you what's still wrong, and each resubmission adds more waiting time.
Where this leads
If this is the bit you want handled rather than explained:
- Penalty recovery. Diagnosis first, then the clean up, the reconsideration request and the rebuild.
- SEO audits. Technical causes ruled in or out before anyone calls it a penalty.
- A free first pass. Send the drop date and I will tell you which of these you are dealing with.
