SEO & AI search · Guide
How to Check If Your WordPress Site Has a Google Penalty
Short answer
Open Google Search Console, go to Security and Manual Actions, then select Manual actions. A green check mark means your site has no manual action, while a listed action names the violation, the affected pages, and the fix. Fix every affected page, then select Request Review and describe what you changed.
Key takeaways
- A Google penalty is usually a manual action, and the Manual Actions report in Search Console is the only place that confirms one.
- A green check mark in the Manual Actions report means your site has no manual action as of November 2026.
- Fix every affected page before you ask for a review, because a partial fix earns no partial return to search results.
- Most reconsideration reviews take several days or weeks, and link-related requests can take longer.
- A traffic drop with no manual action is not a penalty, so check core update timing and your site before you appeal.
What does a Google penalty mean for a WordPress site?
A Google penalty usually means a manual action: a human reviewer at Google found pages on your site that break Google's spam policies.
Google's Search Console Help says most manual actions address attempts to manipulate the search index. Affected pages can rank lower or disappear from results, and searchers see no warning that this happened.
A penalty is not the same as an algorithm change. Google makes core updates several times a year, and its core updates page says these changes are broad and do not target specific sites or single pages.
That difference decides what you can do next. A reconsideration request only applies to a manual action, so the report tells you which problem you actually have.
Common triggers include link spam, hidden text, cloaking, and large volumes of low-value pages. Google's spam policies page lists these practices and says sites that break them may rank lower or not appear at all.
Pages made in bulk with generative AI tools can also fall under the scaled content abuse policy when they add little value for readers. If your site publishes AI-written posts, our guide on whether Google penalizes AI content explains where that line sits.
How do you check the Manual Actions report?
Open Google Search Console, pick your property, then go to Security and Manual Actions and select Manual actions.
You need a Search Console account with access to the site's property. If you have not verified the site yet, verify it first, because the report only shows data for properties you can access.
- Sign in to Search Console and select the property for your site.
- In the left menu, open “Security & Manual Actions”.
- Select “Manual actions”.
- Read the count at the top of the report.
If your site has no manual actions, Google's Search Console Help says you will see a green check mark and a message saying so. That check takes less than a minute once you are signed in.
If an action is listed, expand it to see the type, a short description, and the pattern of affected pages. Google gives the example pattern https://example.com/real-estate/*, which means some or all pages under that folder are affected.
Google also sends a notice to the Search Console message center, so check there if you missed the first alert.
If you recently bought the site, fix the listed issues first, then say in your reconsideration request that you are the new owner. Google's help page gives this exact advice for new owners.
Google also publishes a short training video that walks through the report. Watch the Manual Actions report video if you want to see each screen before you open it.
What do the different manual actions mean?
Each manual action names one spam policy violation and says whether it affects the whole site or only some pages.
Follow the “Learn more” link on the action itself for the exact fix. The table below covers the violations WordPress owners see most, as described on Google's spam policies page.
| Spam policy | What Google says it means | Where it shows up on WordPress |
|---|---|---|
| Link spam | Links created mainly to manipulate rankings | Paid links, link schemes, and comment spam with optimized anchor text |
| Cloaking | Different content for users and search engines | Hacked pages and plugins that serve one page to Googlebot |
| Sneaky redirects | Visitors sent to a different URL than requested | Mobile-only redirects to spam domains |
| Hidden text and links | Content placed to manipulate search, not for readers | White text on white backgrounds and links hidden in single characters |
| Keyword stuffing | Pages filled with keywords to manipulate rankings | Blocks of city names and repeated phrases with no added value |
| Scaled content abuse | Many pages made mainly to manipulate rankings | Bulk-generated posts with little original value |
| Hacked content | Content placed on a site without permission | Injected spam pages, hidden links, and phishing pages |
| Site reputation policy | Third-party pages hosted mainly to borrow ranking signals | Sponsored sections run by outside firms on a trusted site |
If the action mentions markup, our guide to structured data and rankings explains how markup should describe the page.
An action can list a pattern rather than every URL, so treat the pattern as the full scope. Google's help page says not all pages matching a pattern are necessarily affected, but you must still fix the pattern.
How do you tell a penalty from a traffic drop?
A traffic drop alone does not prove a penalty, so check the Manual Actions report first and the timing of Google updates second.
If the report shows no action, the drop is not a manual penalty. Google's core updates page says core updates are broad changes that do not target specific sites, and a drop that lines up with an update is usually an algorithm change.
Google advises waiting at least a full week after a core update finishes before you analyze the drop in Search Console. After that week, compare the new week with the week before the update started, and use the Search Status Dashboard for the start and end dates.
Google gives two examples to judge size: a small drop from position 2 to 4 needs no drastic action, while a large drop from position 4 to 29 deserves a deeper assessment. Open the Performance report to see whether the drop hits the whole site or only some pages and queries.
Slow pages can also cut traffic, so rule out page speed problems before you blame Google. A single slow template can drag down every post that uses it.
A host move can cut traffic too if redirects break. Our guide to changing hosting without losing SEO covers the checks to run after a move.
If you improved content after a drop, expect a wait. Google says some changes take effect in a few days, but it could take several months for its systems to confirm the site now produces helpful content in the long term.
How do you check if pages have dropped out of search results?
Use the URL Inspection tool in Search Console to see whether Google can find and index a single page.
Enter the page URL, and the tool shows whether Google has indexed it and whether it can reach it. A missing page with no manual action points to a crawl or indexing problem rather than a penalty.
Check the affected pages one by one instead of judging from one search. A page can rank lower without being removed, and a manual action can affect only part of a site.
Also confirm the page is not blocked by a noindex tag or a robots.txt rule. Google's help page says fixed pages must stay reachable for a review, with no login, paywall, robots.txt block, or noindex tag.
If the tool says the page is indexed but it still ranks far below its old spot, the problem is ranking, not removal. That points back to content quality and the core update checks in the last section.
How do you fix a manual action and request a review?
Fix the problem on every affected page, then select Request Review in the Manual Actions report.
Set aside enough time to finish the whole job, because a partial fix earns nothing. Google's Search Console Help says fixing only some pages will not earn you a partial return to search results.
- Expand the action and follow its “Learn more” link for the exact fix.
- Fix the issue on all affected pages, not just the example URLs shown.
- Make sure Google can reach the fixed pages, with no login, paywall, robots.txt block, or noindex tag.
- Test a fixed page with the URL Inspection tool.
- Select “Request Review” and describe your fixes.
A good request does 3 things, according to Google's help page: it explains the exact quality issue, describes the steps you took, and documents the outcome of your efforts. Write it like a short report, with numbers such as how many pages you fixed.
For thin pages, rewrite them with useful detail or remove them. Our guide on how many words a blog post should be for SEO can help you judge whether a post has enough depth.
Do not resubmit while a request is still pending. Google says you will get a review confirmation message when you send a request, and you should wait for a final decision before sending another.
After the review, open the Manual Actions report again. If the action is gone, the penalty is lifted, and you will have the decision email to confirm it.
How long does a reconsideration review take?
Most reconsideration reviews take several days or weeks, and link-related requests can take longer.
Google's Search Console Help says you will get an email when your request is received and another when the review is complete. Plan for weeks, not hours, and do not send a second request while the first is pending.
Hacked sites follow a different clock. Web.dev says spam-hack reviews can take up to several weeks, malware reviews a few days, and phishing reviews about a day, and warnings leave browsers and search results within 72 hours once Google finds the site clean.
There is no date you can count on, so keep the site clean while you wait. Check the Message Center for the result instead of guessing from traffic.
How do you check for hacked content and security issues?
Open the Security Issues report in Search Console, which is separate from the Manual Actions report.
Google's Search Console Help explains the difference: the Manual Actions report lists attempts to manipulate the search index, while the Security Issues report lists signs the site was hacked or could harm visitors. Hacked pages can carry a warning label in search results or a full browser warning page.
WordPress.org lists clear signs of a hack, including a Google blacklist warning, a disabled site, malware flags, new users you did not create, and strange behavior in the browser. Its hacked-site FAQ walks through documenting the problem, scanning the site, and changing every password.
After cleaning, WordPress.org says to change the passwords again, since the first change may have happened before the site was fully clean. It also says to update the site to the latest software once it is clean.
If the Security Issues report lists a problem, fix it and select Request Review there, not in the Manual Actions report. Web.dev says to confirm the site is verified, cleaned, fixed, and back online before you ask for a review.
What mistakes should you avoid?
Most failed recoveries come from rushing the fix or filing the request too early.
- Do not file a reconsideration request before every affected page is fixed.
- Do not fix only the example URLs while the rest of the pattern stays live.
- Do not resubmit a request while the first one is still pending.
- Do not treat every traffic drop as a penalty without opening the Manual Actions report.
- Do not block fixed pages with a noindex tag or a robots.txt rule.
- Do not ignore the Security Issues report when the real problem is a hack.
Frequently asked questions
Can a WordPress site be penalized without any notice from Google?
No. Google notifies you in the Manual Actions report and in the Search Console message center when it applies a manual action. If neither place shows an action, you do not have a manual action, even if traffic fell. A drop with no notice usually comes from an algorithm change or a technical problem on the site.
How do I know if my traffic drop is a Google penalty?
Open the Manual Actions report first. A listed action means a penalty, while a green check mark means the drop has another cause. Compare the drop with core update dates, check your top pages and queries in the Performance report, and rule out site changes such as a host move or broken redirects.
Does a manual action affect my whole site or just some pages?
It can be either. Expand the action in the report to see the pattern of affected pages, which may cover the whole site or only a folder such as a single directory. Fix every page that matches the pattern, not just the examples Google shows.
Can I speed up recovery by filing several reconsideration requests?
No. Google says not to resubmit while a request is still pending, and a second request will not move the first one faster. Most reviews take several days or weeks, and link-related requests can take longer. Use the wait to double-check that every affected page is truly fixed.
What should I do if I bought a site that already has a manual action?
Fix every issue listed in the report first. Then explain in your reconsideration request that you recently acquired the site and that it no longer violates the policies. Google gives this exact advice to new owners in its Manual Actions report help.
Is hacked content the same thing as a manual action?
No. Hacked content shows in the separate Security Issues report, which covers signs the site was hacked or could harm visitors. A manual action covers spam policy violations found by a human reviewer. The two can overlap when a hack adds spam pages, so check both reports.
Sources
- Manual actions report Search Console Help
- Spam policies for Google web search Google Search Central
- Google Search's core updates and your website Google Search Central
- Request a review web.dev
- FAQ My site was hacked WordPress.org
- Manual Actions report in Search Console - Google Search Console Training YouTube
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
