Have I had a Google algorithm penalty?

Traffic or ranking drops can feel like a 'penalty', but Google uses two distinct mechanisms: manual actions (human review) and algorithm updates (automated).

• Manual actions are applied for policy violations (e g spam, unnatural links,
• In Google Search Console, open Security & Manual Actions and check for
• If you have a manual action address the stated issue (e g

Traffic or ranking drops can feel like a 'penalty', but Google uses two distinct mechanisms: manual actions (human review) and algorithm updates (automated). Manual actions are reported in Search Console; algorithm updates are not. Many drops are due to algorithm changes that affect whole niches or quality signals rather than a manual penalty. Checking Search Console for manual actions and understanding the timeline of algorithm updates helps you know whether you need to request a review or improve site quality more broadly. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click…

Manual actions are applied for policy violations (e.g. spam, unnatural links, thin content, cloaking). Algorithm updates can reduce visibility for sites that no longer meet quality, relevance, or E-E-A-T expectations—without any manual action. Sometimes a drop is due to technical issues, stronger competitors, or lost links rather than a penalty. Assuming a penalty without checking can lead to the wrong fix; verifying in Search Console and correlating with known updates is important.

Common examples

A real-world example: after a site update, a business saw visibility drop for "Google algorithm penalty". They checked Search Console, found the blocking issue, fixed it, and regained impressions over the following crawl cycles.

How to diagnose

In Google Search Console, open Security & Manual Actions and check for any manual actions. If present, read the message and the affected issue type. Correlate traffic drop dates with Google's announced algorithm updates (e.g. Core updates, helpful content). Review your backlink profile and content for spam or quality issues. Check for hacked content or security problems. Use Search Console Performance to see which queries or pages were most affected.

Recommended fixes

If you have a manual action: address the stated issue (e.g. remove unnatural links, fix thin or spam content, resolve hacking). Document the fixes and request a review in Search Console. If no manual action: treat the drop as algorithm-related. Improve content quality, E-E-A-T, and technical SEO; remove or disavow bad links; ensure the site is clearly useful and relevant. Recovery can take months. Avoid quick 'penalty recovery' tactics that don't address the underlying cause. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task.