Security is not a direct ranking factor, but HTTPS is, and mixed content or forms that send data unencrypted make browsers warn users. Security headers protect your visitors against common attacks.
AD2SPIDER checks every page for mixed content and insecure forms, and audits the HSTS, Content-Security-Policy, X-Content-Type-Options, clickjacking protection and Referrer-Policy headers, as well as external links that open tabs without noopener.
HTTPS and security headers warnings
Real problems worth fixing.
Mixed content
- Why it matters
- An HTTPS page loads a resource over HTTP: the browser may block it or flag the page as insecure.
- How to fix it
- Load the resource over HTTPS.
Form submitting over HTTP
- Why it matters
- An HTTPS page has a form whose target is HTTP: the data travels unencrypted and the browser warns the user.
- How to fix it
- Change the form action to HTTPS.
Form on an HTTP page
- Why it matters
- The page is served over HTTP and has a form: whatever is typed travels unencrypted and the browser marks it as not secure.
- How to fix it
- Serve the page over HTTPS and redirect the HTTP version.
HTTPS and security headers opportunities
Improvements with impact, usually based on configurable thresholds.
No HSTS header
- Why it matters
- Security recommendation, not a ranking factor: HSTS forces browsers to always use HTTPS.
- How to fix it
- Add Strict-Transport-Security after checking the whole site works over HTTPS.
External target=_blank links without noopener
- Why it matters
- Without rel=noopener the external page could control this tab (window.opener). Modern browsers apply it by default, but not all.
- How to fix it
- Add rel="noopener" (or noreferrer) to external target=_blank links.
Protocol-relative links (//)
- Why it matters
- URLs starting with // inherit the page's protocol: over HTTP they load unencrypted resources. It is an outdated practice.
- How to fix it
- Write URLs with explicit https://.
Missing Content-Security-Policy
- Why it matters
- Without CSP the browser does not restrict where scripts and resources load from: it protects against XSS. Security, not ranking.
- How to fix it
- Define a Content-Security-Policy header, starting in report-only mode to avoid breakage.
Missing X-Content-Type-Options: nosniff
- Why it matters
- Without nosniff the browser may reinterpret a file's type and execute content it should not.
- How to fix it
- Send the X-Content-Type-Options: nosniff header on every response.
No clickjacking protection
- Why it matters
- Neither X-Frame-Options nor CSP frame-ancestors: another site can embed this page in an iframe to trick users.
- How to fix it
- Send X-Frame-Options: SAMEORIGIN or CSP frame-ancestors 'self'.
Insecure Referrer-Policy
- Why it matters
- The declared policy sends the full URL to other sites. Without a header, browsers already apply strict-origin-when-cross-origin, so only an insecure declared one is flagged (Screaming Frog also flags a missing one).
- How to fix it
- Use strict-origin-when-cross-origin or a stricter one.