How to check for a Google penalty

Short answer: there's only one way to confirm a Google penalty in the strict sense. Open the Manual Actions report in Search Console. If there's a manual action, Google tells you there, and in the Search Console message center. If there isn't one, your drop has another cause: a Google ranking update, a technical problem, a tracking fault, a site move or a change in demand. None of those is a penalty, and none of them is fixed by asking Google to reconsider.

This guide is the order I check things in. It starts with the quick, certain checks and ends with the ones that take judgment.

Is my website penalised by Google? The quick check

Work down the list. Stop at the first yes.

1. Manual Actions report shows an action? That's a manual action. Go to "If there is a manual action" below.
2. Security issues report shows an issue? That's a security problem, not a penalty. It still needs fixing first.
3. Did the drop show up in Search Console, or only in your analytics? If only in analytics, check your tracking before anything else.
4. Did you launch, move or change the site around the time of the drop? Check indexing and redirects.
5. Does the same dip show up at the same time last year? It may be seasonal.
6. Does the drop line up with a Google ranking update? It may be an algorithm drop.
7. None of the above? Look at which pages and queries lost. The pattern usually points to the cause.

Step 1: check the Manual Actions report (and Security issues)

Open the Manual Actions report in Search Console for your site. Google uses this report to show any manual action issued against the site, and the site's manual action history.

A manual action is when a person at Google finds that pages on your site break Google's spam policies. Google says most manual actions mean pages or the whole site are ranked lower or left out of search results. If there's one, the report lists the type, a short description, and whether it affects the whole site or certain page patterns. Google also says it will notify you in the report and in the Search Console message center.

While you're there, open the Security issues report too. Google uses it to show if your site was hacked or does something that could harm visitors, such as phishing or malware. Pages with a security issue can show a warning in search results or in the browser, and Google says that can bring Search traffic down. It's not a manual action, but it needs fixing first.

You need access to the site's Search Console property to see either report. That's the one thing no outside tool can do for you.

Step 2: rule out tracking and reporting problems

Before you blame Google, make sure the drop is real.

• Compare Search Console with your analytics. Search Console's Performance report counts clicks from Google Search. If clicks there are steady but your analytics shows a fall, the problem is likely in tracking, not in Google. Common causes are a lost tracking tag after a release, a consent banner change, or a filter change.
• Check Google's Data anomalies page. Google says a drop can come from a change in its data processing or a logging error, and it lists known issues there.
• Check impressions as well as clicks. Google's guide says that if impressions hold steady but clicks fall, your titles and snippets may be less appealing, or other results may have richer listings. That's a different problem from losing rankings.

Step 3: rule out site problems (indexing, robots, redirects, migrations)

Next, check the site itself. Google lists technical issues as one of the main causes of Search traffic drops. Examples include the server being down, robots.txt problems, pages returning "not found", or a noindex tag left on pages by mistake.

• Page indexing report: look for a rise in pages that aren't indexed, and read the reasons Google gives.
• Crawl stats report: look for a spike in errors around the drop date.
• URL Inspection tool: check a few of the pages that lost the most.
• Is Google being blocked? If your firewall or bot protection is challenging or blocking Googlebot, pages can drop out without anyone noticing, because the site works fine for people. BOTCHECK reads your access logs and shows whether verified Googlebot got 403, 429, 5xx or a challenge. The method is in how to check Googlebot in your access logs.
• Removed pages: if you deleted or merged pages around the drop date, check they return what you meant: 404 or 410 for gone, a 301 to a close match for moved. GONE checks a list of removed URLs against what each one should do, including soft 404s and leftover sitemap entries. See 404 vs 410 vs soft 404.
• Lots of new "not indexed" reasons: RAUM reads a Page indexing export and turns the reasons into a list of live checks, so you can see which ones are real problems.
• Site moves and migrations: if URLs changed, Google says rankings can move around while it recrawls and reindexes. A medium-sized site can take a few weeks. Larger sites can take longer. If the drop isn't recovering, check redirects first. Missing or broken redirects are the usual culprit. If this is you, see SEO migration services.

Step 4: check for seasonality and changing demand

Sometimes fewer people are searching. Google's guide suggests two checks in the Performance report:

• Set the date range to the last 16 months, so you can see whether the same dip happened last year.
• Compare the last 3 months year over year, then click through the queries, pages, countries and devices tabs to see where the change sits.

For your top queries, check Google Trends. If interest fell across the web, not just for you, it's a demand change, not a penalty.

Step 5: line up the drop with Google's ranking updates

If there's no manual action, no technical fault and no seasonal pattern, compare your drop date with Google's list of ranking updates. Google posts notable updates, including core updates and spam updates, on the Search Status Dashboard with their start dates and how long they ran.

For core updates, Google's advice is specific:

• Check that the update has finished rolling out, and note its start and end dates.
• Wait at least a full week after it completes before you analyse.
• Then compare a week after the update with a week before it started.

Google also says that if you lose traffic after a core update, there may be nothing fundamentally wrong with your content. Small moves up and down happen all the time. A big drop across lots of searches is different. That's when I'd look at the whole site properly, not just a few pages.

Be honest with yourself about what the timing tells you. If your drop lines up with an update date, that's a strong clue, but it's not proof. Nothing in Search Console will ever say "you were hit by this update". So I use the date as one piece of the picture, next to the pages and searches that actually lost traffic.

What free and online penalty checker tools can and can't show

There are plenty of free and online "Google penalty checker" tools. They can be useful, but be clear about what they do.

What they can do:

• Show your estimated traffic over time, from the tool's own data.
• Plot Google update dates on that chart, so you can see if a drop lines up with one.
• Save you building the timeline by hand.

What they can't do:

• See your Manual Actions report. Only people with access to your Search Console property can see it.
• Confirm that an algorithm update caused your drop. They show timing, not cause.
• See your real clicks. Tool traffic figures are estimates. Your Search Console data is the real record.

So use a tool for the timeline if it helps. Use Search Console for the answer.

What is a Google penalty? Manual action vs algorithm drop

"Google penalty" gets used for two different things.

Only the first is a penalty in Google's own terms. The second is your pages being re-judged, which can happen to sites that have done nothing wrong.

How to recover from a Google penalty

It depends which kind it is. Here's the honest version.

A manual action:

1. Read the action in the Manual Actions report. It says what the issue is and whether it affects the whole site or some pages.
2. Fix it on every affected page. Google says fixing only some pages won't earn a partial return.
3. Write down what you found, what you changed and what the result was. Google's help says a good request explains the issue, the steps you took and the outcome.
4. Select Request Review in the Manual Actions report.
5. Wait. Google says most reviews take several days or weeks, and some, such as link-related ones, can take longer. You get an email when it's received and when it's done. Don't send another request while one is open.

There's no guarantee Google will lift it, and no fixed timeline for traffic afterwards. If the request is rejected, Google tells you, and you fix what's still wrong before you try again. My reconsideration request guide goes through each step.

An algorithm drop: there's nothing to request. Recovery means improving the pages that lost, then waiting for Google to reassess them. Google's core update guidance says some changes can take effect in a few days, but it can take several months for its systems to confirm the site as a whole has improved. If a few months pass with no effect, that could mean waiting for the next core update, though smaller unannounced updates can pick it up too.

What to do next

If there is a manual action: fix the issue on every affected page first. Google says fixing only some pages won't earn a partial return to search results. Then select Request Review in the Manual Actions report and explain what you fixed. My guide on how to write a reconsideration request for Google covers the method step by step.

If there's no manual action: don't send a reconsideration request. There's nothing for Google to reconsider. Work out which pages and queries lost, what changed, and what each fix is worth. That's what a traffic drop audit does.

If you'd like help either way: Google penalty recovery is where I work through manual actions with you, from diagnosis to the request.

Google penalty check FAQs

How do I check if I have a Google penalty? Open the Manual Actions report in Search Console. If Google has issued a manual action, it's listed there, and Google also sends a message in the Search Console message center. If the report shows nothing, your drop isn't a manual action. Check tracking, site changes, seasonality and Google's ranking updates instead.

Can a Google penalty checker tool tell me if I've been penalised? Not for certain. A tool can't see your Manual Actions report, and it can't prove an update caused your drop. Most can show whether a drop lines up with a known update date. That's a useful clue, not an answer.

Does Google tell you if you have a penalty? For a manual action, yes, in the Manual Actions report and the Search Console message center. For an algorithm drop, no. There's no notice, because nothing has been issued against your site.

What is a manual action? It's when a person at Google finds that pages on your site don't comply with Google's spam policies. Google says most manual actions mean affected pages or the whole site are ranked lower or left out of search results.

Is a traffic drop after a core update a penalty? No. Google says there may be nothing fundamentally wrong with your content. Core updates change how Google assesses content across the web. Wait at least a week after the update finishes, then compare before and after in Search Console.

My traffic dropped but Search Console shows no issues. What now? Check your tracking first. If Search Console clicks are steady, the drop may be in your analytics setup, not in Google. If clicks did fall, work through indexing, recent site changes, seasonality and update dates, in that order.

Is my site banned from Google? A site: search (for example site:example.com) is only a rough check. Google says it doesn't necessarily return every indexed URL. If your pages show up, you're not removed. If nothing shows, check the Manual Actions report and the Security issues report first, then the Page indexing report, and inspect your home page with the URL Inspection tool.

Is a security issue the same as a penalty? No. It shows up in a separate report, the Security issues report. Google can show warnings to people before they reach a hacked or harmful site, and that can cut Search traffic. It still needs fixing, and the review is requested from that report.