Restore / Research / Penalty Location Penalty Location Where can I find the Google penalty? Search Console Manual Actions report first, then the verification surfaces.
The Search Console Manual Actions report names manual penalties with a category line. The Security Issues report flags hacked sites and malware (distinct surface). The message archive carries historical actions. The URL Inspection tool and the site: operator verify indexation. The diagnostic always starts at the report.
The Search Console Manual Actions report
The Manual Actions report is the authoritative surface for current manual penalties. In Search Console, navigate to Security & Manual Actions → Manual Actions. If a manual action has been issued against the property, a notice appears naming the category line (unnatural-links-to-site, thin-content-with-little-added-value, scaled-content-abuse, site-reputation-abuse, cloaking, sneaky-redirects, etc.). If no action has been issued, the report reads "No issues detected."
The report is property-level. A site with multiple Search Console properties (the domain property plus subdomain or subfolder properties) requires reading each property's report. An action against a subfolder property does not necessarily surface on the parent domain property if the property scopes do not overlap. Verify the surface that covers the affected URLs.
The notice names the category and describes the affected surface. The remediation path is per-category. Removal of the manual action runs the per-category remediation; manual action remediation checklist covers the steps per category.
The Security Issues report, distinct surface
The Security Issues report sits adjacent to the Manual Actions report in Search Console under the same Security & Manual Actions menu. It flags hacked-site patterns and malware. The two reports look similar in the interface and the distinction matters: the Security Issues report flags compromise (the site has been hacked, the site is serving malware); the Manual Actions report flags intentional manipulation by the operator.
The remediation paths do not overlap. Security Issues route to a separate incident-response partner. Manual actions route to the per-category remediation workflow. Mixing the two in the diagnostic costs time. Search Console security issues vs manual action covers the distinction.
The message archive and the verification surfaces
Message archive. Search Console maintains a message archive that captures historical actions and their resolution status. Prior manual actions, prior security issues, prior policy notifications surface there even after the current state shows clean. The archive is useful when an operator inherits a site and needs to read the historical enforcement context before scoping the current remediation.
URL Inspection tool. Per-URL read of the indexation state. The tool reports whether Google has indexed the URL and names the reason for non-indexation when the URL is not indexed. The reasons it surfaces include robots.txt block, noindex directive, canonical pointing elsewhere, crawl error with the HTTP code, discovered but not indexed, crawled but not indexed. Useful for verifying whether a specific URL has been removed from the index by manual action versus by technical block versus by quality-signal suppression.
The site: operator. The site:yourdomain.com query returns the indexed surface. The site:yourdomain.com/specific-path/ variant checks indexation per URL or per subdirectory. Significant divergence between the result count and the historical surface signals removal or indexation block.
The parent surface on indexation enforcement is Google deindex. The decision tree for a site that has dropped is at why did my website disappear from Google rank. The diagnostic in front of every remediation route runs at SEO Penalty Removal.
What operators ask when looking for the penalty surface in Search Console.
- 01.
Where do I find a manual action in Search Console?
The Manual Actions report. In Search Console, navigate to Security & Manual Actions → Manual Actions. A notice appears with the category line if an action has been issued. The report is property-level; check both the domain property and any subdomain or subfolder property the site uses.
- 02.
What is the difference between the Manual Actions report and the Security Issues report?
The Security Issues report flags hacked sites and malware. The Manual Actions report flags intentional manipulation. The remediation paths do not overlap. Search Console security issues vs manual action covers the distinction in full.
- 03.
How do I check historical actions?
The Search Console message archive. Prior actions and their resolution status surface there, even after a current action has been lifted. The archive is useful when an operator inherits a site and needs to read the historical enforcement context before scoping remediation.
- 04.
What if the report says 'No issues detected' but my traffic dropped?
The cause is not a manual action. The next diagnostic surface is algorithmic correlation: line up the traffic-loss date against the named-update calendar. The broader decision tree is at why did my website disappear from Google rank.
- 05.
How do I verify that a page is deindexed?
Two surfaces. The site:yourdomain.com/specific-path/ operator returns the indexed surface; an empty result confirms removal from the index. The URL Inspection tool in Search Console reports the indexation state per URL and names the reason for non-indexation when applicable.
If you are looking for the penalty surface in Search Console and you need the Manual-Actions versus Security-Issues distinction made before remediation routing, book the diagnostic.
We pull the Search Console reports across every property scope, read the message archive for historical actions, run per-URL inspections, and separate manual penalties from algorithmic demotions from technical blocks before any remediation work begins.