The search results load via Ajax. That's the main difference that I see. Also notice that the URL changes when you type in your search result, but that the query args are sitting behind a # anchor. Normally, those values don't get sent via referrers, which would mean that you wouldn't get that information in the referer header on the server that hosts the search result when the user clicks it. However, in this case, Google is doing HTTP redirects in order to send that information along. At the very least, we can see that the format for their URLs has changed. But they may just be in a data-gathering mode right now. If they turn off that redirect, you won't be able to deduce the search query that the user typed in based on your webserver logs.
odd, the regular google.com has done this for me for quite some time. i thought it affected everyone until now. i just loaded a different browser with no cookies on it and it does searches the old non-ajax way. even though i'm logged out of any google services, my long-lasting google cookie must have this ajax option enabled on the main google.com site.
Interesting, you guys must be on one of those A/B tests that Google does without telling anyone. I certainly don't get AJAX results in the classic or sandbox searches.
