Google Manual Action: How to Fix It and Recover
A Google manual action is a human reviewer's penalty. Here's how to read the notice, fix the real cause, and write a request a reviewer approves.
A Google manual action is a penalty applied by a human reviewer, visible only in Search Console's Security & Manual Actions report, for violating a specific spam policy. Fixing it means removing the actual violation completely, documenting what you changed, and filing a reconsideration request that a reviewer can approve without guessing.
That is a narrower, more mechanical problem than most traffic drops. If you have not yet confirmed this is what happened to you, the organic traffic drop guide covers the wider diagnosis first.
On this page
How do you know it's a manual action and not an algorithm hit?
Check the Security & Manual Actions report in Search Console first, before you read another word of advice about algorithms. If it is empty, you do not have a manual action, whatever a drop looks like — you have an algorithmic ranking change, and the diagnosis and fix are entirely different [1].
This distinction gets confused constantly because both produce the same graph: a sudden drop in a line chart. But a manual action names its cause in plain language, in a report built for exactly this purpose, while an algorithmic change never explains itself anywhere. If your report is empty, stop reading this post and work through how to check for a Google penalty instead, or core update recovery if the timing lines up with a named update.
If the report does list an action, read the exact wording Google used. It names a specific policy — unnatural links, thin content, cloaking, hacked content, user-generated spam — and that wording is your entire fix list. Nothing outside it matters for this particular action.
This is the part teams skip past too quickly. It is tempting to read "unnatural links" and start a general link-quality project, or read "thin content" and start a general content refresh, when the report is actually telling you something much narrower: this specific set of links, or this specific batch of pages, is what a reviewer flagged. Broadening the scope feels thorough, but it slows down the one thing that actually lifts the action — showing the reviewer the named violation is gone.
Keep a running log from the moment you confirm the action. Screenshot the report, note the exact date it appeared, and save the wording verbatim. You will need all three when you write the reconsideration request, and Search Console's report only shows the current state — not a history of what it said when you first found it.
What are the most common manual action types?
Most manual actions fall into a small number of categories, and each one has a specific, narrow fix rather than a general "improve quality" response.
| Violation named | What actually fixes it |
|---|---|
| Unnatural links to your site | Remove or disavow the specific links; do not just add new good ones |
| Unnatural links from your site | Remove or nofollow the outbound links you sold or exchanged |
| Thin content with little or no added value | Delete or substantially rewrite the named pages — see helpful content recovery |
| User-generated spam | Clean and moderate the specific sections Google names, usually comments or forums |
| Cloaking or sneaky redirects | Remove the code path that serves different content to Googlebot than to users |
Thin content actions overlap heavily with the broader helpful content problem, just enforced manually instead of algorithmically. If that is your violation, read helpful content recovery alongside this post — the diagnosis is different, but a lot of the actual fix work is the same.
Every category above traces back to Google's published spam policies, which is worth reading in full once rather than working from summaries like this one [3]. The policy document is specific about what counts and what does not — for instance, a normal guest post with editorial oversight is not the same violation as a paid guest post built purely to pass links, even though both involve outside sites publishing your content. That distinction changes what you actually need to remove.
Sites rarely receive more than one or two manual action types at once, which is useful to know going in: if your report names "unnatural links," spend your time entirely on the link graph rather than also auditing content depth on the theory that Google must have meant more than it said.
How do you fix unnatural links before you request reconsideration?
Pull every backlink Search Console and your link-tracking tool show, and sort them by whether they look paid, exchanged, or otherwise manufactured rather than editorially earned. This is the slowest part of the whole process and there is no shortcut worth taking — a reviewer checking your reconsideration request will spot-check the same list.
Export the full backlink list
Search Console's Links report plus a third-party crawler, because neither one sees every link on its own.
Classify each domain
Paid placement, link exchange, PBN, guest post with no editorial standard, or genuinely earned. Be honest — a reviewer will be.
Request removal first
Email the site owners for the ones you can identify a real contact for. Some will actually take the link down, which is cleaner than a disavow.
Disavow what's left
Use Search Console's disavow tool for everything you could not get removed, at the domain level for anything systemic.
Do not stop at disavowing and consider it done. A reconsideration request that shows no evidence of outreach attempts, only a disavow file, reads as someone who wanted the fastest possible checkbox rather than someone who actually cleaned up a problem — and reviewers can tell the difference.
If the links came from a vendor you paid for placements, that relationship is part of the violation, not a side detail. Reviewers read reconsideration requests from sites that fixed the links but kept paying the same vendor for new ones under a different label, and the pattern is not hard to spot from the outside. Ending the relationship, and saying so plainly in the request, is part of the fix — not paperwork around it. Our link building work only ever builds the kind of links that would survive this exact audit, which is the cheaper way to never be in this position twice.
What does a strong reconsideration request actually say?
A request a reviewer can approve on the first read states, specifically, what the violation was, exactly what you did to fix it, and what you changed structurally so it does not recur. Vague requests — "we've improved our SEO practices" — read as someone who has not actually located the problem.
Write it the way you would document an incident for an internal postmortem, not the way you would write ad copy. Name the tool you used to find the links, the number you removed or disavowed, the date, and — if the violation involved a third party like an SEO vendor who built the scheme — that you have ended the relationship. Google's own guidance for reconsideration requests asks for exactly this level of specificity [2].
How long does Google take to respond?
There is no fixed number Google publishes, and it varies with the scale of the action and Google's review queue at the time. Build your plan around weeks, not days, and do not schedule other launches to depend on the manual action being lifted by a specific date.
That timing uncertainty is exactly why getting the first submission right matters more than getting it in fast. A request submitted quickly but incompletely, followed by a rejection and a second, more thorough submission, takes longer end to end than one careful pass would have.
What happens if the reconsideration request gets rejected?
You get a notice, usually with limited detail on exactly what was insufficient, and the action stays in place. Re-read your own request against the violation's exact wording again, and assume the reviewer found something you missed rather than that the policy is being applied unfairly.
Bring in a second set of eyes at this point if you have not already — someone who was not involved in building the site's link profile or content in the first place tends to spot the remaining violation faster than the team that has been staring at the same pages for weeks. Persistent manual actions on sites that genuinely have cleaned up are rare; far more often, something real is still there.
Questions people also ask
How do I know if I have a manual action?
Open Search Console and check the Security & Manual Actions report. If a human reviewer has taken action against your site, it is listed there with the specific violation type and whether it affects the whole site or part of it. An algorithmic drop never appears in this report.
Can I recover from a manual action without an agency?
Yes, if the cause is narrow and you can fix it fully — remove a set of paid links, delete a batch of thin pages, close a hacked-content hole. Complex or long-running link schemes are where outside help earns its cost, because a rejected request costs another review cycle.
Does a manual action affect the whole site or just some pages?
It depends on the violation. Search Console labels each action as either site-wide or partial matching a set of pages or patterns, and the reconsideration request only needs to address what the notice actually names.
How many times can I submit a reconsideration request?
As many as it takes, but each rejected request costs another review cycle, typically weeks. Fix the cause completely and document it before you submit, rather than submitting early and iterating through Google's review queue.
Sources
- Manual actions report - Search Console Help — Google Search Console Help (checked 23 September 2026)
- Reconsideration requests - Search Console Help — Google Search Console Help (checked 23 September 2026)
- Spam Policies for Google Web Search — Google Search Central (checked 23 September 2026)
Get the violation actually gone before you submit again
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Jeremy ZavaCo-founder
Leads growth and client partnerships.
Works on: CRO, SEO
Reviewed before publishing by Ibrahem Helal, Co-founder.
- Organic traffic drop: find the cause and fix itWhy organic traffic drops, how to tell tracking, seasonality, updates, penalties and technical faults apart, and what recovery really takes.
- How to Check for a Google PenaltyConfirm whether Google actually penalized your site, or whether something else caused the drop, in three checks you can run in Search Console today.
- How to Recover From a Google Core UpdateA core update caused your traffic drop. Here's how to confirm it, what actually needs fixing, and how long recovery really takes.
- Helpful Content Recovery: A Step-by-Step PlanHow to recover from a helpful content hit: what the classifier actually penalizes, the fixes that move it, and a realistic timeline for getting traffic back.