serpapi
[Google Maps API] Valid searches not returning results
Empty result with error message
I searched with query "Takeaway under $20" using the [email protected],145.1475484164928,16z I get empty results
WhenI do the same in google map I get good results .
Public links: Serpapi: https://serpapi.com/playground?engine=google_maps&q=takeaway+under+%2420&ll=%40-37.86380642351989%2C145.1475484164928%2C16z&hl=en&type=search&newPara=gl+gl=au
Google: https://www.google.com/maps/search/takeaway+under+$20/@-37.8660416,145.1486213,15z/data=!3m1!4b1?entry=ttu&g_ep=EgoyMDI1MDQyMS4wIKXMDSoASAFQAw%3D%3D
Less gps resolution: Serpapi: https://serpapi.com/playground?engine=google_maps&q=takeaway+under+%2420&ll=%40-37.8660416%2C145.1486213%2C15z&hl=en&type=search&newPara=gl+gl=au Google: https://serpapi.com/playground?engine=google_maps&q=takeaway+under+%2420&ll=%40-37.8660416%2C145.1486213%2C15z&hl=en&type=search&newPara=gl+gl=au
Thank you for reporting the issue @arunzone. Based on your screenshots, I can see the results were not returned. However, I ran your query now, and it looks to be working:
16z:
15z:
I'm not quite sure what might have been causing the query to not return any results, but can you double-check if the results are good on your end as well? I'll keep the thread open for now, but if it's no longer reproducible, we'll close it.
Every couple of searches or so I'm getting empty results.
I've noticed this just today. Does this have anything to do with he new location parameter?
We also have one report from a user, which I thought was unrelated initially.
Inspect from customer | Intercom
A high-volume customer reported this. It happened since November 5:
@ocvit can you please take a look in case this is related to our recent update? Thanks. LMK if I should create a separate report from the original thread. Ref: https://github.com/serpapi/public-roadmap/issues/73
@hilmanski it's not related. I've tested with before/after commits and they both have ~15% fail rate. https://github.com/serpapi/public-roadmap/issues/73 implements alternative way of setting ll parameter with no changes in data sent to Google Maps.
@hilmanski paginated results are not affected by the issue, so setting start=0 to get the first page is an effective workaround.
@hilmanski, I can also confirm that it is not related because I tested production before the PR deployment.
Another example of this from the same customer Hilman mentioned:
Inspect - returned empty Playground - working
Potentially another example which is for place results also affected by this issue. Not sure if it's the same root cause.
Inspect - empty results Inspect - working Intercom
User/Customer reports:
Intercom Intercom - Maps Place API Inspect Intercom - Maps Place Inspect Front
Folks - all of our Google Maps searches are now failing. Do you have an ETA on the fix?
@colethienes Hi Cole, a fix has been merged and is now live. Your results should now be back to normal.
I'm reopening that since the customer reported they are still facing this issue (although less frequently), and I've been able to recreate it.
Intercom Inspect - successful | Inspect - failed Inspect 1 - customer | Inspect 2 - customer
Another customer still facing this issue, also with decreased frequency.
I checked some recent searches and it appears to be happening for ~1/60 searches.
Here are the current fail numbers per 1k searches:
| query | run 1 | run 2 |
|---|---|---|
| Playground example | 0 |
1 |
| Aleef Cafe (ref) | 2 |
0 |
| JP query (ref) | 0 |
0 |
It doesn't look like a global problem. I think there is at least one kind of server error response that we don't properly retry that leads to empty search results.
I'm reopening as the customer reported they are not getting any results again.
Inspect 1 | Inspect 2 | Inspect 3 | Inspect 4
@zyc9012 I'm not sure if the original issues mentioned on the thread should also be fixed by our recent update or not.
Tried to replicate the search and still see empty result for this particular search: Inspect
LMK if we should create a separate issue
I'll follow up with the other reports that it should be fixed.
Notes for CS team: I've followed up with all reports after we initially closed it. Still need to confirm the original issue to see if we should create a separate issue and can close this one.
@Gsosa2703 this search was made before the recent fix. The affected query returns correct results now.
We released a series of fixes that improves search results coverage. All the queries that were still affected return correct results now.
@arunzone there can be incompatibilities between specific coords and queries. Your first SerpApi example included coordinates that didn't match the ones from Google URL - @-37.86380642351989,145.1475484164928,16z vs @-37.8660416,145.1486213,15z. If you try Google's ones you'll get the search results:
If you try @-37.86380642351989,145.1475484164928,16z but with slightly different query, e.g. takeaway under $21, you'll also get the results: