search

Raghuveersingh / google-ajax-apis

Automatically exported from code.google.com/p/google-ajax-apis
0 stars 0 forks source link

Add support for local Google search engines #78

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Please allow callers of the AJAX API to specify that they want a Google
engine local to them to provide the results, e,g, google.fr, google.co.uk etc.

The web search results from those engines are often very different to those
of google.com.

Thanks.

Original issue reported on code.google.com by andym...@gmail.com on 16 Jul 2008 at 8:16

GoogleCodeExporter commented 9 years ago

Original comment by lisba...@google.com on 28 Aug 2008 at 10:08

GoogleCodeExporter commented 9 years ago

Original comment by jrgeer...@gmail.com on 17 Sep 2008 at 2:00

GoogleCodeExporter commented 9 years ago

Original comment by yojoaq...@gmail.com on 25 Sep 2008 at 12:06

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
kindly support for local search i.e allow api to fetch results from local search
engines eg. google.co.in

Original comment by uptrie...@gmail.com on 28 Sep 2008 at 3:18

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago

Original comment by pezzoz...@gmail.com on 26 Oct 2008 at 5:38

GoogleCodeExporter commented 9 years ago 
Come on google this is very important...

Most countries search their region. We do here in AU, as does NZ, UK etc etc
Without this feature, I cannot use your search API.

-Stig

Original comment by stigma...@gmail.com on 17 Nov 2008 at 5:14

GoogleCodeExporter commented 9 years ago 
There is another issue number for this same problem:
http://code.google.com/p/google-ajax-apis/issues/detail?id=24

Original comment by stigma...@gmail.com on 17 Nov 2008 at 5:23

GoogleCodeExporter commented 9 years ago 
this feature is absolutly needed !!!!!! 
Most important ! ... would pay for release :-D

Original comment by andreas....@gmail.com on 26 Nov 2008 at 2:24

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
A big mistake that it doesn`t included in API.

Original comment by telesoci...@gmail.com on 2 Dec 2008 at 3:41

GoogleCodeExporter commented 9 years ago 
Is this feature on the Roadmap? If so when we it be released?

Original comment by bart.anr...@gmail.com on 9 Dec 2008 at 10:34

GoogleCodeExporter commented 9 years ago 
Please add this feature ASAP - the API is pretty much useless to me as a UK 
based
company if the only results being shown are targeted to the US!

Original comment by emails%g...@gtempaccount.com on 11 Dec 2008 at 7:21

GoogleCodeExporter commented 9 years ago 
the api is needless without it

Original comment by ciscole...@gmail.com on 29 Dec 2008 at 2:02

GoogleCodeExporter commented 9 years ago 
Issue 24 has been merged into this issue.

Original comment by lisba...@google.com on 6 Jan 2009 at 10:48

GoogleCodeExporter commented 9 years ago 
this feature is required urgently

Original comment by pavanr...@gmail.com on 3 Mar 2009 at 1:07

GoogleCodeExporter commented 9 years ago 
This feature would be very-very important. My clients do not understand why 
regular
google.hu SERP and Search API results are so different. 

I tried to set gl and hl parameters explicitly but did not affect. Then I 
created a
CSE with the appropriate local parameter and added its id via the cx parameter, 
but
it also did not work. I am very sad.

MSN Live and Yahoo search APIs are able to handle local parameters correctly. 
Why
Google Search API do not support local searches?

Otherwise your Search API is great.

Best regards,
--Adam Mezei (Webman)

p.s.: I also added this comment to issue 24.

Original comment by InstantR...@gmail.com on 4 May 2009 at 7:30

GoogleCodeExporter commented 9 years ago 
Please provide this API feature asap.. waiting for a year !!!

Original comment by w3engine...@gmail.com on 7 May 2009 at 1:21

GoogleCodeExporter commented 9 years ago 
Can we please get an ETA for when this issue will be resolved?

Many thanks.

Original comment by paul.bla...@searchlatitude.com on 5 Jun 2009 at 11:44

GoogleCodeExporter commented 9 years ago 
Paul --

RIght now there is no ETA.  I will update this thread if anything changes.

-Ben

Original comment by lisba...@google.com on 7 Jun 2009 at 5:08

GoogleCodeExporter commented 9 years ago 
Hi Ben, Thanks for the quick reply.

Can you let us know if this issue is to be addressed at any point in the future?

Also, am I right in saying that the SOAP API will retire on 31/09/2009?  If so, 
what 
options do we have if we want to perform localised API web searches ouside the 
US?

Thanks again.

-Paul

Original comment by paul.bla...@searchlatitude.com on 8 Jun 2009 at 9:09

GoogleCodeExporter commented 9 years ago 
Hi,

Given that the SOAP API will be cut off on August 31, 2009, I'm wondering when 
will
this issue be addressed?  Is it possible for Google to kindly extend the life 
of the
SOAP API until the AJAX API mimics non-US Google search engines?  I'm thinking 
there
are a lot of people out there with the same problem.

Thanks,
Doug

Original comment by douglas....@gmail.com on 15 Jul 2009 at 3:54

GoogleCodeExporter commented 9 years ago 
Yes please... Otherwise we'd have to circumvent the Google SPAM defence by 
parsing
html output and burning IPs :-)

Thanks
Martin

Original comment by hufflehu...@west.de on 16 Jul 2009 at 2:40

GoogleCodeExporter commented 9 years ago 
I think this issue should be raised from medium priority to high as without this
feature the rest of the world will not be able to do localized searches via the 
AJAX
API... 

Please end this discrimination against all those would do not live in the U.S 
and
implement this feature! How hard can it be?? At the very least please give us 
an ETA!

Original comment by frank.pr...@gmail.com on 23 Jul 2009 at 12:17

GoogleCodeExporter commented 9 years ago 
This issues effectively makes the search API unusable for the rest of the world.

Original comment by stigmann...@gmail.com on 27 Jul 2009 at 7:29

GoogleCodeExporter commented 9 years ago 
Please make this feature as it is very important for us to get localized 
results.

Original comment by puneet.k...@gmail.com on 28 Jul 2009 at 7:26

GoogleCodeExporter commented 9 years ago 
This feature is for my company very important. Please add it as soon as 
possible.

Original comment by fox_uko...@trashmail.net on 5 Aug 2009 at 10:42

GoogleCodeExporter commented 9 years ago 
This really is an important feature which needs to be added.

Original comment by cjh...@gmail.com on 6 Aug 2009 at 11:47

GoogleCodeExporter commented 9 years ago 
Without the ability to restrict search results by country, this API should be 
renamed 
Google.com AJAX Search API.  Please, oh Great Google, communicate to us your 
intentions 
on this issue.  Without this feature, many of us are having to resort to evil 
page 
scraping.  Throw us a bone?

Original comment by bade...@gmail.com on 10 Aug 2009 at 3:01

GoogleCodeExporter commented 9 years ago 
It would be very useful!!!

Original comment by rpra...@gmail.com on 17 Aug 2009 at 7:43

GoogleCodeExporter commented 9 years ago 
The way you could approximate this behavior is by using Web 
Search Specific Arguments and in particular the argument lr? 

I tried this and what I did was to pass this parameter with value "lang_de", 
for German for example,
to the Google Search engine like this: 

http://ajax.googleapis.com/ajax/services/search/web?v=1.0&lr=lang_de&... 

what I get is a list of results that make reference to pages written 
in that language. Of course this not the same but it is something that for 
certain applications may partially 
solve the problem.

I would prefer to have access to local search. I hope the next version of the 
API includes this feature

Original comment by gta...@gmail.com on 19 Aug 2009 at 4:31

GoogleCodeExporter commented 9 years ago 
@gtagni,  I agree, the the current api allows the results to be restricted by
language--but I think many are measuring the usefulness of an API by comparing 
it to
the results returned by an actual human search.  After all, restricting the 
results
to the German language (spoken by people in more than 4 countries, not 
including the
older special interest groups of South America) still appears to be returning 
data
from North American data centers. In this regard, it seems that at this time 
the API
is a sort of toy to be played with, but not taken seriously.  Even sadder is 
the lack
of response from the Master.  I guess it is time to see how many squeaky geeks 
it
take to finally get the Google grease.

Original comment by bade...@gmail.com on 19 Aug 2009 at 8:31

GoogleCodeExporter commented 9 years ago 
This is forcing people to break TOS and screen scrape in a human way!

Why can we not use the same gl param that we can add to the real Google 
searches!!
We all need .co.uk/other regional variants.

Original comment by ollie.camp on 10 Sep 2009 at 9:53

GoogleCodeExporter commented 9 years ago 
Issue 308 has been merged into this issue.

Original comment by jrgeer...@gmail.com on 11 Sep 2009 at 2:13

GoogleCodeExporter commented 9 years ago 
Guys this has to be a huge feature request.
The search results from the Google regional engines vary greatly from 
www.google.com.
I'm surprised this was not a feature out of the box for this API?

Original comment by jusm...@gmail.com on 11 Sep 2009 at 7:53

GoogleCodeExporter commented 9 years ago 
Please implement this fix as soon as possible.
We can't use the search API without being able to search AU region.

Original comment by analytic...@gmail.com on 17 Sep 2009 at 7:43

GoogleCodeExporter commented 9 years ago 
We decided to go with Yahoo's results for this reason. What's preventing Google 
from
releasing it? Without localised results in an international product you can't 
provide
quality. Non-US users expect the localised results.

Original comment by ejj...@gmail.com on 17 Sep 2009 at 8:07

GoogleCodeExporter commented 9 years ago 
We decided to go with Yandex resuts for this reason.

Original comment by supp...@i.ua on 17 Sep 2009 at 8:10

GoogleCodeExporter commented 9 years ago 
Do we have any idea on whether this will be implemented, and if so when? It 
really is
a deal breaker.

Original comment by app...@gmail.com on 17 Sep 2009 at 5:09

GoogleCodeExporter commented 9 years ago 
Ending the SOAP API has caused me big problems because the AJAX just doesn't 
have the
same functionality if it returns only google.com results

Original comment by sebsw...@gmail.com on 22 Sep 2009 at 3:36

GoogleCodeExporter commented 9 years ago 
The SOAP API is still active, they just aren't issuing anymore SOAP API keys, 
so if
you already have that working for you, then it should continue to be applicable.

Original comment by mattfoster01@gmail.com on 22 Sep 2009 at 8:08

GoogleCodeExporter commented 9 years ago 
Actually, the SOAP API was officially shut off 7 Sept 2009, I believe. At any 
rate,
it's dead now.

Original comment by jrgeer...@gmail.com on 22 Sep 2009 at 8:11

GoogleCodeExporter commented 9 years ago 
Internet is a world wide concern, so why not open the API accordingly ?  I'm in
Canada and most of my client are in europe but the API is totally useless for 
them.

Original comment by martial-...@isavaria.com on 23 Sep 2009 at 4:41

GoogleCodeExporter commented 9 years ago 
needed badly

Original comment by ciscole...@gmail.com on 25 Sep 2009 at 11:01

GoogleCodeExporter commented 9 years ago 
Hi all, we've just announced that it is now possible to request web search 
results in
the country of your choice. For more details and examples see our blog post:

http://googleajaxsearchapi.blogspot.com/2009/10/web-search-in-your-country.html

Happy coding!

Original comment by jscud.w...@gmail.com on 12 Oct 2009 at 6:37

GoogleCodeExporter commented 9 years ago 
wow, that´s wonderful news... can anyone verify that the results are remotely 
similar
to local non-API 'human' search?

Original comment by bade...@gmail.com on 13 Oct 2009 at 10:10

GoogleCodeExporter commented 9 years ago 
I'm having some trouble getting results that resemble google.co.uk's 'pages 
from the
UK' through the REST interface - I've tried gl=en, gl=gb and gl=uk, each giving
different results and none of them anything like the results given by the 
non-API UK
search.  It also does not give any indication that the language code is 
invalid, even
when entering a bunch of random characters, and looks like it just falls back 
to the
global search.

Examples:
http://ajax.googleapis.com/ajax/services/search/web?v=1.0&q=Earth%20Day
http://ajax.googleapis.com/ajax/services/search/web?v=1.0&q=Earth%20Day&gl=gb
http://ajax.googleapis.com/ajax/services/search/web?v=1.0&q=Earth%20Day&gl=sd8y8
3f

Strangely, the 'flowers' example from the API blog above appears to work (with 
gl=gb)
- the oddity there is that the non-API search returns the UK results even if the
'pages from the UK' radio button is not selected.

Original comment by cro...@gmail.com on 16 Oct 2009 at 9:51

GoogleCodeExporter commented 9 years ago 
This parameter works for web search, but not for local search.

ie, http://ajax.googleapis.com/ajax/services/search/web but not 
http://ajax.googleapis.com/ajax/services/search/local

Is it likely to be implemented for local search?

Original comment by xurizae...@gmail.com on 2 Mar 2010 at 11:57