3 ms·
I think the reason Google does this is to prevent the site you're landing on from knowing what you searched for through the HTTP Referer header.
by jameslk 8y ago
I think the reason Google does this is to prevent the site you're landing on from knowing what you searched for through the HTTP Referer header.
- Nicksil 8y agoI vaguely recall the `rel` attribute value "noreferrer" on the anchor element producing this behavior; is that not the case (any more)?
- zenexer 8y agoThat's graduated into Referrer Policy, more or less, but it should still work.
- jakeogh 8y agoThat header is the user-agent's decision, I consider it an anti-user feature. Google (like most search engines) wants to know what you clicked on.
- zenexer 8y agoThat's correct. Google uses Referrer-Policy [1] to prevent the full referrer from being sent to the destination website. The transition page is purely for tracking. The ping attribute [2] is meant to replace that transition page eventually, but it needs to be ubiquitous and equivalent in terms of features before Google switches to that method. [1]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Re... [2]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#attr-ping https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#...