http://googleblog.blogspot.com/2011/10/making-search-more-secure.html
QuoteWhat does this mean for sites that receive clicks from Google search results? When you search from https://www.google.com, websites you visit from our organic search listings will still know that you came from Google, but won't receive information about each individual query.
No more keyword data in my server logs? >:(
bastards.
Any idea about what percentage of users actually log in to Google?
well, on the plus side, we're about to find that out quite accurately for some sites. Which will be good because it'll help me prioritise the +1 items on my list.
When autocomplete came in I worked out logged in users to probably being about 3% (or something really low) of all internet users in the UK, based on inaccurate figures, gmail usage and some sheer guesswork. Possibly more people stay logged in now because of +1? Doubt it.
Even 3% is a pain in the arse though - especially when you're mid way through developing long tail traffic on a site. Webmaster centrals 1000 to aggregated results won't really go that far for a lot of sites :(
Cutts said last night that it was a single figure percentage. At the time I wasn't sure whether he meant to the users logged in on .com were a single-figure of all searches, or whether logged in ones were a single figure. Hoping from gurties data it is the latter.
Sucks though. Sucks unbelievably. On a selfish front, if that % is any higher I probably need to now scrap 6 months work I've been doing on something.
Why are they doing this? Is it to make SEO more difficult so it is more difficult to manipulate search results? What is the purpose of Google doing this? What would keep them from redirecting *all* of their search results so we'd get *no* referrers?
Not a good thing for SEO. That said, it would be trivial for browsers to start carrying referer data for SSL to non-SSL. The data is there, it just needs to be passed on.
The silver lining? I could see this being good for affiliates as it makes it that much harder for merchants to deconstruct their affiliates traffic sources.
My bet is Google will soon allow you to see more keywords via webmaster tools and Analytics integration.
They want more people to switch
Then for their new enterprise analytics customers they will show all keywords.
(not provided) will soon be the most converting keyword ever then??
Good job we brought the emd domain
www.notprovided.co.uk
Listening to the Strike Point w Jason / Mikkel discussing this. Would I be right in thinking you could trap the info by "fronting" any given domain with HTTPS, then global 301 > HTTP equivalent page? Or would you be more concerned about the possible loss of trust if a SSL cert fails for some reason
Again, I ask: what is the purpose of Google doing this?
"All your keywords/referrals are belong to us."
@Jason
OK, I'd thought they were sending a null field, not a fake one
>why
So they can sell their corporate clients access to the data for a premium fee.. and screw with the SEO's in same time? :)
incidentally we're tracking the split of logged in/not logged in users, and seeing in the UK only around 2.5% from logged in users, but more like 15% in the US.
travel only
thanks. Only 3+ years late ;)
Jason, he sent you a PM to tell you, and everything...
Firefox 14.01 just out. Firefox G searches are now SSL by default.
I swear I read somewhere that if the searcher gets taken to a https page then you can see the referrer data.
e.g. https -> https (works)
https -> http (doesn't)
Is that right or did I dream that?
Quote from: Chunkford on July 17, 2012, 04:25:44 PM
I swear I read somewhere that if the searcher gets taken to a https page then you can see the referrer data.
e.g. https -> https (works)
https -> http (doesn't)
Is that right or did I dream that?
Yep that's correct, Jason has a post on here somewhere that broke down all the permutations of how you can/can't get referral data but that's the main gist of it.
Between this and the ever increasing use of sample data analytics is starting to get a bit flakey
Quote from: BoL on July 17, 2012, 04:47:28 PM
Quote from: Chunkford on July 17, 2012, 04:25:44 PM
I swear I read somewhere that if the searcher gets taken to a https page then you can see the referrer data.
e.g. https -> https (works)
https -> http (doesn't)
Is that right or did I dream that?
Yep that's correct, Jason has a post on here somewhere that broke down all the permutations of how you can/can't get referral data but that's the main gist of it.
So if we go 100% ssl we get our data back? That seems too easy
Seems to be that way
http://en.wikipedia.org/wiki/HTTP_referer
QuoteIf a website is accessed from a HTTP Secure (HTTPS) connection and a link points to anywhere except another secure location, then the referer field is not sent.[6] (http://tools.ietf.org/html/rfc2616#section-15.1.3)
An interesting sentence after that regarding HTML 5.
QuoteThe upcoming standard HTML5 will support the attribute/value rel = "noreferrer" in order to instruct the user agent not to send a referer.[7]
> So if we go 100% ssl we get our data back? That seems too easy
It is too easy
SSL -> SSL sends referer - that isn't the issue.
G purposely fakes the referer by replacing the real search referal URL with fake URL. Hence the "Not provided" issue
I thought that was the case. Would have been kicking myself for weeks if I'd missed that.
It could be possible to workout the entry keyword from [secure search] keywords. G is still giving the rankings for the secured search keywords, so if you know how you're ranking for certain keywords you can make a pretty good educated guess. No programs doing this yet though that I know of.
They are providing the keywords to the paid advertisers (PPC) but not to the organic traffic. It's unfair but we get used to that.