Google Maps incorrectly scraping results with correct `ll` parameter
complete
Illia Zub
marked this post as
complete
The fix was deployed on Dec 4, 2021. We forgot to update this forum thread.
The request is retried on the SerpApi side if the country code of request parameters differs from the country code in the results. It doesn't impact how much searches are charged. You pay for successful searches only, not for the number of requests under the SerpApi hood.
Justin O'Hara
marked this post as
in progress
This is still in progress.
This post was marked as
complete
Illia Zub
marked this post as
in progress
Max Allen
Hey Justin O'Hara -- I noticed this recently too. Has there been any progress toward a fix for this? Seems pretty core to making the API work and be valuable as a service
Justin O'Hara
Max Allen: Hi, Our engineers dug into this issue a little more.
This is a hybrid of weird behaviors. Obviously this is a weird behavior on Google Map's side because they are retrieving results from the neighborhood of "NoHo" in NYC for the specified Copenhagen
ll
. And then there is also our proxies that need to be taken into effect when looking at this issue as well. I will see if there's an implementation in the works.
Max Allen
Justin O'Hara: Thanks Justin! Yeah it seems Google Maps is preferring the IP Geo location for "near me" over the explicit query path / param. The general Google API doesn't seem to do this when you pass in a UULE param... so I'm not sure if there's a similar thing we could do for Google Maps API as well. Thanks for digging on this!
Justin O'Hara
marked this post as
under review