A store owner opens Search Console on a Monday morning and finds organic clicks down by two thirds since Friday. The first thought is the worst one: Google has penalized the site. Within the hour there is a half-written apology sitting in a reconsideration request, promising to clean up links nobody has looked at yet. Most of the time that reflex aims at the wrong target. A sudden drop is far more often an algorithmic re-ranking than a manual action, and confusing the two sends days of effort in the wrong direction.
What a manual action actually is #
A manual action is a decision made by a person at Google, not by a ranking system. A reviewer looked at a page or a whole site, judged that it breaks the spam policies, and applied a demotion or removal by hand. Because a human made the call, a human can be asked to reverse it once the problem is gone. That single fact is the reason the reconsideration process exists at all.
Algorithmic suppression is a different animal. Nobody reviewed the site. A system, usually a core update or one of the spam-fighting algorithms, re-evaluated the page against its current signals and ranked it lower. There is no notification, no named violation, and no way to appeal. Filing a reconsideration request against a core update accomplishes nothing, because there is no manual decision on file to reconsider.
Tell the two apart before you touch anything #
The distinction decides everything that follows, so it is worth settling first.
| Manual action | Algorithmic drop | |
|---|---|---|
| Who applied it | A human reviewer at Google | A ranking system, no person involved |
| Notification | Yes, shown in Search Console | None, the site owner is not told |
| Where you confirm it | The Manual actions report | By process of elimination |
| How it lifts | Fix, then an approved reconsideration request | Re-evaluation, usually at a later update |
| Can you appeal it | Yes, once the fix is done | No, the position is only earned back |
The trap is reading a clean report as an all-clear. A site can lose half its traffic to a core update and still show no manual action at all, because the two systems never touched each other.
Check the report first, it takes about a minute #
Search Console answers the question directly. Under the Security and Manual Actions section, the Manual actions report either states that no issues were detected or names the exact violation, its scope, and often a few example URLs. Google also sends a notification when it applies one, so an inbox with no message and a report with no issues together point away from a manual action entirely.
Reading this before anything else ends most penalty panics. It costs a minute, and it keeps the next week of work aimed at the real problem instead of a phantom one.
The types you are most likely to see #
Manual actions come in two shapes. A site-wide match hits the whole domain, and a partial match affects only certain pages or sections, which the report calls out specifically. The categories shift over time as new abuse patterns appear (site reputation abuse, for instance, was added as its own action in 2024), and Google keeps the current list in Search Console Help.
| Manual action | Usually triggered by | Typical scope |
|---|---|---|
| Unnatural links to your site | Bought or exchanged inbound links | Site-wide or partial |
| Unnatural links from your site | Selling links or manipulative outbound links | Site-wide or partial |
| Thin content with little added value | Auto-generated, doorway, or scraped pages | Often partial |
| Site reputation abuse | Third-party pages published to ride a host’s ranking | Partial |
| User-generated spam | Spammy profiles, comments, or forum posts | Often partial |
| Hidden text and keyword stuffing | Text stuffed for engines, not readers | Site-wide |
| Cloaking and sneaky redirects | Showing search engines different content | Site-wide |
| Pure spam | Aggressive, wholesale policy violation | Site-wide |
Fix the problem before you ask for anything #
A reconsideration request is not a plea for mercy, it is a report of work already finished. The reviewer is checking whether the violation is genuinely gone, so the request is only as strong as the cleanup behind it. Submitting one before the fix is complete is the most common reason a request comes back rejected.
The shape of the fix depends on the action. An unnatural-links match calls for auditing the backlink profile, removing or disavowing the manipulative links, and keeping the outreach records and the disavow file as evidence. A thin-content match calls for improving, consolidating, or removing the low-value pages rather than lightly editing a few sentences. For a partial match on one section, the work can stay scoped to that section, though the reviewer still expects the underlying pattern to be resolved rather than hidden from view.
Write a reconsideration request a reviewer will believe #
A reviewer reads a stack of these, and the approved ones share a pattern. They read like an honest incident report, not a negotiation. Vagueness and blame both signal work that is not yet done.
Requests that tend to succeed carry four things:
- A plain acknowledgment of the specific violation, named rather than softened.
- A concrete account of what was fixed and roughly when, page by page or link by link where it matters.
- Evidence a reviewer can check: the disavow file, a list of removed links, before-and-after examples of rewritten pages, records of outreach.
- A credible reason the pattern will not return, tied to a process change instead of a promise.
What happens after you submit #
There is no fixed timeline. A review commonly takes a few days to a few weeks, and link-related cases can run longer because the reviewer is checking a larger surface. Google responds through the same report, either lifting the action, rejecting the request, or noting partial progress with examples of what still needs work.
A rejection is not a dead end, and it is rarely about tone. It almost always means the reviewer still found the pattern the action was about, or a close relative of it. The path forward is more cleanup and a second, evidence-backed request, not a longer apology. Some link actions come back with specific example links still flagged, which is the reviewer showing exactly where to look next.
When the report is clean but traffic still fell #
If the Manual actions report shows no issues and rankings still dropped, the work moves to a different track, and no reconsideration request belongs there. The useful questions become whether the timing lines up with a known update, and whether the affected pages hold up against Google’s current guidance on helpful, reliable content.
Scale changes how that diagnosis runs. On a small site, comparing the drop against update dates and reading a handful of affected pages closely is usually enough. On a large site, the pattern is easier to see by segment, checking whether the loss concentrates in one template, one content type, or one section rather than spreading evenly. In both cases recovery tends to arrive only when the system re-evaluates the site, often around a later update, and no request will speed it up.
The honest version of the timeline #
Neither path offers a same-week guarantee. A manual action lifts when the violation is genuinely gone and a reviewer confirms it, which can take weeks. An algorithmic drop recovers when the site earns the position back against the current bar, on the system’s schedule and not the owner’s. The fast move is not the fast apology. It is opening one report, reading one line, and aiming the effort where it will actually land.