What Do You Do When Google Gives Your Site a Manual Action?

What Do You Do When Google Gives Your Site a Manual Action?

You find the exact violation, fix it everywhere it appears, then file one careful reconsideration request and wait. There is no shortcut and no appeal to a person. The process is deliberately slow, so the winning move is to fix thoroughly once rather than quickly three times.

Manual actions are rarer than the SEO panic industry suggests, and more survivable than most people fear. What makes them painful is that the clock only starts when your fix is genuinely complete.

Here is what Google actually documents, in the order you will need it.

What Is a Manual Action, and How Is It Different From an Algorithm Drop?

A manual action is a human reviewer at Google deciding your site breaks a spam policy. An algorithmic drop is a ranking change with no reviewer involved. They feel identical from the traffic graph and they are completely different problems.

Google is explicit about the practical consequence. Reconsideration requests are intended for sites with manual spam actions, and if your site's visibility has been affected solely by an algorithmic change, there is no manual action to be revoked and therefore no need to file a request.

This is the first fork in the road, and a surprising number of teams take the wrong branch. They spend a fortnight writing a reconsideration request for a problem that no human at Google ever flagged. Our guide to diagnosing an SEO traffic drop covers the other branch.

Where Do You Find Out You Have One?

In the Manual Actions report in Google Search Console, and by email to the verified owners. If nobody on your team has Search Console access, you can be under a manual action for months and only notice the traffic.

That is the boring lesson worth acting on before anything goes wrong. Verify the property, make sure more than one person receives the notifications, and check that those addresses still belong to people who work there.

The report is also where the fix is filed. Google's documentation describes the flow as fixing all issues across all affected pages, then selecting Request Review in the report and describing your fixes. Our Search Console guide covers the rest of the property setup.

Which Manual Actions Exist?

Google documents a defined list, which is helpful because it means the notice you received maps to a specific, published description rather than a vague judgement. Knowing the exact label is the difference between fixing the right thing and guessing.

The link-related ones are unnatural links to your site, described as a pattern of unnatural, artificial, deceptive or manipulative links pointing to your site, and unnatural links from your site, covering paid or manipulative outbound links.

The content ones include thin content with little or no added value, covering thin affiliate pages, scraped content and doorway pages, plus hidden text or keyword stuffing, cloaking and sneaky redirects, cloaked images, and sneaky mobile redirects.

There are also structural and host-level actions: a structured data issue for markup that violates guidelines, spammy free host where a significant fraction of sites on a free hosting service are spammy, site abused with third-party spam, user-generated spam, back button hijacking where the site interferes with the user's browser navigation, AMP content mismatch, site reputation policy, and major spam problems for aggressive techniques such as scaled content abuse and cloaking.

Is It Your Whole Site or Just Some Pages?

It depends on the action, and the report tells you. Google documents the scope alongside each type. Major spam problems applies to the entire site. Spammy free host applies to an entire hosting service. Unnatural links in either direction can be site-wide or partial.

Others are narrower. User-generated spam and site reputation policy actions typically hit some pages. Structured data issues hit the affected pages. Cloaked images are image-specific and sneaky mobile redirects apply to mobile pages.

Read the scope carefully before you start, because it determines the size of the job. A partial action on a forum section is an afternoon. A site-wide action for major spam problems is a rebuild of how you produce content.

Which Spam Policy Did You Break?

Every manual action traces back to Google's published spam policies, and those are worth reading properly rather than skimming. The document was last updated on 28 August 2026, with recent changes noted regarding the site reputation policy as it applies in the European Economic Area.

The policies most likely to catch a B2B site in 2026 are not the classic ones. Scaled content abuse covers generating many pages without user value, primarily to manipulate rankings, using AI tools or scraping. Site reputation policy covers hosting third-party content mainly to exploit established ranking signals rather than to serve users.

Expired domain abuse covers buying expired domains and repurposing them mainly to manipulate rankings with little user value. That one catches companies who acquired a domain for its backlinks and pointed it somewhere unrelated.

The rest of the list is the traditional set: cloaking, doorway abuse, hacked content, hidden text and link abuse, keyword stuffing, link spam, machine-generated traffic, malicious practices, misleading functionality, scraping, sneaky redirects, thin affiliation and user-generated spam. Our piece on Google's spam policies and AI content goes deeper on the newest ones.

How Do You Actually Fix It?

Completely, and everywhere. Google's documented flow requires you to fix all issues in all pages before requesting review. Partial fixes fail, and a failed review costs you weeks rather than days.

The practical method is to treat it as an inventory problem rather than a judgement problem. Enumerate every page that matches the violation pattern, decide page by page whether to fix, merge or remove, and then verify the outcome by crawling the site yourself rather than trusting a content management system count.

For link actions the work is different. You are documenting an effort, not just flipping a switch, because you often cannot remove links on sites you do not control. Keep a record of outreach attempts, what was removed, and what you disavowed.

Resist the urge to also make unrelated improvements. A reconsideration reviewer is checking one thing, and a sprawling change set makes it harder to see that the one thing is fixed.

What Goes Into a Reconsideration Request?

Three things, in Google's own framing. Explain the exact quality issue on your site, describe the steps you took to fix it, and document the outcome of your efforts. That structure is a checklist, not a suggestion.

Be concrete and unflattering about yourself. A request that says traffic dropped and we have improved quality gives a reviewer nothing to verify. A request that says we published 4,000 templated location pages with no unique content, removed 3,800 and rewrote 200, here is the list, gives them something to check in minutes.

Include evidence a reviewer can inspect without asking you for anything. A spreadsheet of affected URLs with their current status, a note of the date each change went live, and a plain statement of what you changed in your process so it does not recur.

Leave out the emotion. Explaining that a penalty is unfair or that a contractor did it without your knowledge does not change the assessment, and it uses space the evidence needs.

How Long Does a Review Take?

Google says most reconsideration reviews can take several days or weeks, and that link-related requests may take longer than usual. You will be told by email when the request is received, and again when the review completes.

The critical operational rule is in the documentation too. Do not resubmit your request before you get a final decision on the outstanding one. Resubmitting does not add urgency and it complicates the queue you are already in.

Plan the business around the wait. If a manual action has taken out a meaningful share of your organic traffic, several weeks is long enough that paid, outbound or partner channels need a temporary budget decision. Making that call early is easier than making it in week three.

What If the Request Is Denied?

You fix what you missed and file again. Google documents that when the violation is resolved, it will revoke the manual action. The documentation we could retrieve does not spell out a separate appeal path beyond resubmitting after a final decision, so treat a denial as information about your fix rather than a verdict on your site.

In practice a denial almost always means coverage, not interpretation. Pages you did not find, a subdomain nobody remembered, a staging environment indexed years ago, a partner microsite on your domain. Go looking for the part of the site you have never audited.

This is where an external crawl earns its keep. Teams reliably underestimate how many pages their own site has, and the ones they forget are exactly the ones that triggered the action.

How Do You Avoid the Next One?

Change the process that produced the pages, not just the pages. Almost every manual action we have seen discussed publicly traces to a system: a bulk page generator, an outsourced link campaign, an unmoderated user-generated section, a partner given publishing rights on your domain.

Two habits do most of the work. Review anything that creates pages at scale before it ships, and audit who can publish on your domain at least once a year. Site reputation actions in particular are usually a governance failure rather than an SEO failure, which we covered in our piece on Google's site reputation policy.

And keep reading the spam policies as they change. That page was updated in August 2026, and the categories that catch sites today did not exist a few years ago.

If you want help auditing a site for exposure before Google does it for you, or working through a live manual action, we are happy to walk through it. You can find us at phoenix.studio.