More fixes

Visitors see a red "Deceptive site ahead" warning before your site

Customers tell you Chrome shows a full red page saying "Deceptive site ahead", "Dangerous site" or "The site ahead contains malware", and most of them leave. Firefox and Safari show the same block, because they all read Google's Safe Browsing list. Edge may show its own "reported as unsafe" page. The warning means Google found specific pages on your domain that phish, carry malware or trick visitors, and it stays until those pages are gone and someone asks for a review. It does not lift by itself. Below is a rebuilt example (not a real client), the five-minute check that names the flagged pages, and the fix for each cause.

What a visitor sees

What the check found


  

The five-minute check: what did Google flag?

  1. Look up your domain on Google's Safe Browsing status page. Search for "Google Transparency Report safe browsing site status" and enter your domain. It says whether the site is currently flagged and roughly why (deceptive pages, harmful downloads, unwanted software).
  2. Open Search Console's Security issues report. In Google Search Console, go to Security & Manual Actions > Security issues. It names the type of problem and lists sample addresses. Those samples are the starting point: open them in a private window and note what they are. No Search Console yet? Add the site (a DNS or HTML-file check) first; the report and the review button only exist there.
  3. Look for pages you never made. Phishing kits usually sit in an odd folder (/wp-includes/js/secure/, /.well-known/, /old/, a random string) and copy a bank, Microsoft or a parcel company. Your host's File Manager sorted by "last modified", or the host's malware scan, finds them quickly.
  4. Check Edge separately if it is Edge that warns. Microsoft keeps its own list (SmartScreen). A site can be clear on Google and still flagged there, or the other way round.

What causes it and the fix

What the check showsWhy it happensThe fix
"Deceptive pages" or social engineering; sample addresses are login pages for a bank, Microsoft 365, a parcel firmSomeone got in (an old plugin, a reused password, an abandoned FTP account) and uploaded a phishing kit. Your real pages may be untouched, which is why you never saw itDelete the kit's whole folder, not just the sample pages. Then close the way in: update or remove every plugin and theme you do not use, change every admin, hosting, FTP and database password, and remove admin users you do not recognise. Then request the review (below)
"Malware" or harmful downloads; the site sends some visitors to another site, or a scan finds injected scriptCode was added to your theme files, the database or .htaccess that loads a script from another domain, often only for phone visitors arriving from GoogleClean it the way site sends visitors to a spam page describes: replace core and plugin files from clean copies, search the database for the injected domain, check .htaccess. Restoring a backup from before the infection is faster if you have one, as long as you then close the way in
Flagged for a file you offer for download (a price list, a tool, a zip)Safe Browsing flags the download itself. An old installer, a macro-enabled document or a file a past web person bundled with something can trip itRemove the file or replace it with a plain PDF. If it is genuine software you make, sign it and host it on a well-known download service instead
Only one embedded script, ad or widget is named (a chat box, an old counter, an ad network)The third party's domain was taken over or sold, and your pages still load it. To Google, your page now serves what that domain servesRemove the snippet from the theme, the header-script plugin or the page builder's custom code box. An old visitor counter or a defunct widget is the usual one
Clean site, but you bought the domain recently or it lapsed and came backThe flag belongs to what the domain hosted before you. It stays until someone requests a reviewAdd the domain to Search Console, confirm Security issues lists nothing current, and request a review. If no review button appears, use Google's form for reporting an incorrect phishing warning
Only Edge warns ("This site has been reported as unsafe")Microsoft's SmartScreen list, separate from Google'sClean the site first, then use Microsoft's "report an unsafe site" page and choose that you are the site owner asking for a review; it asks for the address and what you changed

Requesting the review

  1. Confirm the sample addresses now answer "not found" and a host malware scan comes back clean. Asking too early fails the review.
  2. In Security issues, tick that you fixed each issue and press Request review. In the box, say what you removed and how you closed the way in (for example: "deleted phishing folder /wp-includes/js/secure/, removed unused plugin X that was exploited, reset all passwords, removed unknown admin").
  3. Wait. Deceptive-page reviews usually finish in a day or two, malware reviews in a few days. You get a message in Search Console either way. Visitors' browsers may keep the warning a little longer until their copy of the list refreshes.

What not to do

Requesting the review is a few clicks; finding the kit's folder, the backdoor that reinstalls it and the old plugin that let it in is the part most owners would rather hand over, especially with the warning costing customers every day. If that is you, the box below is for that. Related: site sends visitors to a spam page, Japanese spam in Google results and "Not secure" warning.