How to Check for a Google Penalty
Confirm whether Google actually penalized your site, or whether something else caused the drop, in three checks you can run in Search Console today.
To check for a Google penalty, look in Search Console's Security & Manual Actions report first — that confirms or rules out a manual action in under a minute. If it is empty, compare your traffic drop's timing against confirmed algorithm update dates and rule out a technical cause before you conclude it is algorithmic.
This is the first branch in a bigger decision tree. For the full picture once you know which kind you are dealing with, the organic traffic drop guide covers every path from here.
On this page
What counts as a "Google penalty," exactly?
People use "penalty" loosely, but Google's systems only really produce two distinct things that fit the word. A manual action is a human reviewer's decision, logged and visible to you. An algorithmic penalty, more precisely called an algorithmic demotion, is a ranking system deciding your site matches a pattern it demotes, and it is never logged anywhere you can see directly.
That difference is not academic — it decides where you spend your next hour. One has a report you can open right now; the other you have to infer from timing, breadth, and elimination. Confusing the two means either searching a report that was never going to show you an algorithmic issue, or agonizing over "what did we do wrong" when a two-line manual action notice was sitting in Search Console the whole time.
There is a third thing people also call a "penalty" that is neither of the above: a straightforward technical break. A bad deploy, a misapplied noindex tag, a robots.txt rule that blocks more than intended. It produces the same falling line in the same chart, but it is not a penalty at all — nothing judged your site, something just stopped working. Ruling this in or out belongs earlier in the process than most people put it, and this post treats it as a first-class third possibility rather than an afterthought.
Keeping these three separate matters because the fix for one does nothing for the other two. Filing a reconsideration request against a technical break wastes a review cycle on a report that was never the problem. Rewriting content to chase an algorithmic pattern when the real cause was a blocked section of the site fixes nothing, because the pages were never being crawled to be reassessed in the first place.
How do you check for a manual action first?
Open Search Console, go to Security & Manual Actions, and read what is there. An empty state with a green checkmark means exactly what it says: no manual action. There is no partial credit or hidden nuance to this report — it is binary [1].
If something is listed, you have your answer and your next step is not this post — it is Google manual action, which covers fixing the specific violation and filing a reconsideration request. Do not proceed to the algorithmic checks below if this report has an entry; fix the named violation first, because it will keep suppressing rankings regardless of anything else you do.
It is worth checking this report even when the drop looks nothing like what you'd expect a manual action to cause — a gradual decline over months, say, rather than an overnight cliff. Manual actions do not always land as a sudden drop; a partial-match action against a slow-growing section of the site can look exactly like a gradual algorithmic decline until you actually open the report and see it named there.
How do you check for an algorithmic penalty?
There is no report to open. Instead, build the case from three pieces of evidence: timing against Google's confirmed update calendar, breadth across queries and pages, and whether the affected content matches a pattern Google has publicly said it targets — thin content, unnatural links, aggressive ads, deceptive design [3].
| Manual action | Algorithmic penalty |
|---|---|
| Listed in Security & Manual Actions report | Never listed anywhere |
| Has a specific named violation | Inferred from pattern and timing |
| Lifted by a reconsideration request | Lifted by the site no longer matching the pattern |
| Can hit at any time, tied to a review | Usually coincides with a confirmed update rollout |
Run through this checklist in order — each step either confirms or rules out the algorithmic explanation before you move to the next.
Compare the drop date to Google's confirmed update list
A same-week match is meaningful evidence; a drop with no nearby update is a reason to look elsewhere first.
Check whether the drop is broad or narrow
Algorithmic penalties usually touch many pages and query types at once, not one template or one section.
Read your own content against Google's spam policies
Be specific: thin content, unnatural links, and deceptive practices are named categories, not vague quality complaints.
Check Search Console's traffic-drop debugging guidance
Google's own troubleshooting flow rules out several common false positives before it points you toward an algorithmic cause.
What's the fastest way to rule out a technical cause instead?
Before you commit to either penalty explanation, eliminate the boring and far more common one: something broke. Check whether the affected pages are still indexed, whether a recent deploy touched robots.txt or canonical tags, and whether Search Console's Page Indexing report shows a spike in excluded pages around the same date [4].
If a batch of pages moved from "indexed" to "crawled – currently not indexed" right when your traffic fell, you likely have a technical problem wearing a penalty's clothes — see crawled currently not indexed for the specific fix, which has nothing to do with content quality or links.
This step gets skipped constantly because it feels less interesting than diagnosing a penalty. It shouldn't. In our own audit work, a bad deploy or a misconfigured plugin explains a meaningful share of "penalty" tickets that arrive already convinced Google is punishing them — check our SEO audit approach if you want this ruled in or out systematically rather than by hunch. A ten-minute crawl comparison before and after the drop date settles it either way.
Two more checks worth ten minutes each: fetch a sample of affected URLs with a tool that renders JavaScript the way Googlebot does, and confirm the page actually looks the way you expect — a broken script can blank out the main content while the page still returns a 200 status, which looks fine to a human glancing at it in a browser with a cached version loaded. Then check whether your CMS or hosting platform shipped an update around the drop date; a surprising number of "algorithm" tickets trace back to a platform-level change nobody on the marketing team was told about.
What do you do once you've confirmed which kind it is?
A manual action gets a specific fix and a reconsideration request. A confirmed algorithmic pattern gets a broader quality response — and if that pattern points at thin or unhelpful content specifically, helpful content recovery is the narrower, faster path than a generic core update response. A technical cause gets a technical fix, and often recovers within days of the fix shipping rather than the weeks or months either penalty path takes.
Whichever it turns out to be, write down the evidence that led you there. If the drop resurfaces in six months, that record is what tells you whether history is repeating or whether this is something new.
Keep the record short and factual: the date the report or the chart first showed the change, which report you checked and what it said, and the exact fix you shipped with its date. Six months from now, when someone asks "didn't this happen before," a two-paragraph note settles the question in a minute instead of everyone trying to remember what actually happened from memory, which is usually wrong in some detail that turns out to matter.
Questions people also ask
Is there a free tool that tells me if Google penalized me?
Search Console's Security & Manual Actions report is that tool, and it is free and official. Nothing else can confirm a manual action, and nothing can confirm an algorithmic penalty directly, because Google does not publish those against individual sites.
Can a site have both a manual action and an algorithmic drop at once?
Yes, though it is uncommon. Check the manual actions report first regardless, since it takes two minutes and rules out the more mechanical explanation before you spend time on the harder, algorithmic diagnosis.
Does a drop in rankings always mean a penalty of some kind?
No. Technical breakage — a bad deploy, a blocked section, a broken sitemap — produces the same shaped graph as a penalty and is far more common. Rule out technical causes before you conclude the algorithm targeted you specifically.
How long does an algorithmic penalty last?
There is no fixed sentence to serve. An algorithmic reassessment lifts once your site no longer matches the pattern that triggered it, which is why the fix is changing what caused it rather than waiting out a timer.
Sources
- Manual actions report - Search Console Help — Google Search Console Help (checked 23 September 2026)
- Debug Google Search Traffic Drops — Google Search Central (checked 23 September 2026)
- Spam Policies for Google Web Search — Google Search Central (checked 23 September 2026)
- Page indexing report - Search Console Help — Google Search Console Help (checked 23 September 2026)
Find out which of the three it actually is
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Ibrahem HelalCo-founder
Leads strategy and delivery.
Works on: SEO, GEO
Reviewed before publishing by Jeremy Zava, Co-founder.
- Organic traffic drop: find the cause and fix itWhy organic traffic drops, how to tell tracking, seasonality, updates, penalties and technical faults apart, and what recovery really takes.
- Google Manual Action: How to Fix It and RecoverA Google manual action is a human reviewer's penalty. Here's how to read the notice, fix the real cause, and write a request a reviewer approves.
- Helpful Content Recovery: A Step-by-Step PlanHow to recover from a helpful content hit: what the classifier actually penalizes, the fixes that move it, and a realistic timeline for getting traffic back.
- Fix Crawled – Currently Not Indexed PagesGoogle crawled your page and chose not to index it. Here's what that status actually means, why it happens, and how to get the page indexed.