Does the AJAX API really replace Web Search API?

[trashi]

Hello.

For testing and analysing I use the Google Web Search API  (http://code.google.com/intl/de-DE/apis/websearch/docs/) to read out different Google results. Now I noticed that the API is deprecated and in the doc's I found a link to the latest API, the JSON/ATOM Custom Search API. After I did read the doc-page of the new API, I created a Google Account and tried to create my "Custom Search Engine". The problem is, that Google needs several domains to provide the Google search enginge. Of course, I think this is a great feature for all webmasters who want to use the google engine on their own sites, but for me its a little bit senseless because I dont want to search for keywords on specific domains, I want to search in the whole Google index to get the general results from the websearch. That was exactly what the "depracted" Web Search API did, but I cant see how to use the new API for that issue.

Thanks for the help!

[Jeremy Geerdes]

The Custom Search API (CSAPI) is indeed the successor for the Web Search (AJAX) API. As you have noticed, the two are not exactly analogous. But if you do the initial setup of your CSE with a domain or two in that box, you can later go into the settings, remove the domains, and tell it to search the entire web. Even after you do this, though, you should not expect your results to correspond exactly to those of the AJAX API or a standard Google search.

It should also be noted that, while I don't know what your "testing and analysing" are, the CSAPI's (and actually, the AJAX API's) TOS explicitly prohibit accessing the service via any automated means (e.g., scraping, bots, load testing) to access the API for any purpose.

Jeremy R. Geerdes

Generally Cool Guy

Des Moines, IA

For more information or a project quote:

jrge...@gmail.com

If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church!

--
You received this message because you are subscribed to the Google
Groups "Google AJAX APIs" group.
To post to this group, send email to
google-ajax...@googlegroups.com
To unsubscribe from this group, send email to
google-ajax-searc...@googlegroups.com
To view this message on the web, visit
https://groups.google.com/d/msg/google-ajax-search-api/-/hXk9lD26b7EJ
For more options, visit this group at
http://groups.google.com/group/google-ajax-search-api?hl=en?hl=en

[Paul Beech]

Thanks for the clarification and this useful 'hack' Jeremy.

I'm currently monitoring Google Search for links to my clients'
illegally posted intellectual property. Manually finding links through
Google Search is too slow and cumbersome given the scale of the
problem and given Google automates the indexing of this content it's
an uphill battle.

The API limits are too low and costs are excessive, given I'm careful
about ensuring links are genuinely to illegal content (false positives
are not acceptable, the Megaupload issue being a prime example).

I'm grateful with the help Google gives in removing indexed links
under the DMCA et al, but given these API limits and the scale of the
problem, how can I successfully gather the links I'm looking for,
given the lack of an official way to do so by Google?

Is there an agreement or path to being able to partially automate the
collection of results through APIs or otherwise, even if certain parts
of the process are human-driven?

Thanks,

P. Beech
Web Guy in the UK.

[trashi]

Thank you for the extensive answer. I know the Google TOS and I'll
take care of it, as good as I can.
Additionally I think 5$ per 1000 queries are _not_ expensive and I'm
nearly sure, I'll claim that service.

> Even after you do this, though, you should not expect your results to correspond exactly to those of the AJAX API or a standard Google search.

Do you have further information regarding that issue or is it maybe
annotated in a part of the documentation?
Its no big problem for me, if the results aren't to 100% the same, but
I would like to know WHY.

Thanks and best regards.

[Jeremy Geerdes]

It is not documented, and the team won't comment on it. However, it is reasonable to assume that the disparity is designed to discourage people who would use the services to compete against Google.

Jeremy R. Geerdes
Generally Cool Guy
Des Moines, IA

For more information or a project quote:
jrge...@gmail.com

If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church!

> --
> You received this message because you are subscribed to the Google
> Groups "Google AJAX APIs" group.
> To post to this group, send email to
> google-ajax...@googlegroups.com
> To unsubscribe from this group, send email to
> google-ajax-searc...@googlegroups.com
> To view this message on the web, visit

> http://groups.google.com/group/google-ajax-search-api?hl=en_US