One question I often get asked is, “Why can’t I use Google Blog Search to track my coverage?” There are a variety of reasons one would not want to do this, most importantly, Google’s metrics are meaningless.
To demonstrate the flaws in Google’s metrics, I decided check out the blog coverage from Google Wave. Doing a quick search in Google Blog Search revealed about 1,569,236 results. Was this a lot of conversation? Looking over on the left, I saw the time frame was set to anytime. Anytime is a little ambiguous so I narrowed it down to last week, and it returned about 15,419 results. Using a separate browser, I ran the same query and it returned about 27,085 results. That’s a difference of 11,666 results. How could this be? It was from the same machine, just different browsers (one being Safari, the other Firefox). In fact, each time I hit refresh the numbers changed.
Aside from different browsers getting different results, Google has another problem: the problem of counting. Running a query for “Apple TV” for the date rage of 9/22-9/24 returned 1,526 results. I wanted to know if there was a spike in conversation between these days so I ran the query once for each day. The queries returned 162, 160, and 142 for the three days: 9/22, 9/23, and 9/24 respectively. Adding those numbers returned 464 results. The math didn’t make sense (464 does not equal 1,526). As it turns out there is an explanation.
The number Google provides is only an approximation based on the probability of the the search terms occurrence in blogs. Although I was not able to get an official word from Google (I’ll update the post if I hear back from them on the matter) there is a quote from an unnamed Google employee. It’s old, but after testing the results, it seems they haven’t done much in this area.
There are small variations in the number of results due to the fact that index updates are done at different times in different data centers. But there are much larger variations due to the fact that these are all estimates, and we just haven’t tried that hard to make the estimates precise. To figure out the number of results in the query [a OR b], we need to intersect two posting lists. But we don’t want to pay the price of intersecting all the way to the end, so we do a prefix and then extrapolate. The extrapolation is done with the help of some parameters that were carefully tuned several years ago, but haven’t been reliably updated as the index has grown and the web has changed, so sometimes the results can be off.
Bottom line, Google’s search results are not meant to be used as an analytics platform.