Understanding the Google API Response
While the Google API grants you programmatic access to the lion’s share of Google’s index, it doesn’t provide all the functionality available through the Google.com web site’s search interface.
The Google API, in addition to simple keyword queries, supports the following special syntaxes [Section 1.5]:
site: daterange: intitle: inurl: allintext: allinlinks: filetype: info: link: related: cache:
The Google API does not support these special syntaxes:
phonebook: rphonebook: bphonebook: stocks:
While queries of this sort provide no individual results, aggregate
result data is sometimes returned and can prove rather useful.
kincount.cgi [Hack #70], one of the hacks in this book, takes
advantage of result counts returned for
The 10-Result Limit
While searches through the standard Google.com home page can be tuned [Hack #1] to return 10, 20, 30, 50, or 100 results per page, the Google Web API limits the number to 10 per query. This doesn’t mean, mind you, that the rest are not available to you, but it takes a wee bit of creative programming entailing looping through results, 10 at a time [Hack #51].
What’s in the Results
The Google API provides both aggregate and per-result data in its result set.
The aggregate data, information on the query itself and on the kinds and number of results that query turned up, consists of:
A Boolean (
false) value specifying whether or not results were ...