Your traffic fell off a cliff. Maybe overnight, maybe over several weeks. You’re checking Search Console, refreshing Analytics, and wondering whether you got hit by an algorithm update or something worse.

Here’s the first thing to establish: those are not the same problem. An algorithm update and a manual penalty are handled completely differently, and confusing them is how businesses spend months doing the wrong work.

This guide is about the manual penalty path — what it is, how to confirm it, what to fix, and how to actually get out of it. If your situation turns out to be algorithmic, you’ll know that by the end of the first section, and the path forward looks different.


Manual Penalty vs. Algorithm Update: Know Which One You Have

A manual action is exactly what it sounds like. A human reviewer at Google looked at your site, decided it violated their spam policies, and applied a penalty. You get notified in Search Console. Google tells you what they found. It affects your site specifically, not sites broadly.

An algorithm update is automatic, affects many sites at once, and produces no notification whatsoever. Google adjusts how it weighs certain signals, and sites that benefited from the old weighting lose ground while sites that align with the new signals gain. There is no “fix” in the traditional sense. There is no reconsideration request. Recovery from an algorithm update is about improving the underlying quality of the site until the algorithm agrees with that assessment.

Checking which one you’re dealing with takes about 30 seconds.

In Search Console: go to Security & Manual Actions in the left sidebar, then click Manual Actions. If you see “No issues detected” with a green checkmark, your traffic problem isn’t a manual penalty. If you see an active action, it will tell you what type it is and which pages are affected.

That’s your starting point. Everything else follows from that answer.


What Manual Actions Actually Cover

Google’s spam policies are the rulebook. Manual actions get applied when a reviewer finds a site violating them. The most common violations in 2026:

  • Unnatural links. Either links pointing to your site that look like they were bought, built at scale, or otherwise manipulated. Or links going out from your site that appear to be part of a scheme. This is the most common manual action most SEOs encounter.
  • Thin or low-quality content. Pages with minimal original value. Scraped content, templated pages with only slight variations, AI-generated content that adds nothing to what already exists. Google has been more aggressive here since the March 2024 updates.
  • Cloaking. Showing Google one version of a page and users a different version. Usually deliberate. Almost always penalized hard.
  • Structured data abuse. Marking up content as a review or FAQ when the page doesn’t actually contain that content. This one surprises people who added schema without thinking through what it was actually claiming.
  • Hacked content. Your site got compromised and someone injected spam pages, redirect scripts, or links to unrelated sites. This is the penalty type where the webmaster is usually a victim, not the cause. But it still needs to be addressed.
  • Site reputation abuse. A newer enforcement area. This is when a site with established authority publishes third-party content (often thin affiliate or coupon content) that exists primarily to borrow that site’s ranking signals rather than provide genuine value to users. Google clarified and strengthened this policy in late 2024.

Manual actions can affect specific pages, a section of the site, or the entire domain. The notification in Search Console tells you which.


Step One: Read the Actual Manual Action Notification

This sounds obvious. People skip it anyway.

The manual action report tells you the violation type, a short description, and example URLs. Read all of it. Google is not being coy. They’re telling you specifically what the problem is. Whatever the action says, that’s what you’re fixing. Not a general cleanup. Not a broad site audit. The specific thing they identified.

Some people receive a manual action, immediately panic-audit everything, change a dozen unrelated things, and submit a reconsideration request without properly addressing the actual violation. That request gets denied. They’re confused. Then they submit again. It gets denied again. Months pass.

Read the notification. Fix what it says. Document that you fixed it.


Step Two: Go Through Google’s Search Essentials

Before you start fixing anything, read Google’s Search Essentials. Not because the documentation will surprise you, but because you need to understand what standard you’re being held to before you can demonstrate that you’ve met it.

The documentation covers the technical requirements Google expects of any site, the content policies, and the spam policies in detail. If your site received a manual action, you’re currently on the wrong side of at least one of these. Knowing exactly where that line is matters before you claim in a reconsideration request that you’ve crossed back over it.


Step Three: The Actual Audit Work

This is where the manual effort lives. What you’re auditing depends on the penalty type, but most manual action recoveries involve at least some version of the following.

Backlink audit (for link-related actions)

Pull your link profile from Search Console’s Links report. You want to identify links that look bought, built at scale through a service, placed on obviously irrelevant or low-quality sites, or generated through any kind of scheme.

Signals that a link is problematic: it came from a site that exists only to sell links, it uses exact-match commercial anchor text pointing to your money pages, it appeared in large numbers over a short time period, it’s sitewide (footer or sidebar across an entire domain), or the linking site has nothing to do with your industry.

The goal isn’t to disavow everything with a low domain authority score. Google already ignores most junk links. The goal is to identify the pattern that triggered the manual review and dismantle it.

Try to get the links removed first. Contact the site owners. Keep a record of every outreach attempt — the date, the domain, whether you heard back. That documentation belongs in your reconsideration request later.

For links you can’t get removed, Google provides a disavow tool. You build a text file listing the URLs or domains you want Google to ignore when evaluating your site. Submit it. Google is explicit that this tool is for advanced use only, that most sites will never need it, and that using it carelessly can hurt you. They’re not being dramatic about that last part. Disavow things you know are problematic. Don’t use it as a general backlink cleanup exercise.

Content audit (for quality-related actions)

If the penalty is about thin content, go find the thin content. Look for pages with very little original text, pages that were generated from AI or templates with only slight variable changes, pages that scrape or closely paraphrase content from other sources, and pages that exist primarily to target a keyword rather than to say something useful to an actual person.

Google’s framing for what good content looks like in 2026: Does it provide original information or analysis? Does it demonstrate real first-hand knowledge? Would the person who read it actually find it useful? If the honest answer to those is no, those pages need to either be substantially improved or removed. Removing and redirecting thin pages can actually help faster than attempting to improve them all in place.

Technical checks (for any action type)

Make sure Google can actually reach the pages you’re trying to get reviewed. Googlebot shouldn’t be blocked by robots.txt on any affected pages. They shouldn’t require a login. They shouldn’t be behind a noindex tag.

The URL Inspection tool in Search Console lets you see exactly what Google sees when it renders a specific page. Use it on affected URLs before you submit a reconsideration request.

For hacked sites

Google has dedicated documentation for this. The short version: identify what was injected (spam pages, redirects, malware), remove it, secure the vulnerability that allowed the hack, then request a review. The Search Console security issues report is where you’ll see this flagged separately from manual actions.


Step Four: Fix All Affected Pages Before You Submit Anything

The manual action report shows which pages or URL patterns are affected. You need to fix all of them before you submit a reconsideration request. Not most of them. All of them.

Google is specific about this: fixing the issue on some pages does not earn a partial return to search results. If there are multiple manual actions on the same site, you address all of them before requesting review.

This is also why partial cleanups followed by premature reconsideration requests burn time. Each rejected request resets the clock. You’re better off doing the cleanup thoroughly once than submitting three inadequate requests over six months.


Step Five: The Reconsideration Request

A reconsideration request isn’t an apology letter. It’s documentation. Google’s reviewers need to understand what the problem was, what you did to fix it, and why it won’t happen again. That’s the entire job of the request.

What to include:

  • A clear statement of what the manual action was
  • A description of what caused it (be honest; if an SEO you hired built garbage links, say so)
  • A specific account of what you did to fix it — pages removed, links disavowed, domains you reached out to, content improved or deleted
  • Evidence where possible: outreach logs, before/after screenshots, a summary of what changed
  • What you’ve done to prevent recurrence

What not to do: write a vague paragraph explaining that you’ve “committed to high-quality SEO practices going forward” without describing any specific action you took. Reviewers read these all day. Vague promises get rejected.

Submit the request through the Manual Actions report in Search Console. The interface has a “Request Review” button attached to each active action.

Timeline: most reviews take several days to a few weeks. Link-related reviews can take longer. Google will email you when the review is complete. Do not resubmit while a review is pending.


What Happens After the Penalty Is Lifted

Here’s something the original copy on this topic usually leaves out: lifting the manual action doesn’t automatically restore your prior rankings.

For link-related manual actions, Google has been explicit that when their systems remove the credit previously given to spammy links, any ranking benefit those links generated is gone and won’t come back. You’re starting from a cleaner baseline, but you’re starting. Recovery is gradual and depends on the underlying quality of the site now that the manipulative signals are gone.

For content-related actions, recovery is faster if the underlying site is actually good. If you removed thin pages and replaced them with content that genuinely serves search intent, Google’s systems will reassess over time. Search Console will start reflecting the change in coverage and impressions as Google recrawls and re-indexes the cleaned-up site.

Monitor Search Console for changes in coverage, the Manual Actions report to confirm the action was lifted, and performance data for the queries that matter to your business. Don’t refresh Analytics every hour. These things move on Google’s timeline, not yours.


A Note on What Caused This

It’s worth being direct about this, because a lot of penalty recoveries trace back to the same place: a previous SEO or agency did work that violated Google’s policies, and the current site owner is now cleaning it up without fully understanding how the mess happened.

If you hired someone to “build backlinks” and they used a link network, a link farm, or a bulk outreach service that placed links on irrelevant sites, that’s the likely origin. If you hired someone who produced large volumes of templated or AI-generated content as a content strategy, that may have triggered a quality action. If your site was on a shared hosting plan and got compromised alongside other hacked sites, that’s a different category entirely.

Understanding how it happened matters for two reasons:

First, your reconsideration request is stronger if you can accurately describe the cause.

Second, and more practically: if you don’t understand what caused it, you’re more likely to hire someone who does the same thing again.


The Honest Timeline

Manual penalty recovery takes time. A straightforward link cleanup with a clear disavow file and a well-documented reconsideration request can be resolved in a few weeks. A site-wide content quality issue that requires substantial rewrites across hundreds of pages could take several months of improvement before Google’s systems register meaningful recovery.

Anyone who tells you they can fix a manual penalty in two weeks, or guarantees specific ranking recovery by a specific date, is either working on a trivially simple case or telling you what you want to hear.

Do the work thoroughly. Document it. Submit the request once, clearly. Then let Google’s reviewers do their job.

Author

Brennan Flentge

Published

March 16, 2026

Share
About the author:
Brennan Flentge is an SEO consultant at Digital Beeline in Phoenix. He wrote this bio all by himself.

Leave A Comment

Chat with a digital expert!