Referrer trimming by browsers
Modern browsers trim the referrer for privacy: the default policy sends only the origin (scheme + host) when navigating cross-site, not the full path and query. So you often see example.com rather than the specific page that linked to you. This page explains the default referrer policy, why it exists, and why UTM parameters are unaffected.
Why browsers trim the referrer
The Referrer-Policy standard governs how much of the referring URL a browser shares. To reduce leaking page paths and query strings across sites, modern browsers default to strict-origin-when-cross-origin: for cross-origin navigations they send only the origin (scheme and host), and they send no referrer at all when downgrading from https to http.
The effect on analytics is that cross-site referrals commonly show only the bare domain. The full referring URL — the specific article or thread — is withheld by default, so you can see that traffic came from a site but not exactly which page on it.
- Default policy is typically strict-origin-when-cross-origin
- Cross-site referrers are reduced to the origin (no path/query)
- https-to-http downgrades send no referrer at all
Working with trimmed referrers
Trimming is not something to fight; it is the privacy baseline and it is consistent. Read the referrer as a coarse source — which site, not which page — and do not build reports that depend on full referring URLs you will rarely receive.
For the granular detail trimming removes, use UTM parameters on the links you control. Query parameters on your own destination URLs are not subject to referrer trimming, so utm_source, utm_medium, and utm_campaign give you the specificity the trimmed referrer cannot.
How it appears in analytics and logs
An origin-only referrer (the bare host with no path) is the expected result of the browser's default referrer policy on cross-site navigation. The missing path is privacy trimming, not a lost source — though it does mean you cannot see the exact referring page.
Diagnostic use case
Understand why your referrer report shows bare domains instead of full referring URLs, and rely on UTM parameters rather than the referrer path for granular source detail.
What WebmasterID can help detect
WebmasterID records whatever referrer the browser sends — full URL or origin-only — and reads UTM parameters that are not subject to referrer trimming, so source detail survives even when the path is stripped.
Common mistakes
- Treating an origin-only referrer as a bug instead of the default privacy behaviour.
- Building reports that depend on full referring-page URLs you will rarely get.
- Forgetting that https-to-http downgrades drop the referrer entirely.
Privacy and accuracy notes
Referrer trimming is a deliberate privacy default; WebmasterID treats the origin-only referrer as a coarse source and never tries to reconstruct the trimmed path or identify the visitor.
Related pages
- Referrer-Policy and missing referrers
Referrer-Policy is the web standard that controls how much of the referrer a browser sends with a request. Site owners set it via an HTTP header or a meta tag, and modern browsers default to a privacy-leaning value. Understanding the policy values explains why so many referrers arrive trimmed to the origin or missing entirely.
- HTTPS-to-HTTP referrer loss
A long-standing browser rule removes the referrer when navigating from a secure HTTPS page to an insecure HTTP page, to avoid leaking a secure URL into an unencrypted request. With most of the web on HTTPS this is less common than it once was, but it still explains specific cases of missing referrers — and it is a reason to serve your own site over HTTPS.
- UTM vs referrer: which wins
When a visit carries both a referrer and UTM campaign parameters, most analytics treat the explicit UTM source as authoritative over the inferred referrer. That is usually correct: UTM tags describe intent you set deliberately, while a referrer is whatever the browser happened to send. Understanding the precedence prevents double-counting and mis-attribution.
- Campaign links
Use UTM tags for the source detail that referrer trimming removes.
Sources and verification notes
- MDN — Referrer-PolicyDefault strict-origin-when-cross-origin and the per-policy behaviours.
- W3C — Referrer Policy specificationStandard governing how much of the URL is shared as a referrer.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.