Shared publicly  - 
Google to make more changes to referrer URL reporting - still using privacy as unjustifiable excuse to stop supplying organic search keyword data. It isn't like users haven't been performing sensitive searches for years on topics like breast enlargement and who's gay or not ....

+Danny Sullivan rightly calls this out as the hypocrisy it is given that advertisers still get keyword data, sensitive or not. This is one of those admittedly rare cases where big Google is clearly behaving very badly.

Google's original announcement is here: but read Danny's article below to try to understand what it really means.
Martino Mosna's profile photoSean Carlos's profile photoMarco Cilia's profile photoDavid Iwanow's profile photo
they are using the meta refferer, though
Sure... but they're still using privacy as the excuse for the changes they're making... yet this has nothing to do with privacy.

It also remains to be seen as to what data they do or don't pass along with this change.

As a side point, WordPress plugins and the like which attempt to greet users based on their provenance, e.g. , will most likely need to be updated.
Io ho capito che il cambiamento aumenta le info, non le diminuisce. Adesso https è trattato come direct, in futuro come search, senza keyword
+Marco Cilia My understanding is that Google currently supplies the empty parameter name value pair q="" in https search referrers which is the signal Google Analytics uses to set the (not provided) pseudo keyword (and potentially to distinguish from non-search Google referrers, although most Google services seem to be using sub domains. Thus no change in info, AFAIK, but a change in how it is sent which will break some existing apps - and anything relying on log analysis as the albeit limited meta tag info won't be in the server log. So I've got a post idea for you: how to write meta tag page data to an Apache log file :-)
+Marco Cilia I'm not exactly sure what you have in mind - but it could be due to the late hour. Most logged in Google users default to https - e.g. all gmail users since 2010 etc: ref: I suppose there may be a Google account or two somewhere out there which isn't tied to a Google service which defaults to https, but they are probably few and far between at this point.
Add a comment...