Apparently, Google is testing search results delivered through Ajax from Google.com. What does this mean? It’s breaking search and keyword tracking for Google Analytics, Clicky, and any other analytics app you care to name. Here’s an example:
With the URL, http://www.google.com/search?q=erik+deckers this tells the analytics app that someone on Google was searching for Erik Deckers. And that shows up on my analytics page.
Six people have searched for me on Google. Thanks, Mom!
But what happens with the new Ajax-powered URLs?
http://www.google.com/#q=Erik+Deckers
That hash mark (#) is the problem. The analytics apps can’t recognize anything that appears after the hash mark, which means the analytics app only recognizes that searches came from Google, but not what brought them there.
Michael VanDeMar also discusses what might happen if Google switches to Ajax on his Smackdown blog.
Tweet This Post 
Digg This Post 
Ping This Post 
Reddit 
Stumble This Post
