Analytics and Tracking

Security Issues Report

Also called Security issues, hacked site notification

Where Search Console warns that your site has been hacked, is serving malware or is hosting deceptive pages.

Quick facts: Security Issues Report

Category
Analytics and Tracking
Also called
Security issues, hacked site notification
Level
Intermediate
Affects
Search warnings, browser interstitials, visitor trust
Where to see it
Google Search Console (Security and Manual Actions), Safe Browsing site status
In this article4
  1. How the security issues report works
  2. Why the security issues report matters
  3. Where security clean-ups go wrong
  4. How to act on it

How the security issues report works

Google checks the pages it crawls for signs of compromise, and when it finds them it records the finding here, alongside manual actions. The categories are broad but distinct: hacked content, where someone has injected pages, links or code into a site they do not own; malware and unwanted software, where visitors are offered a harmful download; and social engineering, where a page or an advert on it tries to trick people into handing over passwords or personal details.

Each entry names the category and lists example URLs where the problem was detected. Those examples are a sample, not an inventory, which is an important distinction when you start cleaning.

The consequences are immediate and public. Listings can be labelled as unsafe, Chrome and other browsers can put a full-page warning in front of the site, and affected pages can be dropped from results. After you clean up, you request a review from inside the report and the warnings lift once Google confirms the site is safe.

Why the security issues report matters

Because a compromise is usually invisible to the owner. Injected pages are frequently cloaked so that the site looks normal to a logged-in administrator on a familiar device, while search engines and new visitors are shown pharmaceutical spam, gambling pages or a redirect somewhere else entirely. The first symptom the owner notices is often a customer asking why their browser blocked the site.

The cost is not only rankings. A browser warning stops paid traffic dead as well as organic, it damages trust with anyone who sees it, and it can affect email sent from the same domain. For small businesses running WordPress on shared hosting with old plugins — an extremely common setup in Nepal — this is a realistic risk rather than a theoretical one.

Where security clean-ups go wrong

The usual failure is treating the listed URLs as the whole problem. Deleting the visible spam pages and requesting a review leaves the way in untouched, so the site is reinfected within days and the second warning is harder to shift than the first.

The second failure is skipping credentials. Attackers commonly leave behind an extra administrator account, a modified core file, a scheduled task or a backdoor in the theme. If passwords, hosting logins, database credentials and file transfer keys are not all changed, the same person simply returns.

How to act on it

Take the site offline or into maintenance mode if the compromise is active, then work backwards from the entry point: outdated plugins and themes, weak or reused passwords, an unpatched server, or a nulled theme installed to save money. Restore from a backup taken before the infection where one exists, and update everything before putting the site back.

Then remove every leftover account and file, change all credentials, run a full malware scan, and only then request the review. Afterwards, keep watching: alerts turned on in Search Console, updates applied promptly and regular backups are ordinary website maintenance, and they cost far less than a repeat clean-up.

Do and do not

Do

  • Turn on Search Console email alerts
  • Close the entry point before removing the damage
  • Change every password and key afterwards

Do not

  • Request a review straight after deleting pages
  • Run nulled themes or abandoned plugins
  • Assume the listed URLs are the whole problem

Questions people ask about this

How will I find out that my site has been hacked?

Usually not by looking at it. Injected content is often hidden from logged-in administrators and shown only to search engines or first-time visitors. The reliable signals are an entry in this report, a browser warning that a customer mentions, a sudden appearance of unrelated pages in search results, or unexplained files and administrator accounts on the server.

I deleted the pages Google listed. Why is the warning still there?

Two reasons. The listed URLs are a sample rather than a full inventory, so other injected content probably remains, and the warning only lifts after you request a review and Google verifies the site. More importantly, deleting pages does not close the hole they came through, so a site cleaned that way is commonly reinfected before the review completes.

Will a hack damage my rankings permanently?

Not permanently, but recovery is rarely instant. Affected pages can be dropped or demoted while the problem is live, and warnings deter the visitors who do still see your listing. Once the site is genuinely clean and the review has passed, positions usually return. The lasting damage is to trust, especially if customers saw a browser warning.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.