I left a few comments below, but I wanted to say thanks for mentioning some searches that Google didn't do well on. They're interesting searches, so I thought I

I left a few comments below, but I wanted to say thanks for mentioning some searches that Google didn't do well on. They're interesting searches, so I thought I'd break them down: - [avaya 103r manual] It's a fair complaint to say some low-quality results are returned, but there's a reason. Do that search and Google says "About 1,510 results." That's a minuscule number of results--it usually means the web has very little content that matches that query in any way. That's why the lower-quality and foreign results show up: we're scraping the bottom of the barrel of the web to find any results at all, and there's not many pages that have that those words. If you go to avaya.com and search for [103r], they don't find any results either. It's hard for Google to return useful Avaya results when avaya.com doesn't have that word anywhere on the site. :) - You were looking for specs on a Gateway mt6840 motherboard, specifically the socket. Instead of trying to solve that in one query, I'd go for doing it in two steps. I did the query [site:gateway.com mt6840] to see if there was any authoritative result, and the #1 result was http://support.gateway.com/s/Mobile/2007/Oasis/1014554R/1014554Rsp2.shtml http://support.gateway.com/s/Mobile/2007/Oasis/1014554R/1014... which has specs for that motherboard, but not the socket. But that spec sheet mentions that the motherboard uses a Intel® Core™ 2 Duo processor T2450. So then I searched for [T2450 socket] and got a Wikipedia page that says the T2450 uses Socket M. Just to be safe, searching for [MT6840 "socket m"], which returns a page on computing.net that's a forum with some ads, but the page mentions "945GM-based laptops support Socket M Core 2 Duo CPUs." The Gateway spec sheet says the MT6840 uses a 945GM chipset, so Socket M seems like a safe bet. - The last search was about an OpenSolaris machine that wouldn't boot and that said "Error 16" instead. The complaint was that the results were stale/old. I did the search [opensolaris boot "error 16"]. Then over on the left-hand side, click "Show search tools" and click "Past year" to get results from the past year. The #1 result shows a long discussion about debugging this (which implies it's not a trivial issue). The #2 result is a discussion that points into opensolaris.org, which then points to this bug: http://bugs.opensolaris.org/view_bug.do?bug_id=6774616 http://bugs.opensolaris.org/view_bug.do?bug_id=6774616 . My point on this query is that you can use the left-hand search bar to restrict the results to a certain time range (e.g. only results from the last week, month, or year). We do try to provide tools (e.g. estimated number of results, or the ability to restrict results by date) to help find the answers--or to find out if there aren't good answers on the web. And in some cases like your #2 search, we could do a better job of synthesizing information. If page A says that a motherboard uses this chip/chipset and page B says that this chip/chipset uses this socket, then we could infer what socket the motherboard uses. Inferring information like this is really tricky though because the web can be really noisy. I'm not saying Google shouldn't do better on these searches. You're clearly a power searcher, and I share your frustration when it's really hard to find what you want using Google. I'll pass this article around within the search quality group at Google and see if we could do better on searches like these--thanks for the feedback.