Safe Browsing Test
The Safe Browsing Test queries Google's Safe Browsing list to see whether any URL has been flagged as malware, phishing, social engineering or unwanted software. A flagged URL triggers the red "Deceptive site ahead" interstitial in Chrome, Firefox and Safari — effectively blocking 90%+ of organic traffic and suspending all advertising until cleared. The test is free, instant and the first thing to run when traffic suddenly drops or someone reports a warning.
What This Tool Checks
- Google Safe Browsing classification (clean, malware, phishing, etc.)
- Compromise indicators (injected scripts, suspicious redirects)
- Cross-check against community blocklists
- Suspicious outbound link patterns
- Cloaking detection (different content to bots vs users)
Why It Matters for SEO
A Safe Browsing flag is the worst possible thing that can happen to a website's traffic. Browsers display a full-page red warning before users can reach the page, ad networks pause all campaigns, and Search Console issues a manual action notice. Detection is the first step; the second is removing the malware, requesting review in Search Console, and waiting for re-crawl. The test takes seconds; the recovery from a flag takes days.
How to Fix It
If flagged, identify the compromised content via Search Console > Security Issues, remove all injected code, change all admin passwords, update all software, and submit a review request via Search Console. Going forward, monitor Safe Browsing status weekly, keep CMS / plugins / server software patched, and use a web application firewall (WAF) at the CDN edge.
How It Works
We query the Google Safe Browsing API for the URL and the parent domain. If flagged, we report the threat type and approximate listing date. We also do a behavioural scan of the page for common compromise indicators (unexpected outbound iframes, base64-encoded scripts, suspicious redirects).
Common Mistakes to Avoid
- Compromised CMS plugin injecting malware (most common WordPress issue)
- Outdated server software with known RCE vulnerabilities
- Stolen credentials letting attackers add malicious pages
- User-uploaded content not scanned for malware
- Not monitoring Safe Browsing status proactively
Quick Checklist
- Safe Browsing returns "no threats" for your domain
- CMS, plugins and server software fully patched
- Admin accounts use strong passwords + 2FA
- WAF (Cloudflare, Sucuri) enabled
- Search Console > Security Issues monitored