Use the word penalty precisely
People often use “Google penalty” for any sharp fall in traffic or rankings. Google uses more specific public mechanisms. A manual action follows human review and appears in Search Console with a named issue. Automated spam and ranking systems evaluate pages without creating that notice. Measurement failures, deindexing, migrations, demand changes, and stronger competing results can produce the same falling graph without either one.
The distinction changes the work. A manual action has an affected scope, a documented policy, and a reconsideration path after the violation is fixed. A clean Manual Actions report means there is no manual action to remove. It does not mean the loss is imaginary; it means the evidence must come from somewhere else.
The Manual Actions report is the direct check
Open the Manual Actions report in the correct verified Search Console property. If Google has issued an action, preserve the exact wording and whether it affects all or part of the site. The example URLs help reveal the pattern but may not list every affected page.
Map the notice to the production source: a template, publishing workflow, serving rule, link-acquisition process, or compromised system. Repair every instance you control, verify the public result, and document the work. The full sequence is covered in Google manual action removal.
A clean report opens a different investigation
Google's spam policies describe behavior its automated systems may detect as well as behavior that can lead to manual action. A site can therefore lose visibility without receiving a manual notice. Broad core systems can also rank other pages more highly without declaring that your page violated a rule.
When the report is clean, use the first-party penalty checks and define the smallest affected page and query group. Compare Search Console with analytics, indexing, canonicals, response and rendering behavior, release history, demand, competitors, and the official update timeline. The complete sequence is in the ranking-loss investigation.
Choose the branch the evidence supports
| Evidence | What it establishes | Next route |
|---|---|---|
| A named Search Console manual action | A human reviewer identified a stated policy problem. | Repair the affected system, then request review. |
| A clean report and a page-family loss | No manual action exists; the affected group still needs explanation. | Investigate indexing, releases, demand, competition, and ranking systems. |
| A date near a public rollout | The rollout is a comparison point, not proof of cause. | Compare affected and unaffected groups using the core-update framework. |
| A third-party toxicity or visibility score | A tool observed its own metric. | Return to first-party reports before changing the site. |
Restore's commercial work begins from this classification. It does not sell a universal penalty score or promise that Google will return a previous position.