Chrome "Dangerous site" red full-page warning

What’s actually happening

Instead of your page, visitors get a full red interstitial titled "Dangerous site" with a "Back to safety" button. The continue link is buried under Details. This is the harsher Safe Browsing flag — more severe than the grey-ish "Deceptive site ahead" — and it tanks traffic instantly because Chrome (and every Chromium browser) shows it before the page renders. Search Console usually has a matching Security Issues report, and the URL shows as unsafe on Google's Transparency Report.

Common causes

• The site was hacked and is serving injected phishing pages or fake login forms (often hidden in subdirectories the owner doesn't check)
• Malicious or obfuscated JavaScript injected into the theme/templates, redirecting users or pushing forced downloads
• Social-engineering content: fake "update Flash," fake virus warnings, deceptive download buttons
• Compromised ad network or third-party script serving malware to visitors
• A nulled/pirated plugin or theme that shipped a backdoor, later used to plant the harmful content

How to fix it

1. Confirm the flag and read the exact reasonOpen Google Search Console, go to Security & Manual Actions, Security Issues — it names the category (social engineering, malware, harmful downloads) and often sample URLs. Cross-check the domain on Google's Transparency Report (transparencyreport.google.com/safe-browsing). Don't request a review until you've actually found the problem.
2. Find and remove the malicious contentScan the full document root, not just the homepage. Diff core files against clean copies, look in upload dirs for stray .php files, grep templates/header/footer for injected <script> and base64/eval blobs, and audit recently modified files (find . -mtime -14). Pull the listed sample URLs and view source to see what Safe Browsing saw.
3. Close the entry point so it doesn't come backReset all CMS/FTP/cPanel/DB passwords, update core, plugins, and themes, delete nulled extensions, remove unknown admin users, and rotate any leaked API keys. A review that passes while the backdoor is still open just gets you re-flagged in days.
4. Request a Safe Browsing review in Search ConsoleWith the site clean, in Security Issues click "Request Review," describe exactly what you removed and how you closed the hole. Phishing reviews often clear in roughly a day; malware can take a few days. Don't submit repeatedly — repeat false submissions slow you down.
5. Verify the warning is gone across browsersOnce Google clears it, the Transparency Report flips to "no unsafe content found," and Chrome, Firefox, and Safari all drop the block, since they share the Safe Browsing list. Hard-refresh or test in a fresh profile so you're not seeing a cached interstitial.