Few things stop traffic as fast as a full red screen in Chrome saying your website is dangerous. Visitors leave, ad campaigns stop and customers start emailing.
The warning comes from Google Safe Browsing, the same blocklist used by Chrome, Firefox, Safari and many other apps. The good news: Google has a clear review process, and false positives are fixed regularly. Here is how.
Key takeaways
- Chrome, Firefox and Safari all use Google Safe Browsing to show red warnings.
- The warning is often triggered by one URL, such as a hacked page, a form or a download.
- Removal goes through the Security Issues report in Google Search Console.
- Reviews are usually completed within one to three days when the request is well documented.
The different Chrome warnings
Google Safe Browsing shows several types of warnings, each tied to a different threat category:
- Deceptive site ahead: Google believes the page is phishing or social engineering.
- The site ahead contains malware: the page is thought to distribute harmful software.
- The site ahead contains harmful programs: unwanted software or misleading downloads.
- Dangerous download blocked: a specific file was flagged, not the whole site.
The wording tells you what to look for. A deceptive site warning usually points to a login form, payment page or brand impersonation, while a malware warning points to scripts or files.
Why Google flags legitimate websites
Safe Browsing scans billions of URLs automatically. Clean sites get caught when they look like known threats, for example a login page that resembles a bank, a page with lots of external redirects or a site that was briefly hacked. Our article on why clean websites get phishing warnings explores these triggers in detail.
How to request a review in Search Console
Google only accepts review requests from verified site owners. Follow these steps:
- Verify your domain in Google Search Console if you have not already done so.
- Open Security & Manual Actions, then Security Issues, to see the exact problem and sample URLs.
- Fix or remove every flagged URL and check the rest of the site for similar content.
- Click Request Review and explain what the page does and what you changed.
- Wait for the email from Google confirming the review result.
What to write in your review request
Keep it short and factual. Explain your business, describe the flagged page and state clearly whether it was a false positive or a compromise you have since cleaned up. Mention specific actions such as "removed injected script from footer.php" or "the login page is our own customer portal". Vague requests are more likely to be rejected.
See our Google Safe Browsing false positive guide and the in-depth review walkthrough.
After the warning is lifted
Once approved, the warning usually disappears from Chrome within hours. Other browsers and tools that cache Safe Browsing data may take a little longer. Because Safe Browsing data also feeds into VirusTotal, check that report as well and contact any other vendors that copied the listing.
Frequently asked questions
How long does a Google Safe Browsing review take?
Google states that reviews for phishing take about a day and malware reviews a few days. Most well-documented requests are handled within 72 hours.
Can I remove the warning without Search Console?
Not as the site owner. You can report an incorrect warning through Google's public form, but a Search Console review is faster and more reliable.
Why was my review request rejected?
Usually because a flagged URL is still live or a similar page exists elsewhere on the site. Recheck every sample URL before requesting another review.
Will the warning hurt my SEO?
While the warning is active, visitors bounce and Google may show a notice in search results. Rankings usually recover once the warning is removed.