You search for your business on Google and, under the name, it says: "This site may be hacked". Your customers see it before they visit, and many no longer do. The good news is that the warning can be removed. The bad news is that it does not go away on its own: according to Google's help, it is not removed until the site owner takes action and requests a review. This is the route, in order, and the part of WordPress malware removal you should not improvise.
What the warning means (and which one it is not)
Google shows it when it believes someone has modified pages on your site or added new spam pages: pharmacy text, casinos, replicas, sometimes in Japanese or Chinese, or redirects to other sites. It is the most common warning on WordPress sites with a vulnerable plugin.
It is not the same as Chrome's red screen ("Deceptive site ahead" or "This site contains malware"). That one comes from Google Safe Browsing and is more serious: it blocks the visit. The process to remove it is similar and starts in the same place, Search Console.
If you have not seen the warning but suspect something (odd redirects, users you did not create, your host warning about a spike in resource use), bear in mind that some of those signs can also come from a cache or a badly configured plugin. The Search Console report in step 1 is the quickest way to find out.
Step 1: go to Search Console
If your site is not in Google Search Console, add and verify it (ideally as a domain property, which covers every version). Go to Security & Manual Actions → Security issues. There Google tells you what it found, what type it is (hacked content, malware, social engineering) and shows you sample URLs.
Write those URLs down. They are your lead: they tell you whether they are your own pages modified or new pages you do not recognise.
Also check Indexing → Pages and search Google for site:yourdomain.com: if hundreds of pages you never created show up, it is injected spam.
Step 2: backup, host and clean-up
Before touching anything:
- Take a copy of the site as it is, files and database, even if it is infected, and store it off the server. If something goes wrong you can go back, and it is the best lead on how they got in. Do not delete files blindly before you have it.
- Tell your host. Ask what they see in their logs, whether they can isolate the site while you clean it and how far back their backups go. Many have scanning tools you cannot see.
Then clean. Google asks for the problem to be fixed on every page, not just the sample ones. In WordPress, malware is almost never in one place:
- Files: modified plugins or themes, stray PHP files in
wp-content/uploads, changes to.htaccessorwp-config.php. To find out what has changed, compare core and plugins with the originals: with WP-CLI,wp core verify-checksumsandwp plugin verify-checksums --all, or with a security plugin. It helps, but it is no guarantee: premium plugins cannot be checked this way, and malware also hides in files that look normal. - Database: spam posts, scripts inserted into content or theme options, administrator users that are not yours.
- Scheduled tasks that recreate whatever you delete.
If you clean only the files and a copy remains in the database, it comes back. We explain this in detail in why malware comes back after cleaning.
Restore a backup or clean by hand?
Restoring is faster, but it only works if three conditions are met:
- The backup is older than the infection and you know for sure when it started. File dates are not enough: some malware fakes them.
- You restore files and database, not just files.
- You accept losing whatever has changed since that date. In a shop, that means orders and customers.
If you do not know when the infection started, or you cannot lose recent data, you will have to clean by hand. Either way, the next step is the same.
Step 3: close the door they came in through
Google's help is insistent on this: if you do not fix the vulnerability, the site will probably be reinfected. In WordPress, the usual culprits are:
- An outdated plugin or theme with a known flaw. Update it or remove it, and get rid of those you do not use. In 2026 several have been attacked at scale; we review them in WordPress vulnerabilities exploited in 2026. Check the server's PHP version too: an old or unpatched one is another way in (what to do about the PHP vulnerability).
- Stolen passwords: from a trusted computer, change those of every administrator, FTP or SFTP, hosting, database and the linked email account, and the keys in
wp-config.php(the salts), to close any open sessions. - Extra users: delete any administrators you do not recognise, but first note their names and when they were created. It is another clue to when the attacker got in.
Step 4: check it is really clean
- Open the sample URLs from Search Console. If they were spam pages, they should now return a 404 or 410 error.
- Use URL Inspection in Search Console on those addresses to see the page as Google sees it. Some attacks only show the spam to Google and show you the normal site.
- Search
site:yourdomain.comagain with words from the spam (for example,site:yourdomain.com casino). - If spam URLs were indexed, ask for them to be removed with the Removals tool to speed things up. It does not replace the clean-up.
Step 5: request the review
When everything is clean, click Request review in Security issues. Google asks you to explain what the problem was, what you did to fix it and what result you checked. Be specific, for example:
The site had a vulnerable plugin (name and version) through which spam pages were created under /xyz/. We have removed those pages and the malicious files in uploads, updated every plugin, deleted two unknown administrators and changed all passwords and keys. The sample URLs now return 404.
According to Google, security reviews take from a few days to a few weeks, and you get an email when it is received and when it is done.
Mistakes that make the wait longer
- Requesting the review before you finish. If Google finds the site is still infected, it rejects the request, and its help warns that asking too early can make later reviews take longer. Do not submit another request while one is pending either.
- Restoring an old backup without closing the door. You go back to a version with the same vulnerable plugin and they get in again.
- Deleting only the spam pages and leaving the code that creates them.
- Not looking at the database. That is where spam hides most often in WordPress, and where people look least.
- Changing only the WordPress password. If the attacker has access to the server, that is not enough.
If you run a shop or store customer data
The Google warning is what people see, but in a shop it is not the worst part. If the attacker may have injected code into the checkout, talk to your payment provider. And if there are signs that personal data (names, emails, addresses) has been seen, Article 33 of the GDPR gives you 72 hours to notify the breach to your data protection authority (the AEPD in Spain) when it poses a risk to people. Check with your adviser early, not at the end of the clean-up.
When to ask for help
Do it straight away if you do not know when the site was compromised, if it is a shop, if you have no reliable backups or if the infection has already come back once. And be wary of anyone who promises an instant clean-up or zero risk: the serious approach is to find the cause, clean up, close the way in and give you a written record of what was done.
What we don't know
Google gives no fixed timeframe and does not explain in detail how it decides when to re-review. Nor does it guarantee that rankings recover as soon as the warning is lifted: if a lot of spam was indexed, it can take time to clear from the results.
What now
If the warning has just appeared: Search Console, sample URLs, a copy of the site and a message to your host, today. If you would rather not do it yourself, with WordPress malware removal we clean files and database, close the way in and write the review request. And to keep it from happening again, the most effective protection is the least glamorous: up-to-date software, backups off the server and someone keeping an eye on it, which is what WordPress maintenance is for.
Reviewed on 7 November 2026 against Google Search Console documentation.