"There are three kinds of lies: lies, damned lies and statistics," said Mark Twain. Progress has given us a fourth: Web statistics, and now Google has inadvertently invented a new way to make it even worse.
Google is obsessed with speed. You know about Chrome, the hot rod of the browser world. You probably know about autocompletion. You might know about Google Instant, but you probably don't know about SPDY. There's so much speed it's hard to keep up. The newest improvement, announced today, is Instant Pages.
It's actually been in the Chrome developer channel for awhile, so I've been trying it.
As you type in Google Instant, searches are being run and results displayed on the page.
But as you type in Instant Pages, whole pages are being requested from potential destinations. This is being integrated with Google Search so even before you've decided where to click, Google has already predicted your behavior and your browser has fetched the page.
The result is faster page displays. For users, this is great. So what's the problem? Take a look at this screenshot:
This is a Drupal 7 Watchdog report showing 404s -- requests for invalid URLs.
What's causing this? Me, typing with my thumbs, apparently. While I'm mumble-typing, Chrome is happily tugging at the website, generating bogus page requests during my the pauses.
So if anyone is typing in a URL, or if Google's simply guessing wrong about which search result you'll be clicking, the browser is going to be creating server hits that can screw up your Web metrics (as well as create unwanted server load and error reports).