I've also tried changing settings, and still get these bad results. I wish Google would do something about it -- it's very frustrating, and I don't have this problem with other APIs.
On Dec 2, 1:32 am, "Gerhard W. Recher (abuse)" <[email protected]> wrote: > Hi Kieran, > > I can reproduce this for me: > > -- gerhard > > stdClass Object > ( > [responseData] => stdClass Object > ( > [results] => Array > ( > [0] => stdClass Object > ( > [GsearchResultClass] => GwebSearch > [unescapedUrl] > =>http://www.pap.lib.tx.us/obits/pap_panews-1994.htm > [url] > =>http://www.pap.lib.tx.us/obits/pap_panews-1994.htm > [visibleUrl] =>www.pap.lib.tx.us > [cacheUrl] > =>http://www.google.com/search?q=cache:nyYX__Mzt0EJ:www.pap.lib.tx.us > [title] => Obits 1994 > [titleNoFormatting] => Obits 1994 > [content] => JONES, <b>HORACE > (BUMBLEBEE</b>), 19940918, 7C. JONES, JESSIE MAE, 72, 19940812, 5C. > JONES, KRYSLYNN MICHELLE, INF, 19941121, 8A. JONES, LENORA E. 56, > 19940726, 6B <b>...</b> > ) > > ) > > [cursor] => stdClass Object > ( > [pages] => Array > ( > [0] => stdClass Object > ( > [start] => 0 > [label] => 1 > ) > > ) > > [estimatedResultCount] => 1 > [currentPageIndex] => 0 > [moreResultsUrl] > =>http://www.google.com/search?oe=utf8&ie=utf8&source=uds&start=0&safe=... > ) > > ) > > [responseDetails] => > [responseStatus] => 200 > ) > > > > Kieran wrote: > > I've experienced the same problem. Here's an example: > > >http://ajax.googleapis.com/ajax/services/search/web?q=%22Horace+Bumbl... > > > This yields 1 result: > > *http://www.pap.lib.tx.us/obits/pap_panews-1994.htm > > > Executing a query for "Horace Bumblebee" on the google.com web > > interface yields 3 results: > > * oldestandwisest.com/linked/first%20character%20appearance.doc > > *www.pap.lib.tx.us/obits/pap_panews-1994.htm > > * blogs.myspace.com/index.cfm?fuseaction=blog.view... > > > Some things I've tried varying are: the User-Agent, Referer / Key, > > safe search and duplicating filtering. > > > There doesn't seem to be much to do about it, based on what I've > > read. But I do wonder the following: can anyone try to replicate the > > exact search results above? I would be curious to know if everyone's > > AJAX requests are nerfed the same way, or whether different people's > > mileages vary. > > > Best, > > > Kieran > > > On Nov 7, 7:40 am, Josu <[email protected]> wrote: > > >> Hi, > > >> I'm using the REST interface and I'm getting different results. I've > >> seen issue 43 in code.google.com that is talking about this. However > >> I've realized that is open since May-2008. Will be fixed? Do we need > >> to change anything in the queries? > > >> Best Regards, > > >> Jordi Suñer > > > -- > > > 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 > > athttp://groups.google.com/group/google-ajax-search-api?hl=en. -- 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.
