4 ms·
I found this reference from Google's analytics blog (which documents the change in Referer:s that people should expect), which seems to argue that ot is right:
by saurik 15y ago
I found this reference from Google's analytics blog (which documents the change in Referer:s that people should expect), which seems to argue that ot is right: this behavior has been in place since 2009.
http://analytics.blogspot.com/2009/04/upcoming-change-to-googlecom-search.html http://analytics.blogspot.com/2009/04/upcoming-change-to-goo...
(edit:) One of the comments from "Brett Crosby, Sr. Manager, Google Analytics" looks interesting:
"""Sorry for the delay in responding (especially Andre), I was seeking clarification from the search team. A lot of the comments were directed to them and I think it is best to let that team handle those questions. I do want to answer some of the Analytics questions though. Phil's comment above is correct. I posted this because a couple months ago Google tested some search results that added a # into the URL. This created a big problem for people interested in seeing which keywords were driving traffic to their site (anything in the URL after a # doesn't get passed in the referrer... this is particularly a problem for web analytics products), so we worked with the search team to stop that test until they could find a better solution. The announcement above is the answer to that. It allows them to test new search results without the negative side effects (if it introduced others, that was not the intent). Some of the other comments had interesting theories about why we did this (grassy knolls not included), but the goal was to allow new tests of search without making it difficult for analytics products to report on query data."""
The post he is talking about from Phil, for reference:
"""I have previously heard about (from various sources) the intent by Google to roll-out a hash '#' in the search results page URL that would strip the paramaters altogether - is this blog entry implying that this will not happen now?? or is this something different?"""
This also puts forward an alternative explanation for why this is served only to JavaScript-capable clients than my theory below (which was that the goal was to use JavaScript to make the behavior transparent, but that that intention failed at a later point and was not noticed).
Honestly, this new explanation makes even more sense, now that I notice that the search query no longer exists in the Referer: portion of the /webhp URL that is being used for the super-fast AJAX Google search pages they have been deploying for a while now.
(That said, it is still really weird that they choose to hide the behavior until onmousedown; the only reason it would seen beneficial to do that is if they wanted to make the behavior transparent, and the way it is currently implemented seems to fail to do that: interacting with the link at all causes the URL to change to a /url URL.)