Google Confirms google.com/goto Rollout: What It Means for SEO Tools
Google has confirmed it is rolling out google.com/goto passthrough URLs in search results. Here is what the change does and why it matters for SEO tools and rank trackers.
Google confirmed on August 26, 2026 that it is rolling out a new URL format, google.com/goto, as a passthrough redirect inside organic search results. Instead of linking directly to a page, search result links now route through a server-side redirect that cannot be decoded on the client side. Google's stated reason is preventing abuse of its search results, a move widely read as targeting the AI companies and rank-tracking tools that scrape SERPs at scale.
What happened
| Detail | Fact |
|---|---|
| Feature name | google.com/goto passthrough URL |
| Testing started | July 2026 |
| Confirmed rolling out | August 26, 2026 |
| Observed rollout level | Nearly 100% of SERPs across several residential IP providers (Nozzle) |
| Google’s official reason | “Deploying technical measures against evolving forms of abuse” |
Before this change, hovering over a search result showed a direct link to the destination page. Now, that same link points to a google.com/goto URL, which acts as a server-side redirect (meaning the browser must follow the redirect to find out where it leads, rather than reading the destination from the page HTML itself).
Derek Perkins at Nozzle, a rank-tracking platform, reported the change on X. He shared a chart tracking the share of “goto-only” SERPs Nozzle fetched over roughly four months of testing, showing a sharp spike consistent with a near-full rollout.
Why scraping Google just got a lot harder
Perkins explained the core problem for anyone pulling SERP data programmatically: the goto links cannot be decoded without actually following the redirect. That means scrapers can no longer read destination URLs from the raw HTML. They have to fire real HTTP requests for every link on every results page.
A typical SERP has around ten organic results plus additional features, so each page fetch could require hundreds of follow-on requests to recover the underlying URLs. Google can throttle or block those redirect requests independently, giving it a new lever to limit automated access without affecting ordinary users at all.
The move fits a broader pattern. Google has long used similar techniques, such as the older /url?q= redirect parameter, but the goto format appears harder to bypass because it is purely server-side with no decodable destination in the page source.
What does this mean for SEO professionals?
For most site owners and in-house SEO teams, nothing changes day to day. Your rankings are unaffected. Your clicks still arrive. Your Google Search Console data is still accurate.
The impact lands on the tools that power rank tracking, competitor research, and SERP analysis. Platforms that rely on scraping Google will face higher infrastructure costs and a real risk of being blocked when following hundreds of redirect chains per crawl. Some may degrade in accuracy or speed. Others may pass those costs along through pricing changes.
If your agency or tech stack depends on third-party SERP data, now is a good time to ask your provider how they are handling the goto redirect and whether their data quality has changed. Our team tracks these shifts closely as part of our SEO work for clients, and we have already seen inconsistencies in rank-tracking exports since the rollout began.
Our take
Google’s statement (“we regularly take steps to protect our services and users”) is careful not to name AI companies specifically, but the timing is hard to ignore. The AI search and data-licensing wars have made Google’s index more valuable and more contested than ever. This is a technical enforcement move dressed up in policy language.
For legitimate SEO practitioners, the practical worry is tool reliability. If your rank tracker relies on a scraping pipeline, its data may already be drifting. Cross-check with Search Console as a source of truth while the dust settles.
We covered a related trend earlier when Google quietly reduced PDF appearances in search results with no formal announcement. The goto rollout follows the same playbook: test quietly, confirm only after it is essentially done.
What to do about it
- Audit your rank-tracking tool’s data for the past four months and compare fluctuations against Search Console impressions and clicks.
- Ask your SERP data provider directly whether their pipeline follows goto redirects and what their current success rate is.
- Treat Search Console as your primary ranking data source for now, since it comes directly from Google and is unaffected by this change.
- If you rely on competitor SERP analysis tools, validate a sample of results manually to check for accuracy gaps.
The bottom line: your SEO performance is not affected, but the tools you use to measure it may be.
Frequently asked questions
What is the google.com/goto URL in search results?
It is a server-side passthrough redirect Google now places on organic search result links. Instead of linking directly to a destination page, the link routes through google.com/goto, which redirects the browser to the actual site. Ordinary users are unaffected; only automated scrapers struggle with it because the destination URL cannot be read from the page HTML.
Why is Google using goto links in search results?
Google confirmed on August 26, 2026 that the change is part of its ongoing measures against abuse of its services. The move is widely interpreted as targeting AI companies and third-party tools that scrape search results at scale.
Does the google.com/goto change affect my website's rankings?
No. The change affects how links appear in the results page HTML, not how Google ranks pages. Your rankings, click-through rates, and Search Console data are unaffected.
How does google.com/goto affect SEO rank tracking tools?
Tools that scrape Google SERPs can no longer read destination URLs from the raw page source. They must follow each redirect individually, which increases infrastructure load and gives Google a way to throttle or block automated requests. Some tools may show reduced accuracy or speed as a result.
