Docs Security

Referrer-Policy

Checks that your homepage sends a Referrer-Policy header, which controls how much of your page address is passed to other sites.

SecurityWeight 1In reports as referrer

What it checks

It passes when the homepage response has a Referrer-Policy header with any value. The value is not judged, and a referrer meta tag is not read.

Why it matters

When a visitor clicks a link or the page loads a file from another site, the browser can send the address of the page they were on. Addresses can hold search terms, email addresses or tokens in the query string.

Current major browsers already default to a fairly safe policy. Setting the header yourself makes the behaviour the same in every browser and lets you choose a stricter one.

How to fix it

For most sites, strict-origin-when-cross-origin is a good choice: other sites see only your domain, never the full address. Use same-origin or no-referrer if you want to share less. Avoid unsafe-url, which sends the full address everywhere.

Platform notes

Cloudflare

Add it with a Transform Rule that modifies response headers.

Nginx and Apache

Use add_header on Nginx or Header set on Apache.

Next.js, Vercel and Netlify

Set it in next.config.js headers, vercel.json, or a Netlify _headers file.

WordPress

Add it in server config, through your host, or with a security header plugin.

Shopify, Wix, Squarespace and Webflow

These platforms control the response headers on their own hosting, so there is usually no setting for this header in the site editor. If you need it, ask the platform's support what your plan allows.

Your report shows what this check found on your site. Pro shows the exact fix for your site. See pricing.

See what this check finds on your site

Free, about 30 seconds, with every other check included.