Yes, the API will return only up to 64 results. But, if I might offer a counterpoint as a relatively objective (i.e., non-Google employee user), 64 results is more than adequate for (a) the API's intended purpose and (b) the vast majority of its users. The reason for this is really quite simple. The AJAX Search API was not designed for SEO, data mining, or rolling your own search engine, etc., but for adding general search functionality to a website or application. When used for this, I honestly can't remember the last time I looked through all 64 results. In fact, if I don't find what I'm looking for by the end of the first page, I will almost always refine the search; certainly, by the time I get to page 4 I've changed my query.
If you are looking for more search results, you will need to go with a different service. Both Yahoo! and Live Search/MSN offer APIs similar to the AJAX Search API. Please note, though, that the last I knew, even these both offered only up to 1,000 results, which still isn't really adequate for real SEO or data mining applications. However, both of these also have some significant other restrictions. For instance, the Live Search/MSN API has a query rate limit that restricts you to only so many requests per 24-hour period (which, by the way, they bury in their TOU and even there don't tell you what it is anymore). Yahoo! is also preparing to roll a system by which they will charge you for queries past a certain threshold (the exact conditions hadn't been released yet the last time I was there). In addition, I can tell you from personal experience that Yahoo!'s API (they call it BOSS) has intermittent but significant performance and availability issues. And Live Search/MSN's TOU explicitly state that their goal is to respond to a query within 1.5 seconds, an eternity in performance terms! And these are only just a few examples of the limitations they place on their APIs. All of this to say that, while I would encourage you to recommend on the issue tracker that the API return more results (click the star on the link below), I'm not holding my breath that we'll see a dramatic increase any time soon. And frankly, I think that such an increase would actually inhibit its usefulness in the applications for which it was truly designed. http://code.google.com/p/google-ajax-apis/issues/detail?id=189 Jeremy R. Geerdes Effective website design & development Des Moines, IA For more information or a project quote: http://jgeerdes.home.mchsi.com http://jgeerdes.blogspot.com http://jgeerdes.wordpress.com [email protected] Unless otherwise noted, any price quotes contained within this communication are given in US dollars. If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church! And check out my blog, Adventures in Web Development, at http://jgeerdes.blogspot.com ! On Apr 16, 2009, at 10:54 AM, ahmad zaher wrote: > > 64 is the maximum number of results that can be returned using this > silly useless ajax api,, how to get more????????????????? > even this limit is not documented any where in thier documents very > bad google they are > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-AJAX-Search-API?hl=en -~----------~----~----~----~------~----~------~--~---
