Google HTTPS Search Results for Logged-In Users
October 19, 2011I saw this post today on Google switching to HTTPS search results, referred from my trusty Slashdot.
Obviously, I didn’t like it – mostly because, from a website owner perspective, it eliminates the ability to get real-time reporting on keywords, which makes response to media events and such where mass keyword-driven traffic to your site all of the sudden requires proper response & content.
Curious as to whether sites would show up as “no referrer” (i.e. with referrer data totally stripped out) or if they’d show up redirected like Google+ links, I did some tests. They do show up with a Google referrer – just one that has the search keywords obfuscated:
Clicking through a link from HTTPS Google:
I searched for “These Terrible Twos Aren’t Too Terrible“, clicked on the top link which is from my parenting site.
The log line I get resulting from this click through is:
4.2.2.2 - - [19/Oct/2011:11:26:48 -0500] "GET /these-terrible-twos-arent-too-terrible/ HTTP/1.1" 200 66517 http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved= 0CB0QFjAA&url=http%3A%2F%2Fwww.scientologyparent.com%2Fthese-terrible-twos-arent-too- terrible%2F&ei=OfqeTpH2B4Pi0QHBoI2SCQ&usg=AFQjCNHBqTWXZLEY0uBUia1-l7RegVujXA" "Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1"
It obviously then obfuscates the search terms, but still at least tells you it was a Google organic result. I’ve yet to see how Google plans to deliver these 30-day Keyword digests, but now that will obviously become another staple of daily analytics.
Update:
Curious as to how the rest of Google & Facebook services handle HTTPS links, I ran the same test on HTTPS Gmail, Google+ and Facebook. Results:
Clicking through a link from HTTPS Gmail:
4.2.2.2 - - [19/Oct/2011:12:01:21 -0500] "GET /these-terrible-twos-arent-too-terrible/
HTTP/1.1" 200 66517 "-" "Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1"
4.2.2.2 - - [19/Oct/2011:12:01:21 -0500] "GET /these-terrible-twos-arent-too-terrible/
HTTP/1.1" 200 66517 "-" "Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1"
I had earlier done some tests on Google+ HTTPS, and clicking through links in G+ would send you to an intermediate HTTP page which then would send you on to the target link. This way, one could at least tell if traffic was coming to your site from Google+. It seems they’ve done away with that, which is unfortunate. I haven’t seen any traffic appear in my stats from Google+ since shortly after launch — I always attributed that to low takeup on G+ compared to my followings on Facebook & such, but now it appears that it’s simply because the referring info was stripped out.
Clicking through a link from HTTPS Facebook:
4.2.2.2 - - [19/Oct/2011:12:02:33 -0500] "GET /these-terrible-twos-arent-too-terrible/
HTTP/1.1" 200 66517 "http://www.facebook.com/l.php?u=http%3A%2F%2Fwww.scientologyparent.com%2F
these-terrible-twos-arent-too-terrible%2F&h=tAQA11y3eAQBsxDhnT7lzULhrGsW4OkAZv30JIUOUOuUTlA"
"Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1"
Facebook is the only other service that actually redirects you to an intermediate HTTP page that at least discloses where the traffic came from.
Note: See this post I made on Google+ back on 7 July:
https://plus.google.com/101265368753828318255/posts/eJqQCgznhtb
At that point in time, G+ HTTPS links would indeed route you through to an interstitial HTTP page which would then provide a referrer string, such that one could at least tell that the user had clicked-through from G+.