What Is a Google Penalty? Manual Action vs. Algorithmic Demotion

When a site's organic traffic drops sharply, the first question is usually "did I get penalized?" That's the wrong question. The one that actually determines what to do next is different: is this a manual action or an algorithmic demotion? The two differ completely in origin, visibility, and fix, and treating them as the same thing is the fastest way to lose weeks searching in the wrong place.

A manual action is imposed by a person. Google's official documentation explains that it issues a manual action against a site "when a human reviewer at Google has determined that pages on the site are not compliant with Google's spam policies." A Google employee reviews the site, decides it violates the policies, and applies a specific sanction. That decision gets logged with a reason and the affected URLs in Search Console's "Manual actions" report, whether it covers a single directory or the entire domain. And it can be appealed: Google documents a reconsideration request process where you explain what you've fixed.

An algorithmic demotion is not decided by anyone in particular. It happens when an algorithm update, whether a core update that overhauls the ranking system as a whole or a topic-specific update focused on spam or helpful content, re-evaluates the site and automatically decides it deserves a worse position. There's no human reviewer behind that specific case, no entry in Search Console saying "your site dropped because of this," and no button to appeal. Google confirms this plainly in its core update documentation: there's no site-specific notification, only a general note that an update has rolled out, published on the Google Search status dashboard.

Mixing up the two cases has a real cost. A site owner who suffers an algorithmic demotion and mistakes it for a manual action spends weeks combing through Search Console for a notice that will never appear. One who suffers a manual action and mistakes it for an algorithmic demotion runs the opposite risk: passively waiting for the next core update, when what's actually needed is fixing the flagged issue and requesting a review.

The table sums up the four questions worth answering whenever visibility drops: whether it shows up in any report, what causes it, when the effect appears, and how you respond.

The first place to look is the "Manual actions" report in Search Console, under Security & Manual Actions. A clean site shows a green checkmark. If Google has applied a sanction, the report shows the number of active actions and, once you expand each one, the exact reason (artificial links, valueless generated content, cloaking) and the pattern of affected pages, which can be a subset of the site, like one directory, or the whole domain.

Once the cause is identified, the reconsideration process follows the steps Google documents. First, fix the underlying problem: remove the artificial links, rewrite the valueless content, or eliminate the flagged technique, depending on what the report names. Second, confirm Google can crawl and index the corrected pages without added technical obstacles. Third, within the same report, select the option to request a review and describe in detail what changed. Google specifies what separates a good request from a weak one: it should explain the exact quality issue the site had, describe the concrete steps taken to fix it, and document the outcome of that work. A generic request along the lines of "we reviewed the site and believe it now complies" offers nothing verifiable and usually gets rejected.

The final step is waiting, with a caveat. Google states that most reconsideration reviews take several days or weeks, though link-related cases can drag on longer, since they require confirming the problematic link network has genuinely disappeared, not just from the most visible pages. During the process, Google sends email updates on the request's status, and the final outcome also shows up in the Search Console report itself.

One nuance worth flagging: a reconsideration request doesn't ask Google to re-evaluate the site's ranking overall, it asks Google to check whether the specific reason for the manual action still applies. If the answer is that it's fixed, Google lifts the manual action, but that doesn't guarantee recovering the exact same position the site had before: ranking again depends on every other quality factor of the site, not just the absence of the sanction.

If the Manual Actions report is clean and traffic has still dropped, the reasonable first hypothesis is an algorithmic demotion. There's no shortcut to confirming it with absolute certainty, since Google doesn't identify which specific sites each update affects, but there are signals that point that way.

The first is timing overlap. Google publishes on its Search status dashboard when each update's rollout starts and ends, both for core updates and for topic-specific spam or helpful content updates. If the traffic drop lines up with one of those windows, the algorithmic explanation gains weight over other causes, such as a technical issue on the site or a shift in audience behavior.

The second signal is the shape of the drop. A manual action tends to produce a sudden, localized collapse on the pages or directory named in the report. An algorithmic demotion tends to be more gradual and spread across several sections of the site at once, in line with what Google says about core updates: they don't hunt for specific pages to punish, they re-evaluate holistically which content deserves a better position for a given query.

The third is the complete absence of any individual notice, the most common source of confusion. There's no report, no email, and no Search Console notification saying "your site dropped because of the core update on such-and-such date." Google states this outright in its documentation: most sites don't need to worry about core updates and may not even realize one has happened. The only public confirmation is the rollout's start and end date on the status dashboard, with no mention of affected domains.

On timelines, Google is equally explicit: some changes take effect within a few days, but confirming the full effect of a core update on a specific site can take several months, because the systems need time to validate whether the content is genuinely helpful and reliable long term. If several months pass with no visible change, the official recommendation is to wait for the next core update rather than look for a one-off fix that doesn't exist.

• Check the "Manual actions" report in Search Console before drawing any conclusion about a traffic drop: rule out the easiest cause to confirm first.
• Track the core and spam update dates Google publishes on its status dashboard, and compare them against your own traffic graphs before looking for another explanation.
• If there's a manual action, fix exactly the problem the report describes, not a general "improve site quality" version: the reconsideration request gets evaluated against that specific reason.
• Document every step of the fix so you can describe it in detail in the reconsideration request.
• Facing an algorithmic demotion, work on E-E-A-T and genuine content quality: Google evaluates the site holistically and offers no appeal process equivalent to a reconsideration request.
• Keep your own log of site changes, such as migrations or redesigns, so you can rule them out as a cause before assuming a Google penalty.

• Filing a reconsideration request when the Manual Actions report is clean: with no active action, there's nothing for Google to reconsider.
• Waiting weeks for a Search Console notification after an algorithmic traffic drop, when that notification simply doesn't exist for this type of case.
• Treating black hat SEO as the only possible cause of a penalty: an algorithmic demotion from low-quality content can hit a site that has never used a manipulative tactic.
• Writing a generic reconsideration request that doesn't explain the specific problem or the steps taken to fix it: Google rejects it because there's nothing to verify.
• Writing off an algorithmic demotion after a few days, without giving a later evaluation cycle, sometimes months out, time to recognize the improvements made to the site.