A sharp loss of Google traffic can feel like a penalty. That does not make it one. In Google Search, a manual action has a specific meaning: a human reviewer has found that pages on a site do not comply with Google’s spam policies, and the action is reported in Search Console. A ranking drop without that notice needs a different diagnosis.
The distinction matters because the recovery paths are not interchangeable. A manual action can lead to a reconsideration request after the listed problem is fixed. A core update, indexing problem, technical release, demand change, or competitive shift cannot be appealed through the same process.
Before You Call a Ranking Drop a Penalty, Run This Triage
Start with evidence that can rule causes in or out. Google Search Console is the first place to check because a formal manual action is reported there. A clean Manual Actions report is useful evidence, but it does not prove that an algorithm update caused the loss.
| What you find | What it means | What to do next |
|---|---|---|
| A notice in the Manual Actions report | Google has issued a formal manual action against some or all affected pages. | Read the exact issue and scope, fix every affected instance, then request review. |
| A notice in the Security Issues report | The site has a security problem such as hacking or harmful behaviour. This is not the same report or diagnosis as a manual action. | Follow the security remediation path and verify that the compromised content or behaviour is gone. |
| Indexing changes after a release or site change | The loss may be technical rather than a penalty. | Check directives, canonicals, redirects, crawl access, rendering, templates and affected URL groups before rewriting content. |
| A sustained ranking decline near a confirmed Google update | An update may be relevant, but timing alone does not prove causation. | Segment pages and queries, confirm the update window, then compare the affected pattern with the type of update. |
| Clicks fall while rankings or impressions remain broadly stable | The problem may sit outside a penalty or broad ranking reassessment. | Review search demand, result-page changes, click-through rate, analytics tracking and query mix. |
This order prevents an expensive mistake: making site-wide changes before the problem has been classified. Google’s own guidance on debugging Search traffic drops treats algorithmic updates as one possible cause among several, not as the default explanation for every decline.
If Search Console Shows a Manual Action
Google defines a manual action as an action issued after a human reviewer determines that pages on a site are not compliant with its spam policies. The Manual Actions report shows the action and the affected pattern, which may cover part of a site or the entire site.
Read the notice before planning the cleanup
The label matters because different violations require different remedies. Google’s current spam policies cover practices such as cloaking, doorway abuse, hidden text and links, link spam, scaled content abuse, malicious practices and site reputation abuse. A generic ‘SEO penalty fix’ checklist is therefore less useful than the instructions attached to the actual action.
Scope can also be policy-specific. For site reputation abuse, Google documents different consequences for Search results shown inside and outside the European Economic Area, while affected site owners are still notified through the Manual Actions report. That is a good reason to use the notice itself as the source of truth instead of assuming every manual action behaves identically.
Fix all affected instances before requesting review
Google says that fixing only some affected pages does not earn a partial return to Search. If several manual actions are listed, each one needs to be addressed. The affected pages also need to be accessible to Google so the correction can be reviewed.
Once the listed problems have been fixed, the reconsideration request should explain the issue, describe the corrective work and document the outcome. Google says most reconsideration reviews take several days or weeks, with some link-related reviews taking longer. Resubmitting while a request is still outstanding does not speed that process.
Revocation of a manual action is not a promise that previous rankings will return. Removing the action removes that specific restriction. The pages still need to compete under Google’s normal ranking systems.
If the Manual Actions Report Is Clean
A clean report rules out a formal manual action. It does not tell you what the cause is. The next useful question is whether the loss is technical, algorithmic, demand-led, competitive, or simply a measurement problem.
Check site changes before blaming an update
Look at what changed around the first sustained decline. A new template, migration, redirect rule, canonical change, accidental noindex, robots.txt edit, internal-link change or rendering problem can affect many URLs at once. If a technical defect is confirmed, fix it immediately rather than waiting for an update rollout to finish.
Then segment Search Console data by page and query. Device, country and search type can help when the pattern is not site-wide. One folder losing visibility after a release tells a different story from many unrelated pages moving during the same period.
Use update timing as context, not proof
For a suspected core update impact, Google recommends confirming that the rollout has finished and then waiting at least a full week before making the before-and-after comparison. Its current core update guidance also says these updates are broad and do not target specific sites or individual pages.
Use the Google Search Status Dashboard for confirmed rollout dates. MOCOBIN’s guide to search engine algorithm updates covers the wider update-diagnosis workflow, including how to separate core updates, spam updates, technical failures and intent shifts.
If improvements are needed after a core update, avoid a cosmetic ‘recovery’ rewrite. Google advises against quick fixes and says meaningful reassessment can take anywhere from a few days to several months. It also notes that a site does not always need to wait for the next major core update to see an effect.
Three Recovery Moves That Often Solve the Wrong Problem
Submitting a reconsideration request without a manual action
A reconsideration request is for problems identified in a manual action or a Security Issues notification. It is not an appeal route for an ordinary ranking decline or core update. If the Manual Actions report is clean, there is no manual action to reconsider.
Disavowing backlinks because traffic fell
Google describes the Disavow links tool as an advanced feature that most sites do not need. Its guidance says backlinks should be disavowed only when there is a considerable number of spammy, artificial or low-quality links and those links have caused, or are likely to cause, a manual action.
That is a much narrower condition than ‘rankings dropped and the backlink profile looks untidy’. For an actual unnatural-links manual action, Google recommends trying to remove violating links first and using disavow for links that cannot be removed. For an unexplained traffic loss, a rushed disavow file can remove useful signals without establishing that links were the cause.
Rewriting the whole site from one date on a chart
A date correlation is a clue, not a diagnosis. Check the affected URL pattern, recent releases, indexing state and official update window before changing pages that may not be involved. A longer recovery checklist is not automatically a better one; each change should answer a finding you can explain.
Keep a Recovery Record That Another Person Can Verify
Penalty and ranking-drop work becomes easier to manage when the evidence is recorded before changes begin. The record does not need to be elaborate. It should make the reasoning traceable.
- Record the first sustained change: note when clicks, impressions or positions moved and which pages or query groups were affected.
- Record Search Console status: note whether Manual Actions, Security Issues and Page indexing reports showed anything relevant.
- Record site changes: include releases, migrations, template edits, redirect changes, content updates and tracking changes in the same window.
- Record official update dates: use confirmed Google rollout dates rather than third-party volatility alone.
- Record each corrective action: state what was changed, why it addressed the evidence and what result would confirm the fix.
This also keeps authorship and accountability clear. A technical diagnosis should be supported by the technical evidence, not by a byline implying first-hand audit experience that the author profile does not establish.
If the Manual Actions report is clean, do not call the loss a Google penalty yet. If it shows an action, follow the exact notice. That simple distinction keeps the recovery work tied to evidence rather than terminology.
