the frequency a kenny chung blog

I’d like to preface this blog post by saying that I’m usually the first to poke fun at SEOs who blog about the “search impact” of every little thing that Google does, whether it’s changing a font, repositioning items slightly in the SERP, or whatever the case may be. So in order for me to get riled up over something they do, it has to be huge. And this recent update to Google Analytics is nothing short of huge.

To quote this Google Blog Post:

When a signed in user visits your site from an organic Google search, all web analytics services, including Google Analytics, will continue to recognize the visit as Google “organic” search, but will no longer report the query terms that the user searched on to reach your site. Keep in mind that the change will affect only a minority of your traffic.

Under the clearly cop-out guise of protecting user privacy, Google is going to start not reporting on organic keywords that logged-in users search. Isn’t that the whole selling point of Google Analytics? If not, it’s definitely a major one- the ability to see how users reach your site and how you can better position yourself in the space to garner more clickthroughs.

Google Control All The Data
Visual Approximation of Google Engineers

I especially take issue with the last line I quoted above: Google says that this will only affect a minority of organic traffic. B-U-L-L. Think about it for a second. Who’s most likely to use SSL? Or to put it even more broadly, who’s most likely to be logged into their Google accounts when searching? First on the list are net savvy people who work in the cloud and rely on Google and Google Apps services (including companies who run on Apps). Think about the repercussions of a tech content site not being able to see how admins or webmasters are reaching their resources. You also have people on local networks who are most likely to use SSL- probably the majority of college students on a shared network. That is definitely a key demo. And maybe this one slipped past people’s radar, but in order to do anything with an Android phone, you need to be logged into your Google account! So every single Android user will have their keywords stripped as well. Is Google trying to make us hate their mobile OS and its users?

So what’s an SEO to do? Not much to do, really. We can storm Mountain View with our pitchforks, but Google is stubborn, especially when it comes to PR- and soundbyte-friendly topics such as “user privacy”. Let’s face it- Google’s plan is to have more people use their services and to be logged in indefinitely (take the ubiquitous “+You” bar, for example). Given enough time, Google will have everyone logged in whenever they search, and then they’ll also control all of that query data.

Talk about having your cake and eating it too.

March 1st, 2011
according to

This past week, NPR’s On The Media dedicated the latter half of their show talking about Search Engine Optimization. There’s some good basic stuff in there, putting all of the recent bombshells and ramifications into lay terms. Available in audio form and transcripts.

The segments:

How to Cheat Google
David Segal, the author of the NYT article outing JCPenney, explains some of the problems with the algorithm and how Google punished JCP and other sites.

Matt Cutts, Head of Google’s Web Spam Team
Interview with Matt Cutts about how Google engineers operate and how they respond to user questions, etc. Pretty standard stuff from Cutts.

How Search Engines are Changing Journalism
How online news outlets are using SEO to their advantage, including the HuffPo model.

Steven Rosenbaum and the Curation Nation
Interview with the CEO of who says that user recommendations may become more important than search engines when it comes to sharing content.

The Formula for a Most-Emailed Story
Professors looked at months’ worth of NYT articles and came up with some factors that correlate to high levels of sharing (including the quantification of “awe”).

Link to stream/download the full 02.25.11 Episode of On The Media.

Creative Commons License
licensed under a Creative Commons Attribution-No Derivative Works 3.0 United States License.