Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Security · Guide

How to Remove a Google Deceptive Site Warning?

Short answer

To remove a Google “Deceptive site” warning, find the cause in the Security Issues report in Search Console, clean every hacked file and deceptive page, close the entry point, then click Request Review in that report. Google re-checks the site and lifts the warning only when it finds the problem gone. Phishing reviews take about a day, malware reviews a few days, and warnings clear within 72 hours after approval.

Key takeaways

  • The red warning comes from Google Safe Browsing when it finds social engineering, malware, or hacked content on a site.
  • The Security Issues report in Search Console names the issue type and lists sample flagged URLs.
  • Sample URLs are only a sample, so you must clean the whole site, not just the listed pages.
  • A review request must explain the exact issue, the steps you took, and the outcome of your work.
  • Phishing reviews take about a day, malware reviews a few days, and hacked-spam reviews can take up to several weeks.
  • Warnings are removed within 72 hours after Google finds the site clean.

What does the “Deceptive site ahead” warning mean?

The warning means Google Safe Browsing found content on your site that can trick visitors into a harmful action.

Google Search Central says that if Google detects social engineering content on a site, Chrome may display a “Deceptive site ahead” warning when visitors view it (Social Engineering (Phishing and Deceptive Sites)). Social engineering is content that tricks a visitor into doing something dangerous, such as revealing confidential information or downloading software.

A social engineering attack is when a web user is tricked into doing something dangerous online. Google lists 3 main forms: phishing, deceptive content, and insufficiently labeled third-party services. Phishing pages pretend to act like a trusted entity, such as a bank or a browser, to collect passwords or other personal details.

Deceptive content also covers fake warnings that claim device software is out of date and push visitors to install unwanted software. The warning is a browser screen, not a WordPress error, so fixing a WordPress setting alone will not clear it.

How do you confirm Google flagged your site?

Check the Security Issues report in Search Console, because that report is Google's record of the problem.

Search Console Help says the Security Issues report shows Google's findings if an evaluation finds that a site was hacked or shows behavior that could harm a visitor or their computer (Security issues report). Affected pages can appear with a warning label in search results or a full warning page in the browser.

Open Search Console, verify that you own the site, then go to Security and Manual Actions, then Security Issues. If the site has no security issues, you will see a green check mark and a matching message. If it has issues, the report shows a count at the top and the issue type below it.

You can also check the site status page in the Google Transparency Report, which shows whether Safe Browsing currently lists the site as unsafe (Safe Browsing site status). Treat Search Console as the record that decides what you fix.

What caused the warning on a WordPress site?

Most WordPress warnings come from a hack, a deceptive page or embed, or a third-party resource that Google treats as deceptive.

Google Search Central says hackers can take control of innocent sites and use them to host or distribute social engineering content. The hacker may change site content or add new pages, often to trick visitors into giving up personal information such as credit card numbers.

The Security Issues report groups problems into 3 categories: hacked content, malware and unwanted software, and social engineering. Hacked content is any content placed on your site without your permission because of a weakness in the site. Malware and unwanted software can be installed by a hacker or by the site owner.

Deceptive content does not need a hack. Google says embedded social engineering content is a policy violation for the host page, even when the host page itself looks normal. That includes deceptive ads, images, or other third-party components, and pages that send visitors to social engineering pages through pop-ups or redirects.

A common WordPress cause is an old or unused plugin or theme with a known weakness.

Nulled plugins are a known risk too: a copy from an unofficial source can carry hidden code. Read our guide on whether nulled WordPress plugins are safe before you install anything from outside the official directory or the vendor.

What do you need before you start cleaning?

You need Search Console access, a full backup, admin access to WordPress and your host, and a note of every password you will reset.

First, confirm that you are a verified owner in Search Console and that no new, suspicious owners have been added. Google lists this as the first step in its social engineering fix guide. An unknown owner is a sign that an attacker still has access.

Second, make a full backup of files and the database before you change anything, and store it away from the live site.

If you already have a clean backup from before the flag, keep it separate and do not overwrite it. Our guide to restore a backup with UpdraftPlus shows the restore path if you need to roll back.

Third, gather access to your hosting control panel, your domain registrar, and your WordPress admin account. You will need them to check users, files, and redirects. Plan for 2 to 4 hours for a small site, and longer if the report lists many sample URLs.

ItemWhy you need itWhere to find it
Search Console accessShows the issue type and sample URLsSecurity and Manual Actions, then Security Issues
Full backupLets you roll back a bad cleanup stepHosting panel or backup plugin
WordPress admin accessLets you check users, plugins, and themesDashboard, then Users and Plugins
Hosting accessLets you check files and redirectsHosting control panel or file manager

How do you clean a hacked WordPress site?

Work through the flagged URLs first, then check the whole site, because the sample list is not complete.

Search Console Help says the sample affected URLs are only a sample of pages affected by the selected issue. A security issue with no example URLs does not mean no pages are affected. Fix the issue throughout your site, since fixing only some pages will not earn a partial return to search results.

Step 1: Read the report and visit the flagged URLs

Open each sample URL from a computer that is not inside the network that serves your website. Google gives this advice because clever hackers can hide their attacks when they think the visitor is the site owner. Note what each page shows, such as a fake login form, a redirect, or spam text.

Step 2: Check users, passwords, and recent changes

Go to Users, then All Users in WordPress and remove any admin account you do not recognize. Reset the passwords for every admin account, your hosting account, and your database user. Change the WordPress security keys and salts in wp-config.php so every logged-in session ends.

Step 3: Replace core, plugin, and theme files

Sucuri advises replacing all the files you can with known good ones, then manually checking custom files that cannot be overwritten (How To Find and Remove Hidden Website Backdoors). Reinstall WordPress core from Dashboard, then Updates. Delete unused plugins and themes instead of leaving them deactivated.

Update every plugin and theme that stays, and remove any plugin that has not been updated in over 6 months.

Sucuri calls a plugin with no update for over 6 months a major security risk in its plugin audit guide (How to Audit and Cleanup WordPress Plugins and Themes). A clean file set matters more than a scan result alone.

Step 4: Search for backdoors and hidden content

A backdoor is malicious code that lets an attacker return after a cleanup. Sucuri says it is critical that all backdoors are closed, or the site will be reinfected quickly. Check recently changed files, unknown files in wp-content/uploads, and code in the active theme that you did not add.

Look in the database too, for spam links, unknown admin users, and injected scripts in posts and options.

If the site is large or the hack keeps returning, get professional help rather than deleting files at random. Our guide on how much it costs to hack-clean a WordPress site sets out what that help usually covers.

Step 5: Check redirects, ads, and third-party code

Check .htaccess and any redirect plugin for rules you did not add. Remove deceptive ads, pop-ups, and third-party embeds that Google flagged. Google notes that ad networks may rotate ads, so refresh a page a few times before you decide it is clean, and check both mobile and desktop views.

How do you remove deceptive content that is not a hack?

Remove the deceptive page, form, or embed itself, then fix the wording or branding that made it look like a trusted entity.

If no hack is involved, the cause is usually a page or a third-party service on your own site. Delete any page that asks visitors to enter personal information for a service you do not run. Remove fake virus warnings, fake update prompts, and download buttons that do not match what they download.

Google says a third-party service must clearly identify itself on every page it operates.

If you run a site for another group, or a payment or donation service runs part of your site, state the relationship in plain words on each page and link to more information about it. A visitor who sees one page in isolation should still know which site they are on and who runs it.

Check every ad slot and embed after you remove the problem. An ad that looks like a media player button or a system message is still a violation for the host page. If an ad network keeps serving deceptive ads, pause that ad slot until the network fixes it.

How do you harden WordPress so it does not come back?

Close the entry point, update everything, and limit who can change code on the site.

The WordPress hardening guide recommends keeping WordPress, plugins, and themes up to date, using strong passwords, and limiting file permissions (Hardening WordPress). Older WordPress versions no longer receive security updates, so an old version gets easier to attack the longer it stays in place.

Set directories to 755 and files to 644, and set wp-config.php to 440 or 400 where your host allows it, as the hardening guide recommends.

Add define( 'DISALLOW_FILE_EDIT', true ); to wp-config.php to turn off the theme and plugin file editors in the dashboard. That step stops anyone with admin access from editing code through WordPress itself.

Turn on two-factor authentication for every admin account, and give each user the lowest role that lets them do their job.

Add a firewall and a security scanner, and set up Wordfence firewall on WordPress if you use Wordfence. Keep a tested backup off the server so a future incident does not leave you with no clean copy.

How do you ask Google to remove the warning?

Request a review in the Security Issues report only after the whole site is clean and back online.

Web.dev lists 4 steps to confirm before you request a review: verified ownership in Search Console, cleaned the site of the hacker's vandalism, corrected the vulnerability, and brought the clean site back online (Request a review). Do not take the site offline for the review, since Google needs to fetch it to check it.

Use Wget or cURL to view your homepage and a flagged URL, and confirm both are clean.

Then open the Security Issues report, select Request Review, and write a short note that covers 3 points. Search Console Help says a good request explains the exact issue, describes the steps you took to fix it, and documents the outcome of your work.

For a phishing flag, you can also report the cleaned page at google.com/safebrowsing/report_error/, which triggers a review of the phishing page. Use the Search Console request as the main route for a WordPress site, and use the Safe Browsing form only as the extra route Google names for phishing.

Keep the note factual and short, with one line per fix. For example, name the infected theme file you replaced, the unknown admin account you removed, the outdated plugin you updated, and the passwords you reset. Do not include passwords, malware dumps, or server logs in the request.

How long does it take for the warning to disappear?

Plan for days to weeks, since the time depends on the issue type.

Web.dev gives these review times, as of November 2026: phishing reviews take about a day, malware reviews take a few days, and reviews for sites hacked with spam can take up to several weeks. The spam figure is longer because those reviews can involve manual investigation or a full reprocess of the hacked pages.

Search Console Help gives a wider range for reconsideration reviews in general: most take several days or weeks. Google sends an email when it receives your request and another email when the review is complete. Do not send a second request while one is pending.

If Google finds that your site is clean, warnings from browsers and search results will be removed within 72 hours. That 72-hour window starts after approval, not after you send the request. If the review fails, the Security Issues report may show more sample URLs to help your next round of cleaning.

How do you check the warning is gone?

Check the Security Issues report first, then the Transparency Report, then a fresh browser on another device.

When the review is approved, the Security Issues report should no longer show the hacked or deceptive issue types or their example URLs. If the report still shows an issue, the review did not pass, and the report is the place to find the next sample URLs.

Next, check the Transparency Report site status page again and confirm it no longer lists the site as unsafe. Then open the site in a different browser on a different device or network, such as a phone on mobile data. A cached warning on one browser does not mean the flag is still live.

Check a few inner pages too, not just the homepage. If search results still show a warning label a few days after approval, wait out the 72-hour window. If the warning returns later, treat it as a new incident and start again at the Security Issues report.

What mistakes should you avoid?

Do not request a review before the site is clean, and do not clean only the pages Google listed.

Google warns that requesting a review when the issue is not fixed can cause a longer turnaround time for the next request, or even get you marked as a repeat offender. A repeat flag can block future review requests for a time, so one careful request beats several rushed ones.

Do not delete the whole site or take it offline to hide the problem. Google needs a live, clean site to re-check. Do not restore a backup from after the hack without checking it first, since that backup may carry the same backdoor.

Do not ignore third-party code after you clean your own files. A single deceptive ad or embed can keep the flag in place, even when every WordPress file is clean. Do not pay a random service that promises instant removal, since no one outside Google can lift a Safe Browsing flag.

Frequently asked questions

Can I remove a Google deceptive site warning without Search Console?

No, you need Search Console to see the exact issue and to request a review. Verify ownership of the site, open the Security Issues report, fix every listed issue, then select Request Review there. A phishing page can also be reported through the Safe Browsing error form, but Search Console stays the main route for a WordPress site.

Why does the warning still show after I cleaned my site?

The warning stays until Google re-checks the site and approves a review request. Cleaning alone does not lift it. Check that the whole site is clean, that no backdoor or deceptive embed remains, then request a review in the Security Issues report and wait for the review email before you check again.

How long does a Google security review take?

It depends on the issue type. Phishing reviews take about a day, malware reviews take a few days, and hacked-spam reviews can take up to several weeks. Search Console Help says most reconsideration reviews take several days or weeks. After approval, warnings are removed within 72 hours.

What if Search Console shows no sample URLs?

A missing sample list does not mean no pages are affected. Google says it may not be able to generate samples for some issues. Check the whole site for hacked content, deceptive pages, and third-party embeds, then request a review if you are confident the site is clean.

Will the warning hurt my search rankings?

Yes, it can. Affected pages can carry a warning label in search results, and visitors who see a full browser warning usually leave at once. The flag stays until Google approves a review, so clean the site, close the entry point, and request the review as soon as the cleanup is complete.

What should I do if the warning comes back after a cleanup?

Treat it as a missed backdoor or an entry point that is still open. Reopen the Security Issues report for new sample URLs, check recently changed files and unknown admin accounts, replace core and plugin files again, and reset all passwords. Do not request another review until the second cleanup is complete.

Sources

  1. Social Engineering (Phishing and Deceptive Sites) Google Search Central
  2. Security issues report Search Console Help
  3. Request a review web.dev
  4. Hardening WordPress WordPress Developer Resources
  5. How To Find and Remove Hidden Website Backdoors Sucuri
  6. How to Audit and Cleanup WordPress Plugins and Themes Sucuri
  7. Safe Browsing site status Google Transparency Report

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test