Audit rules

Flagged by Safe Browsing

Google Safe Browsing lists the URL as a threat (malware, social engineering, unwanted software). In a QuikSEO audit, a failure of this rule has error severity and counts against the score. Below are the exact condition, its exceptions and the sources behind it, followed by the other rules of the same group.

01 — Definition

How This Rule Is Checked

The rule is a pure function of the fetched page: no extra requests, no account settings. The same input always gives the same result.

Rule Severity and Score

Rule id: security.safe_browsing
Group: Security
Severity of a failure: Error
Counts in the score: Yes, whenever it applies to the page
Required for a score: No
Replaces the check: safe_browsing

Condition and Exceptions

Condition: Probe safe_browsing: any threat → fail
Exceptions: No probe (no API key) → not_checked; an API error, an exception or the test switched off (error set) → not_checked with the reason, never pass

Sources and Project Decision

Sources: Preventing and monitoring abuse on your site (Google Search Central, Q43)
Safe Browsing Lookup API (v4) (Google for Developers, Q24)
Project decision: Only an answer from Google can pass; an API error, an exception or the test switched off is not_checked with the reason.

02 — Security

Other Rules in This Group

The other checks of the same group, each with its own condition and sources.

X-Content-Type-Options Missingsecurity.content_type_options
Content Security Policy Missingsecurity.csp
Framing Protection Missingsecurity.frame_protection
HSTS Missingsecurity.hsts
Permissions Policy Missingsecurity.permissions_policy
Referrer Policy Missingsecurity.referrer_policy
Form Submits Over HTTPsecurity.unsafe_forms