Google goto redirects search results are a new redirect hop Google confirmed on August 26, 2026, with some Search result links using google.com/goto before sending users to the destination page.
Search Engine Land reported on August 26, 2026 that Google confirmed it was rolling out goto URL parameter redirects in search-result links, and quoted Google saying, "We have a long history of deploying technical measures against evolving forms of abuse, and we regularly take steps to protect our services and users." Serpstat said Google confirmed the same rollout on August 26 and described the format as an intermediate google.com/goto URL appearing where a direct page URL would usually sit.
How Google goto redirects search results
The change works by inserting a Google-owned redirect hop between the search results page and the listed page, so a parser looking only at the visible result URL may see google.com/goto instead of the publisher or brand domain. Search Engine Land described the change as adding a redirect hop to google.com/goto, and Serpstat described Search results sometimes using an intermediate google.com/goto URL instead of a direct link to a page.
A rank tracker that records the href value from Google Search can misread a result when the href is a google.com/goto URL. The tracker has to resolve the redirect and store the final destination URL, then match that destination against the ranking page it expected. If the system does not follow the hop, reports can show Google URLs, missing URLs, duplicated results or changed landing pages even when the visible ranking has not changed.
Why Google says it changed links
Google has framed the change as protection against abuse, not as a ranking update or a publisher-facing feature. Search Engine Land's quoted Google statement did not name rank trackers, AI agents, SEO tools, advertisers or publishers, and it did not specify which abuse patterns the /goto rollout targets.
Search Engine Journal connected the timing to a wider fight over SERP scraping and AI agent traffic, but that part of the explanation is analysis rather than a Google confirmation. The publication cited Cloudflare's view of traffic growth and quoted Cloudflare saying, "At the end of 2024, Cloudflare handled an average of 63 million HTTP requests a second. Today, it's almost doubled to 115 million, with peaks above 150 million. Over the past year, daily requests from AI agents on our network grew by more than 1,700%. This year, for the first time, more than half of Internet traffic wasn't human."
The evidence is thinner on scale and intent than it is on the existence of the change. Serpstat said SERPs containing at least one /goto link rose from 5.41% in the first half of August 2026 to a peak of 5.95% on August 24, then became widespread from August 26. Search Engine Land reported Google's confirmation on August 26, but Google has not published a rollout map, a percentage of affected searches, or a statement that /goto targets any named rank tracking provider.
What to check in rank tracking
Rank tracking teams should test whether their collection stack stores the final destination URL after the google.com/goto hop, not only the Google URL found in the result HTML. Serpstat said its own reports continued updating as usual after the August 26 rollout, which shows the change does not automatically break every provider, but it does create a concrete validation point for in-house crawlers and vendor audits.
| Check | Where to look | Failure to flag |
|---|---|---|
| Final URL resolution | Rank tracker export and raw crawl logs | google.com/goto stored as the ranking URL |
| Landing page match | Tracked keyword to URL mapping | Expected page replaced by an unresolved redirect |
| SERP feature capture | Daily SERP snapshots | AI Overview or citation block missing from the record |
| Vendor handling | Tool change logs and support tickets | No written answer on /goto redirect handling |
The practical audit is simple: run a controlled set of branded and non-branded keywords, save the raw result link, follow the redirect, and compare the final URL with the canonical page you expected to rank. If the export contains google.com/goto in place of the destination domain, your visibility reporting is measuring Google's redirect layer rather than your ranking page.
What changes for AI search visibility
The /goto rollout matters beyond rank tracking because Google Search measurement is already getting harder on branded queries with AI Overviews. Ahrefs Blog reported that AI Overviews appeared in 82.91% of U.S. desktop branded-keyword results on September 29, 2026, based on 232.8 million U.S. desktop Google search-result crawls from July to September. Semrush Blog reported DemandSphere data showing AI Overviews at 82.06% of branded queries on September 29 across all markets and devices, while noting that DemandSphere had not disclosed how many keywords it tracks.
The inference for search teams is that a single blue-link rank is now a weaker proxy for branded visibility when Google may show an AI Overview and may route result clicks through /goto. Ahrefs said branded AI Overviews can give third-party sources such as Wikipedia, YouTube and LinkedIn more influence over how a brand appears in Search. Semrush Blog also reported a limit in the DemandSphere data: it measured whether an AI Overview appeared for a branded search, not whether the brand appeared or was cited inside the generated answer.
What happens next
The next trigger to watch is whether Google expands /goto coverage beyond the August 26 rollout pattern while branded AI Overview rates stay above the September 29 levels reported by Ahrefs and Semrush Blog. Search teams should treat the next vendor report or internal crawler anomaly as a data-quality event first: check final URL resolution, AI Overview capture and cited-source extraction before calling it a ranking loss.