http://code.google.com/apis/ajaxsearch/documentation/index.html#fonje
http://code.google.com/apis/ajaxsearch/documentation/reference.html#_intro_fonje

The API key is no longer required, but you do have to supply a valid  
http_referer header. I would recommend that this referer be a url that  
contains information about your application and a way to contact you  
should Google have a problem, especially if you're not going to supply  
the API key.

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 Jul 27, 2009, at 8:48 AM, bleu wrote:

> Is it OK to call these results like this in REST,
>
> eg:
> http://ajax.googleapis.com/ajax/services/search/web?v=1.0&q=+site:http%3A%2F%2Fwww.twitter.com
>
> And parase out the data I want without having to use the API license  
> key, and all the other aspects?
>
> s
> On 27 Jul 2009, at 15:30, Mike Norman wrote:
>
>>
>> Something like:
>>
>> http://ajax.googleapis.com/ajax/services/search/web?v=1.0&q=+site:http%3A%2F%2Fwww.twitter.com
>>
>> The "q=" query portion is empty, so the response contains Google's
>> estimate of the total
>> number of pages for the site:
>>
>> {"responseData": {"results":[{"GsearchResultClass":"GwebSearch", ...
>> "estimatedResultCount":"603000" ...}
>>
>>
>> On Jul 27, 1:39 am, bleu <[email protected]> wrote:
>>> Jeremy, thank you for your input, is there an example you can point
>>> me to
>>> as I cannot seem to find one online which shows the results from
>>> "estimatedResultCount"
>>>
>>> Many thanks in advance
>>> s
>>>
>>> On 27 Jul 2009, at 05:40, Jeremy Geerdes wrote:
>>>
>>>
>>>
>>>> site:mydomain.com should work with the AJAX Search API just as it  
>>>> did
>>>> with the SOAP Search API.  The problem with that approach would be
>>>> that the AJAX API's estimatedResultCount is not exactly reliable.
>>>
>>>> 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 Jul 26, 2009, at 5:05 PM, [email protected] wrote:
>>>
>>>>> I found with the old SOAP api it was possible to get the
>>>>> site:mydomain.com (no of pages indexed) result.
>>>
>>>>> How can I find out how many pages are indexed by google for
>>>>> mydomain.com with the ajax search api?
>>>
>>>>> many thanks
>>>
>>>
>>
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to