New researchTechnical SEO & AI Search · 2027Explore the framework

Google Search Console Security Issues: Audit and Fix

How to investigate the Search Console Security Issues report, find affected pages, fix the underlying problem and request a review safely.

Part of the Technical SEO Audit series. For the full picture, start with Technical SEO audit: the complete guide and checklist.

The Google Search Console Security Issues report is a warning system for harmful site behavior, not a routine list of broken SEO tags. Google uses it to report signs of hacked content, malware, unwanted software and social engineering. Affected pages may show warnings in Search or a browser interstitial, so the first priority is visitor safety, then search recovery. Google’s report guide explains the issue types and review process.

If you are working through a broader technical SEO audit, check Security Issues alongside indexing and crawl data. A clean crawl does not prove a site is free of malicious code, and a security warning is not something to dismiss as an ordinary ranking fluctuation.

What does the Search Console Security Issues report show?

The report identifies the type of suspected problem, when Google first detected it and, where available, sample affected URLs. Google groups issues into hacked content, malware or unwanted software, and social engineering such as deceptive pages. The examples are not a complete URL inventory; Google says an issue can exist even when it cannot provide a sample URL.

Signal What it tells you What it does not tell you
Issue type Google’s classification of the harmful behavior The exact vulnerable file or account
Sample URLs Places to begin investigation Every affected URL
First detected date When Google observed the issue When the compromise began
Review status Whether Google has processed your request That the underlying weakness was fixed

Open the report in the correct Search Console property. If a warning appears, record its exact wording and examples before making changes. This preserves evidence for the security team and gives you a baseline for verification.

How is this different from a manual action?

A Security Issues finding concerns behavior that could harm a user or their device. A Manual Actions finding concerns a violation of Google’s search spam policies; see manual actions and the Search Essentials audit. Google explains the distinction in its Manual Actions report documentation. A hacked site can create both kinds of problems, but the two reports have separate findings and review actions.

Do not submit a manual-action reconsideration request to clear a security warning. Follow the issue in the Security Issues report and request its review there. If both reports show findings, make a work item for each one and verify both outcomes.

How do you investigate without making the problem worse?

Start with the issue description, the affected URL samples and the time window. Then involve the site owner or security team before browsing suspicious pages. Google’s security issue guidance warns that opening infected pages directly can be unsafe; URL Inspection or controlled HTTP fetches may be safer for diagnosis.

  1. Preserve evidence. Record the Search Console issue, example URLs, timestamps, unusual redirects and recent deployments. Keep relevant server and CDN logs.
  2. Find the entry point. Check changed templates, plugins, third-party scripts, uploads, user accounts, scheduled tasks and server configuration. A deleted spam page can reappear if its generator remains.
  3. Find the full scope. Inspect related paths and templates, not only the sample URLs. Compare clean backups with current files and look for unexpected pages, scripts, links or redirects.
  4. Contain and repair. Let the security owner remove malicious code, close the vulnerability, rotate affected credentials and update compromised software.
  5. Test safely. Confirm the intended pages and files are clean, redirects no longer lead elsewhere and legitimate content still works for users and crawlers.

An SEO crawler helps with site-wide URL evidence, such as unexpected paths, changed titles, response codes or redirects. It does not replace malware analysis. If the site is actively compromised, use a controlled environment and coordinate with the security team before crawling it. Our broken links guide is useful after cleanup to find URLs left behind by removed content, but it is not a security scanner.

How do you verify the cleanup and request a review?

Before requesting a review, test the issue across the entire site. Google says fixing only the listed examples is not enough. Recheck the affected templates, newly created pages, third-party resources and the original entry point. Confirm that the site is still crawlable and that a security fix did not accidentally leave important pages blocked or noindex.

Then select Request Review in the Security Issues report. State the detected issue, the root cause you found, the remediation you made and the evidence that it is resolved. Google says reviews may take days or weeks and asks owners not to resubmit while a request is pending. See its review guidance for the current workflow.

Continue monitoring after the warning clears. Watch server logs, unexpected new URLs and changes to scripts or redirects. The outcome you want is not only a green report, but a closed vulnerability and a process that catches recurrence.

Security Issues audit checklist

  • Check the correct Search Console property and record every issue type.
  • Treat sample URLs as starting points, not the full affected set.
  • Preserve logs and deployment history before cleanup.
  • Identify and close the root cause with the security owner.
  • Test affected templates, redirects and legitimate crawl access.
  • Request a review only after all issues are fixed and verified.
  • Monitor for reappearing pages or code after the review.

Frequently asked questions

What does a Security Issues warning in Search Console mean?

It means Google detected signs of hacking or behavior that could harm visitors, such as malware or deceptive content. Open the report for the issue type and examples, then investigate the whole site rather than only the listed URLs.

Is a Security Issues warning the same as a manual action?

No. The Security Issues report concerns hacked or harmful behavior, while the Manual Actions report concerns violations of Google's search spam policies. Check and resolve both reports independently if both have findings.

Why does the report show only a few affected URLs?

Google says the URLs are samples, not a complete list. Some issues have no example URL at all, so use the issue description, server evidence and a wider site investigation to find the full scope.

When should I request a security review?

Request a review from the Security Issues report after fixing every listed issue across the site and testing the result. Explain what happened, what you changed and how you verified the cleanup.

· Founder, Crawlens

Dien builds Crawlens, a desktop crawler for technical SEO audits, and writes about the checks it runs: crawling, indexing, rendering and Search Console data.

Audit your own site with Crawlens

Crawl, run 70 checks, and see them next to Search Console and Core Web Vitals data.

Download free for Windows