Manual Actions in Google Search Console: How to Detect Them and Request a Review

Manual actions are the only Google penalty that arrives signed in a Search Console report and is lifted through a formal process. This is the manual for that process: how to read the report, what each type requires in 2026, and how to write a review request that stands a chance.

What a Manual Action Is and How It Differs From an Algorithm Update

Human Review, Not an Automated System

The documentation puts it plainly: Google issues a manual action "when a human reviewer at Google has determined that pages on the site are not compliant with Google's spam policies." It is not a threshold and not a model that misfired: it is a decision with a named author.

An algorithm update moves thousands of sites at once and comes with no report. A manual action targets your domain and is documented. If the report is clean, drop that theory and work through the traffic drop diagnosis for other causes.

Why the Site Disappears Without Any Visible Indication

Google says it directly: these problems cause affected pages to "lose ranking or even disappear from search results entirely without showing any visible indication to users." Visitors just stop finding the page. The owner usually notices a drop in impressions, not an email.

What a Manual Action Won't Fix (Honest Expectations)

There is no partial recovery: in Google's own words, "fixing the issue on just some pages will not earn you a partial return to search results." No setting lifts it either, and no fixed timeline exists.

How to Check Whether Your Site Has a Manual Action

The Manual Actions Report: From Green Check to Red Count

In Search Console, open "Manual actions". A clean property shows a green check and a no-issues message; otherwise you get one card per action with its type, scope and a sample of examples. It is the only source: there is no public notice.

Message Center and Email: What to Save and Why

Google notifies you in the Message Center and at the verified email on the property. Save the text and the date: the first line of a good request is usually "we received the manual action on date".

Real Scope: URL Patterns vs. "Affects All Pages"

Each action shows a URL pattern, and Google warns that "not all pages with that pattern are necessarily affected." A site-wide action carries the explicit "Affects all pages" label. Mixing the two up leads to rewriting an entire catalog when one section was enough.

The Report Almost Nobody Checks: Security Issues

"Security issues" warns when Google finds that a site "might have been hacked, or used in ways that could potentially harm a visitor or their device" (Search Console guide). A compromised site often collects both warnings: the hack and the manual action.

The Manual Action Types That Exist Today (and What Each One Asks For)

The catalog changed four times between April and August 2026, according to the official changelog. These are the names as they appear in the interface.

Unnatural Links and Link Schemes

Bought links, mass exchanges, blog networks. Google asks you to identify the source, remove the links or mark them with rel="nofollow" and, when removal is impossible, disavow them. It is the slowest review; the operational detail is in auditing your backlinks.

Thin Content With Little or No Added Value

Pages built to capture traffic without adding anything of their own: doorway pages, duplicated text, unreviewed auto-generated summaries. Fix it by deleting, merging or rewriting; adding a paragraph does not count.

Cloaking and Sneaky Redirects, Mobile Included

Showing Google one thing and visitors another, including redirects only mobile devices see. Fix it by removing the deceptive variant, not by moving it to another URL.

Hidden Text, Keyword Stuffing, and Cloaked Images

Text matching the background, hidden blocks stuffed with repeated keywords, images that show something other than their alt text says. Easy to fix and easy to cause by accident while building a template.

User-Generated Spam and Sites Abused With Third-Party Spam

Two different cases. In the first, your comments or forum fill up with spam and you are responsible for it; the practical guide is UGC and SEO. In the second, a third party injects spam pages into your domain and the action lands without you doing anything.

Structured Data That Doesn't Match the Page

Markup that claims reviews, prices or ratings that are not on the visible page. Align the JSON-LD with the content or remove the markup entirely.

The 2026 Additions: Back Button Hijacking and Site Reputation

In April, Google added a policy against back button hijacking: manipulating browser history so the back button cannot take visitors off the site. In August it updated the site reputation policy with a regional nuance: outside the European Economic Area pages can receive a manual action; inside it, content is categorized separately from the main domain. That is not a pardon: that content competes on its own.

How to Actually Fix the Problem (the Step Most People Half-Do)

Fix Every Affected Page, Not Just the Examples

The examples in the report are a sample, not a closed list. If the pattern is /deals/, review every URL that matches it, including those that never appeared in the sample.

Keep Pages Accessible During the Review

Google is explicit: affected pages "must not require a login, be behind a paywall, or be blocked by robots.txt or a noindex directive." The classic mistake is redesigning the site, leaving the staging noindex in production and submitting the request with that noindex live.

Document the Evidence With Dates and URLs

A sheet with four columns: URL, problem, action taken, date. It is not bureaucracy; it is what you paste into the request.

When to Wait Before Requesting a Review

If the fix is not deployed, the review is wasted. Ship it, confirm Google is already crawling it, and only then submit: one day of waiting costs less than a month of rejection.

How to Write a Review Request That Can Be Approved

The Three Things Google Asks You to Explain

The reconsideration request guide asks for three things: explain the exact quality issue, describe the steps you took to fix it, and document the outcome. No pleas and no business history.

A Four-Paragraph Template

We received the manual action on <date> for <type> on <pattern>.
The problem: <what it was and why it happened>.
What we fixed: <actions, dates, number of URLs>.
Outcome: <verifiable evidence and example URLs>.

Mistakes That Delay or Sink the Request

Submitting without fixing, fixing only the examples, replacing evidence with promises, leaving pages inaccessible to the reviewer, or resubmitting before a decision. Any of the five stretches out the process.

How Long the Review Takes and Why You Must Not Resubmit

Timelines are qualitative: reviews "can take anywhere from a few days to a few weeks," and link ones take longer. Google emails you on submission and on the decision, and asks you not to resubmit "until you're notified of the final decision."

Why the Rules Expanded to AI Search in 2026

Spam Policies Apply to Generative AI Responses Too

Since May 15, 2026, the spam policies explicitly cover "attempts to manipulate generative AI responses in Google Search." Text written for AI summaries now falls under the same policy as old-school hidden text.

A Spam Report Can Now End in a Manual Action

The April clarifications, on the 14th and 23rd, confirm that Google may use third-party spam reports as the basis for a manual action. Your competitor has a form.

What Changes for AI-Assisted Publishing (and What Doesn't)

Nothing new if the content is reviewed and adds something. What changes is the excuse: "a model wrote it" is not a defense against a thin-content action. If your site depends on how it appears in AI answers, review the Search Console generative AI control.

Checklist: From Alert to Recovery in 9 Steps

1. Read the "Manual actions" report and note type, URL pattern and date.
2. Check "Security issues" in case the server is compromised.
3. Inventory every URL in the pattern, not just the examples.
4. Fix the cause on each affected page.
5. Deploy and verify access without login, paywall, robots.txt or noindex.
6. Document each URL with the action taken and its date.
7. Draft the request around the three points: problem, steps, outcome.
8. Submit once and wait for the decision by email.
9. If approved, measure recovery in impressions over weeks.

A manual action is not lifted by a trick: it is documented, fixed and explained. Whoever does those three things in order has the process on their side.