Skip to content
MrKeyword
Technical SEO

Security issues report in Google Search Console: what it means and how to fix it

The Security issues report lists pages Google found to be hacked or harmful to visitors, and Google may show a 'This site may be hacked' label or a browser warning until you clean the site and request a review.

A checklist-style dashboard of page and indexing checks
The short version
  • The Security issues report lists pages Google found to be hacked or harmful to visitors. Google may show a 'This site may be hacked' label or a browser warning until you clean the site and request a review.
  • The report groups issues into hacked content, malware and unwanted software, social engineering or deceptive pages, and uncommon downloads. Each type has its own first fix.
  • Clean the site before you request a review. Remove injected files and spam URLs, update the CMS and plugins, change every password, and check robots.txt and the sitemap for URLs you did not add.
  • A review is a request for Google to recheck the site, not a promise that warnings disappear immediately. Google says reviews can take some time, and the warning can stay until the recheck finishes.
  • Security issues are not the same as manual actions. A security issue is about harm to visitors; a manual action is about a spam policy violation.

What does the Security issues report show?

The Security issues report lists pages on your site that Google found to be hacked or harmful to visitors. It is Google's warning that something on the site can infect a visitor's device, steal information or trick people, not a comment on your content quality or rankings.

You find it under Security & Manual actions in Search Console. Google's Security issues report help explains what the report covers and how to request a review. While an issue is open, Google may show a This site may be hacked label in search results or a browser warning before a visitor can open the page.

The report names the issue type, shows example URLs and gives the date Google last checked them. Open each issue to see the affected pages and the guidance for that type. The report is a starting point: it tells you what Google found, not how the code got there.

Which security issue types are there?

Google groups security issues into four families, and the first fix depends on which one you have. Read the issue name in the report before you start deleting files.

Security issue types and the first fix

Issue typeWhat it meansFirst fix
Hacked: code injectionMalicious code was added to your site's files or templates, often to redirect visitors or serve spam.Find and remove the injected code, then close the entry point and change passwords.
Hacked: content injectionSpam pages, links or text were added to your existing pages without your knowledge.Remove the injected content and check the database and CMS for unauthorised changes.
Hacked: URL injectionNew URLs were created on your site, such as spam pages or redirects, that you did not publish.Remove the pages, return 404 or 410 for them, and check the sitemap and internal links.
Malware and unwanted softwareThe site serves or links to software that can harm visitors or their devices.Find the malicious file or link, remove it, and scan the server and CMS.
Social engineering / deceptive pagesPages trick visitors into sharing information, paying or downloading something, often through fake forms or alerts.Remove the deceptive pages or forms and review who can publish on the site.
Uncommon downloadsThe site offers downloads that Google considers unusual or potentially harmful.Check what the file is, remove it if it is not yours, and explain legitimate downloads clearly.
Issue names follow Google's Security issues report. Checked November 2026.

Google's Search Central security documentation explains how Google detects hacked sites and what each warning means. If you are unsure which type you have, start with the issue name in the report rather than guessing from a browser warning.

How do I clean a hacked site?

Take a backup, find what changed, remove it, close the way in, then check that nothing was left behind. Work in that order so you can restore the site if a clean-up step goes wrong.

  1. Take a backup first

    Download a full backup of the files and the database before you delete or edit anything. Keep a copy offline. If the clean-up removes something you need, the backup is the way back.

  2. Find injected files and spam URLs

    Search Google for site:yourdomain.com and look for pages you did not publish. Use URL Inspection in Search Console to see how Google sees a suspicious URL. Compare the live files with a known-good copy or the backup, and look for recently changed files, unfamiliar scripts and new admin users.

  3. Update the CMS, theme and plugins

    Install the current version of your CMS, theme and every plugin or module. Old versions are a common way in. Remove anything you do not use instead of leaving it disabled.

  4. Change all passwords and keys

    Change the passwords for the CMS admin, hosting, database, FTP or SSH, and any connected service. Replace API keys and salts where the platform supports it. Remove accounts and admin users you do not recognise.

  5. Remove spam pages and return 404 or 410

    Delete the injected pages and files. If a URL no longer exists, let it return a real 404 or 410 rather than a soft 404 or a redirect to an unrelated page. Remove the URLs from the sitemap and from internal links.

  6. Check robots.txt and the sitemap

    Look for rules or URLs you did not add. Attackers sometimes add spam URLs to the XML sitemap or change robots.txt to hide their pages from you. Restore both files to the version you intend to publish.

After the clean-up, scan the site again and ask your host to check the server for leftover backdoors. A second pass catches files that the first scan missed.

How do I request a review?

Fix the issue first, then open the Security issues report and choose the request review option for the issue. Google rechecks the site and decides whether the warning can be removed.

In the report, open the issue, confirm that the affected URLs are clean, and follow the review request in the interface. Google's Security issues report help describes the request and what to include. Be specific about what you removed and what you changed to stop it happening again.

Do not request a review while spam pages or malicious files are still live. Google will find them again, and the warning will stay. If the report lists several issue types, clean and request a review for each one.

How long does a review take?

Google says a review can take some time, and the warning can stay until the recheck finishes. There is no guaranteed same-day removal, so plan for the warning to remain while Google verifies the clean-up.

Use the time to check the site again: rescan the files, confirm the spam URLs return 404 or 410, and make sure the sitemap and robots.txt are clean. If the review comes back and the issue is still there, read the report again and fix what Google found before requesting another review.

Security issues vs manual actions

A security issue is about harm to visitors; a manual action is about a spam policy violation. They live in the same area of Search Console but they are different reports with different fixes.

A security issue means Google found hacked content, malware or a deceptive page. A manual action means a person at Google found that the site breaks a spam policy, such as paid links or thin content, and may demote or remove part of the site. Our guide to manual actions in Search Console covers the types and the reconsideration request. Check both reports when traffic drops suddenly, because either one can explain it.

What about Bing?

Bing Webmaster Tools has its own malware and security notices, and the clean-up is the same. Fix the site first, then check the notice in Bing Webmaster Tools and request a review there if Bing offers one.

Our Bing Webmaster Tools guide covers setup, the reports and how to submit changed URLs. Keep the Google and Bing checks separate: each search engine decides when to remove its own warning.

Questions and answers

Security issues report questions

What does 'This site may be hacked' mean?

It is a Google warning that the site may contain hacked content or be harmful to visitors. Open the Security issues report in Search Console to see the issue type and the affected URLs, then clean the site and request a review.

Will Google remove the warning as soon as I clean the site?

No. Cleaning the site is the first step; Google then has to recheck it. Request a review in the Security issues report and allow time for the recheck before expecting the warning to disappear.

Do I need to delete hacked pages or can I redirect them?

Delete the injected pages and let the old URLs return a real 404 or 410. A redirect to an unrelated page can look like a soft 404 and does not remove the spam content from the site.

Is a security issue the same as a manual action?

No. A security issue is about hacked content, malware or deceptive pages that can harm visitors. A manual action is a spam policy violation found by a person at Google. They are separate reports with separate fixes.

About this article

Written by the MrKeyword team, who build an SEO workspace on first-party Search Console and Bing data. Outside facts link to their original source below. We update this page when the product or the sources change.

Sources

  1. Security issues report — Search Console Help on the Security issues report, issue types and requesting a review
  2. Security issues — Google Search Central on hacked sites, malware and security warnings
Keep reading

More on technical SEO, plus the feature and free tool for the same job. All technical SEO guides →

Clean the site, then ask Google to recheck it.

Check any URL for the status, headers, robots.txt and canonical signals behind a security warning with the free indexability checker. Free plan for one website, no card; paid plans from $10 a month.