How to Recover from a Google Manual Action Penalty

Published Read 6 min read

On this page

A manual action is a human reviewer enforcing a named violation against your site, and recovery turns on two things this post treats in depth: knowing which violation type you have, because the fix differs sharply by type, and writing a reconsideration request that actually clears review. The request is not a plea. It is an evidence document, graded the way a compliance audit is graded, and the requests that fail are the ones that give a reviewer nothing to verify. “We improved quality, please reconsider” gets rejected. “Removed the aggregated pages with the URL list attached, rewrote the rest with first-hand testing, adopted a test-before-review policy” passes, because every claim in it is spot-checkable.

This sits next to the end-to-end recovery process, which covers locating the action in the report, fixing the root cause, submitting, and riding out the rejection cycle and timeline. That ground is covered elsewhere. Here the focus is narrower and deeper: the taxonomy of penalty types and how the fix changes per type, the craft of the reconsideration request text itself, and the prevention nuance that keeps the violation from recurring. You locate the action in Search Console under Security and Manual Actions and you do wait for review, but the step-by-step narration belongs to the process post. The line worth stating plainly: a manual action means a human, a Search Console notification, and a reconsideration request that can clear it. An algorithmic drop has none of those, and there is nothing to reconsider.

The taxonomy, and why the type dictates the fix

Manual actions are not one thing with one remedy. The type tells you what the reviewer will look for and therefore what your fix and your evidence must show.

  • Unnatural links to your site. Inbound manipulation. Clean up what you can at the source through removal outreach, document that outreach, and reserve a domain-level disavow for the links you genuinely cannot remove. This is the one type where disavow is the right tool.
  • Unnatural links from your site. Outbound manipulation, usually sold or spammy links you are passing. Remove or nofollow them. Disavow is irrelevant here; it governs inbound links only.
  • Thin content with little or no added value. Content that exists without offering anything beyond what’s already available. The fix is genuine first-hand value or removal. Word count does not fix thinness; padding a thin page leaves it thin and longer.
  • Cloaking and sneaky redirects. Serving Google different content than users see, or bouncing users somewhere they didn’t expect. Serve identical content to users and crawlers, and kill the redirects.
  • Pure spam. The severe end: aggressive, deceptive, or automated spam techniques across the site. Recovery is a major overhaul, not a patch.
  • User-generated spam. Spam in forums, profiles, comments, or guestbooks submitted by visitors. Moderate the UGC: nofollow or remove the offending content and tighten what gets published.
  • Spammy structured data. Markup that misrepresents the page or is invisible to users. Remove the fake or misleading markup so the structured data matches what’s actually on the page.
  • Keyword stuffing and hidden text or links. Remove the stuffing and surface or delete anything hidden from users.

Read your specific action, match it to its type, and let the type set both the fix and the evidence you’ll need to show.

The binary-fix rule

Manual actions are not graded on a curve. You do not get partial credit for fixing most of the problem. The reviewer is checking whether the violation still exists anywhere, and if it persists on pages you missed, the request is rejected. So the fix has to be complete across every affected page and every instance of the pattern, not the obvious ones. Before you write a single word of the request, confirm the violation is genuinely gone everywhere it lived, because a reviewer who spot-checks one page you forgot has all the reason needed to deny.

The reconsideration request, written to be verified

This is the centerpiece. Google’s own guidance is that a good request does three things: explain the exact quality issue on your site, describe the steps you took to fix it, and document the outcome of those efforts. Build the request in four moves around that.

First, acknowledge the exact violation in its own terms. Name the specific issue the reviewer cited. Demonstrating that you understand precisely what was wrong is the foundation; a request that is vague about the violation signals you may not have actually found it.

Second, enumerate concretely what was wrong and what you changed. Counts, URL-level specifics, before and after. Not “we cleaned up our links” but “identified the manipulative links, removed the ones we controlled, requested removal of the rest with outreach logged, and disavowed the unremovable remainder.” Specificity is the whole game because the reviewer can verify it.

Third, attach evidence the reviewer can open. A spreadsheet of the removed or modified URLs, the outreach record, before-and-after examples. You are handing the reviewer the means to confirm your claims quickly. The principle matters more than any template; describe what you did and attach the proof, rather than reproducing some bloated boilerplate email.

Fourth, commit to a concrete prevention policy. State the editorial or technical control that stops the violation from recurring. This both reassures the reviewer and protects you, because a repeat violation is far harder to clear than the first.

The reason this works is mechanical. Reviewers spot-check. A request full of verifiable specifics gives them quick confirmations and a reason to approve. A request full of sentiment gives them nothing to check and a reason to move on. And the type taxonomy tells you which evidence the reviewer is actually looking for: link removal logs for a links action, rewritten pages with demonstrated first-hand experience for a thin-content action, corrected markup for a structured-data action.

Why thin-content affiliate is the archetype

The clearest case is the affiliate site penalized for thin content with no added value. “We researched this from other reviews” is precisely the pattern the policy targets: content assembled from what already exists, adding nothing. The fix is not more words and not a better writer. It is first-hand value, content that demonstrates the site actually tested, used, or knows the thing, paired with removing the pages that can’t be made genuinely valuable. The reconsideration request then shows that shift concretely, with the rewritten pages and the removed ones listed.

Disavow stays in its lane

Disavow earns exactly one mention in a manual-action recovery, and only for the unnatural-links-to-your-site type. The 2026 stance is narrow: the disavow tool is for an active manual action for unnatural links or a strong evidenced belief one is imminent, and nothing else. Illyes has said the tool hurts more sites than it helps, and Google’s systems already neutralize most manipulative links automatically. It is not a general manual-action remedy, and using it for a thin-content or cloaking action does nothing for the actual violation.

Prevention is the part people skip

The fix clears the action; the policy keeps it cleared. Match the prevention to the type: only review products you’ve actually tested, moderate UGC on a real cadence, keep structured data honest as a standing rule, audit outbound links before publishing. A reconsideration request that names a credible prevention policy clears more easily, and the policy is what keeps you out of the far harder position of clearing a repeat offense. The discipline that earned the recovery is the same discipline that prevents the next one.

Sources

Related posts:

  1. Why Is My Bounce Rate So High and Does It Affect SEO? A high bounce rate is not a Google ranking factor, because Google does not use your Analytics data to rank pages, and for content that fully answers a question on......
  2. How to Do SEO for a Podcast A podcast is invisible to Google web search by default, because Google cannot index audio. The entire web-search opportunity for a show is the text layer you build around each......
  3. JavaScript Redirects Are Leaking PageRank to Nowhere If you moved a page months ago and the old URL still ranks on its own, sometimes competing with the page you redirected it to, the cause is almost never......
  4. How to Do SEO for a SaaS Website Most SaaS SEO underperforms for one structural reason: the team pours effort into top-of-funnel blog content that attracts readers who are not buying, while neglecting the bottom-funnel pages that capture......
  5. How to Reverse Engineer Google’s Quality Raters Guidelines for Your Site The Search Quality Rater Guidelines are a public document describing exactly what Google trains its algorithms to detect, which makes them a usable blueprint for self-auditing. You reverse-engineer quality by......
  6. How to Do SEO for Comparison Aggregator Sites Comparison-aggregator sites are losing ground because Google's quality systems no longer reward repackaging publicly available data without original insight. If a user could get the same facts from the source......
  7. How to Do SEO for Franchise Businesses Franchise SEO breaks down as a governance problem, not a technical one. When a corporate brand site and dozens of independently operated franchisee sites all chase the same brand-plus-city queries,......
  8. Redirects Are Working But Traffic Still Dropped A redirect that verifies clean in a crawler proves one thing only: the hop resolves with a 301 and lands on a live page. It does not prove that the......
  9. Google Keeps Choosing the Wrong Canonical A canonical tag is a hint, not a directive, and Google says so directly: it takes your declared canonical into consideration, but it can and does select a different URL......
  10. Original Research as an SEO Moat Original research is defensible for one reason: the asset is data your competitors cannot replicate. Informational content gets reverse-engineered within weeks, because anyone can read the same sources and rewrite......
  11. Your A/B Testing Tool Is Showing Googlebot the Control Variant The conversion winner you just shipped may be content Google never evaluated. Most client-side experimentation tools exclude bots from tests by default, which means Googlebot spent the entire experiment seeing......
  12. Google Is Treating Your Tabs as Hidden Content The flat claim that Google "deprioritizes" content hidden in tabs and accordions is a contested myth, and shipping it as settled fact is the most common error in this corner......
  13. SEO Experimentation Frameworks: Hypothesis Testing for Organic Search Rigorous SEO testing is possible, but only if you abandon the naive before/after comparison that almost everyone defaults to. A page changed, traffic moved, therefore the change worked is not......
  14. Why Your CDN Is Serving Different Content to Googlebot If Googlebot is indexing a version of your pages that no longer exists for users, your CDN is almost certainly serving the crawler a stale or differently-processed response. This usually......
  15. Your Bot Detection Is Blocking Googlebot and You Don’t Know It Aggressive bot protection can challenge or block legitimate crawlers when the rules are ordered so that a strict challenge fires before the verified-bot allowance does. That is why a sudden,......