Manual Actions & Penalties

A manual action is a human reviewer at Google deciding your site violates a specific policy and applying a demotion or de-indexation. Algorithmic demotions are noisy signals; manual actions are sealed verdicts. The recovery process is completely different and the writing of the reconsideration request is the highest-leverage thousand words you will ever produce.

TL;DR

Manual actions appear in one specific place: Search Console → Security & Manual Actions → Manual actions. If that page says “No issues detected,” you do not have a manual action. Period.
Algorithmic demotions and manual actions feel identical and have opposite recovery paths. Algorithmic recovery requires waiting for a refresh; manual recovery requires fixing the violation, ranking change is downstream of approval.
A reconsideration request that succeeds names the violation, shows evidence of remediation, and proves prevention. Generic apologies fail. The reviewer is reading dozens per day; specificity is the entire game.

The mental model

A manual action is like a building inspector issuing a stop-work order. The inspector cited a specific code violation, attached a notice to the door, and the building stays shut until you produce documented proof that the violation is fixed and won’t recur. Generic improvements — repainting the lobby, replacing the fire extinguishers — do not lift the order. Only addressing the specific cited violation does.

Algorithmic demotions, by contrast, are like a bond rating downgrade. The market reassessed you. There is no person to call. You improve the underlying fundamentals and the rating may or may not be revised at the next review.

The first practical implication: never write a reconsideration request for an algorithmic demotion. There is nothing to reconsider. The reviewer will mark the request as “no manual action exists” and your time is gone.

The second: the reconsideration request is a legal-grade document, not a marketing email. Treat it as if it were going to a regulator. Cite the specific policy, show the timeline of remediation, attach evidence, and make prevention claims you can defend.

Deep dive: the 2026 reality

Manual actions in 2026 are issued for a defined set of violations. The taxonomy as it appears inside the Search Console UI:

Manual action	What triggers it	Typical scope
Unnatural links to your site	Inbound links Google judges as manipulative	Partial demotion
Unnatural links from your site	Selling or exchanging links, sponsored links not marked rel=sponsored	Partial demotion
Pure spam	Cloaking, scraped content, automatically generated gibberish	Site-wide de-index
Thin content with little or no added value	Doorway pages, low-quality affiliate, scraped + lightly modified	Partial or site-wide
User-generated spam	Comment spam, profile pages, forum spam in sub-domains	Section-level
Spammy free hosts	Free-host services with widespread spam	Free-host wide
Hacked content	Content injected by a third party via compromise	Affected pages
Sneaky redirects	Redirecting users to unexpected destinations, including device-based cloaking	Partial demotion
Cloaking and/or sneaky JavaScript	Showing different content to Googlebot vs. users	Partial demotion
Hidden text and/or keyword stuffing	Hidden divs, white-on-white text, doorway keyword paragraphs	Partial demotion
AMP content mismatch	AMP page differs materially from canonical	AMP de-prioritized
Sneaky mobile redirects	Redirecting mobile users to different content	Partial demotion
Site reputation abuse (added 2024)	Hosting third-party content that exploits the host’s signals (e.g., parasite SEO on news domains)	Affected sub-paths
Scaled content abuse (added 2024)	Mass production of low-quality content, often AI-generated	Site-wide possible
Expired domain abuse (added 2024)	Buying expired domains to leverage residual authority for unrelated content	Site-wide
News and Discover policy violations	Issued separately for News/Discover surfaces	Surface-specific

The three 2024 additions — site reputation abuse, scaled content abuse, and expired domain abuse — are the most-issued manual actions of 2025–2026 by a wide margin. Google shipped a public enforcement wave for site reputation abuse on May 6 2024, and a second wave hit in March 2025 for scaled content abuse on AI-spun affiliate sites.

Algorithmic vs. manual: the diagnostic

Signal	Manual action	Algorithmic
GSC Manual Actions page	Shows the specific violation	”No issues detected”
Email from Search Console	You will receive one	None
Drop pattern	Often sharp, specific to violated section	Often gradual or aligned to update window
Recovery process	Fix + reconsideration request + approval	Fix + wait for classifier refresh
URL specificity	Often partial (specific paths flagged)	Usually broader

The diagnostic is binary: open the GSC Manual Actions page. If it has a row, you have a manual action. If it does not, it is algorithmic.

Reconsideration request anatomy

A successful reconsideration request has five sections. Order matters; reviewers scan the first 200 words.

Section	What it does	Length
Acknowledgement	Names the specific manual action and the policy it violates	2–3 sentences
Cause analysis	What we did, when, who did it, why	1–2 paragraphs
Remediation evidence	What we removed, fixed, or rebuilt, with URLs and dates	Bulleted, with links
Prevention measures	Process changes preventing recurrence	1 paragraph
Disavow / artifact	Link to the disavow file, audit log, or other artifact	1 line

A submitted disavow file is mandatory for “unnatural links to your site” actions. For other actions, the artifact is whatever proves you did the work — a public changelog, a screenshot of the deleted URLs, a Search Console URL removal log.

What gets rejected

Reviewer notes (compiled from public reports by Marie Haynes, Lily Ray, and Glenn Gabe across 2023–2025):

“We have removed all unnatural links” — without naming any specific examples — is rejected as boilerplate.
Generic apologies without specificity (“We sincerely apologize for any inconvenience”) are ignored.
Disavow files containing only domain: lines without a single URL-level disavow are flagged as low-effort.
Requests submitted within 48 hours of receiving the action are typically rejected as “insufficient remediation.”
Requests claiming “we did not do this” without an alternative explanation are dismissed.
For site-reputation-abuse actions, partial removal of the affected sub-paths is rejected — the policy requires full editorial control.

Approval timelines

Median time from submission to decision (2025 data):

Action type	Median decision time
Unnatural links to your site	14–30 days
Pure spam	21–45 days
Thin content / scaled abuse	30–60 days
Site reputation abuse	30–90 days
Hacked content	7–14 days

Multiple rounds are normal. The second submission must reference what changed since the first.

Visualizing it

sequenceDiagram
  participant S as Site owner
  participant G as Google reviewer
  participant W as Webspam team
  S->>G: Submits reconsideration request
  G->>W: Routes to specialist queue
  W->>W: Audits site against policy
  alt Violation remediated
    W->>G: Approve
    G->>S: Notification: action revoked
    G->>S: Re-evaluation in next index cycle
  else Insufficient remediation
    W->>G: Reject with reason
    G->>S: Notification: action remains
    S->>S: Read rejection, fix gap, resubmit
  end

Bad vs. expert

The bad approach

Subject: Reconsideration request

Dear Google Team,

We received a manual action on our website and are very sorry for any
violations. We have made many improvements to our website and have
removed bad content. We have also disavowed bad links. We hope you
will reconsider the manual action and reinstate our website. We
appreciate your time.

Best regards,
The Team

This is rejected within minutes. It names no policy, points to no specific remediation, attaches no artifact, and demonstrates no understanding of what the violation actually was. The reviewer has no signal to approve.

The expert approach

# Reconsideration request — example.com

## Acknowledgement
On 2026-02-14 we received a manual action under the policy "Scaled
content abuse" affecting the path `/blog/`. We accept the finding. Our
review confirms that 412 of the 540 articles in `/blog/` were produced
between January and August 2024 using GPT-4 and Claude with minimal
editorial review, in violation of Google's scaled content abuse policy.

## Cause analysis
The articles were produced under a contract with an external content
agency that we did not adequately supervise. The brief explicitly
required AI-only production with one-pass human formatting, no expert
review, no original research, and no first-hand evidence. The
arrangement was terminated on 2026-02-19.

## Remediation evidence
- 412 violating articles deleted with HTTP 410 Gone status on
  2026-02-22. Sitemap of deleted URLs:
  https://example.com/sitemaps/deleted-2026-02.xml
- 78 articles in the same path retained because they include
  documented author research; full audit log:
  https://example.com/audit/blog-retention-2026-02.csv
- 50 new articles produced 2026-02-23 onward by named in-house authors
  (bylines link to LinkedIn profiles); editorial workflow documented
  at https://example.com/editorial-policy
- New rel="author" markup, dateModified, and authoritative source
  citations added to all retained articles

## Prevention measures
We have implemented a four-stage editorial workflow: brief → first
draft by named human author → subject-matter expert review →
fact-check pass with citation. AI-assisted writing is permitted only
for outline generation and grammar review, not draft production.
Workflow is enforced via the editorial CMS — the Publish action is
blocked unless all four stages have signed off.

## Artifacts
- Editorial policy: https://example.com/editorial-policy
- Deletion sitemap: https://example.com/sitemaps/deleted-2026-02.xml
- Retained-article audit: https://example.com/audit/blog-retention-2026-02.csv
- Public changelog post explaining the change to readers:
  https://example.com/blog/editorial-changes-2026

We are committed to ongoing compliance and welcome any further
guidance.

This works because every claim is verifiable. The reviewer can click and confirm. The cause is named, the scope is bounded, the artifact list is checkable, and the prevention claim is backed by an enforced workflow rather than a promise.

Do this today

Open Google Search Console → Security & Manual actions → Manual actions. Take a screenshot regardless of result. If “No issues detected” appears, your problem is algorithmic — go to module 98.
If a manual action exists, click “Learn more” on the action row. Read the linked policy page in full and copy the exact policy text into a working document.
Audit your site against the policy. For “unnatural links to your site,” export your backlink profile from Ahrefs or Majestic and tag every link as natural, suspicious, or paid.
Build the disavow file if links are involved. Format: one URL or domain: per line, comments preceded by #. Submit at search.google.com/search-console/disavow-links.
Execute remediation. Delete with HTTP 410 for content violations. Remove sponsored links or add rel="sponsored" for outbound link violations. Restore from a clean backup for hacked content.
Document everything as you go. Keep dated screenshots, sitemaps of deleted URLs, audit CSVs, public changelog entries.
Wait at least two full weeks after remediation before submitting. Reviewers reject as insufficient anything submitted within 48 hours.
Write the reconsideration request using the five-section structure. Have a colleague who knows nothing about the violation read it; if they cannot identify what was fixed and how, rewrite.
Submit via the Manual Actions report → “Request Review” button. Save the submission text in your records.
While awaiting decision, set up monitoring in Search Console → Performance for the affected path. The first signal of approval is often a re-crawl and partial recovery before the official notification arrives.