What we look for
These pages send no Referrer-Policy header (a rule for how much of the page's address is passed to other sites), or set it to unsafe-url or no-referrer-when-downgrade.
Why it matters
A loose policy can pass full addresses, with any private details in them, to other sites. It protects visitors but does not affect search results, so it costs no points.
How to fix
Set Referrer-Policy: strict-origin-when-cross-origin in your server, CDN or hosting settings.
What it cannot know
Current browsers already use strict-origin-when-cross-origin when the header is missing, so a missing header matters mainly in older ones.
Seen in a real crawl
From a crawl of Millbrook Hardware (the broken fixture), a test site from Raptor’s fixture suite.
16 pages have no Referrer-Policy, or an unsafe one
/Missing Referrer-Policy header/gone Missing Referrer-Policy header/missing Missing Referrer-Policy header
http://127.0.0.1:8001raptor 0.3.0, 17 Oct 2026Open this finding in that crawl’s report
It also fired on Kestrel Bay Digital and the js-heavy fixture.
Where you’ll see it
The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.
- Terminal
- When it is one of the five findings under Fix first,
raptor crawlprints the id under it.Check: security.
missing_ referrer_ policy - crawl.json and the CSV
- The crawl JSON names the finding by this id, and so do the CSV and
raptor_query."check_
id": "security. missing_ referrer_ policy" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= security. missing_ referrer_ policy - MCP
raptor_findingswith thischeck_idreturns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.raptor_
findings { "job_ id": ". . . ", "check_ id": "security. missing_ referrer_ policy" }