[Google Search API] /goto links returned in organic_results->link
major- Started
- Oct 30, 6:39 AM EDT
- Resolved
- Nov 2, 8:32 AM EST
- Duration
- 74h 53m
SerpApi's updates (4)
- investigating · Oct 30, 6:39 AM EDT
We're currently experiencing an issue with our Google Search API, which is returning /goto links for organic results instead of direct links. Our engineering team is investigating it. https://github.com/serpapi/public-roadmap/issues/4315 Thanks for your patience in the meantime.
- identified · Oct 31, 2:23 PM EDT
We have released a fix that restores direct links for the top three results in our Google Search API. Results beyond the top three may still return `/goto` links. Our engineering team is continuing work to restore direct links for all organic results. Thank you for your patience. We’ll share further updates as progress is made.
- identified · Nov 2, 6:58 AM EST
We are continuing to work on restoring direct links for all organic results in the Google Search API. Direct links for the top three results remain in place. Results beyond the top three may still return `/goto` links, which are now returned as full `https://www.google.com/goto?...` URLs instead of relative paths. Since our last update, our engineers have tested additional approaches and are now evaluating a possible way to resolve the remaining links. We will share more as soon as we can confirm progress.
- resolved · Nov 2, 8:32 AM EST
We deployed a fix for the issue where /goto links were being served. This is now resolved, and all of your Google API queries should correctly return direct link values. We apologize for the disruption and thank you for your continued patience.
What our checks recorded
We checked SerpApi 576 times from SerpApi's start time to its resolution, once every five minutes. Every one of them reached SerpApi's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 155 ms, against 207 ms over the 24 hours before. SerpApi posted the incident at Oct 30, 6:39 AM EDT.
Updates are SerpApi's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗