Google confirmed on Aug 26, 2026 it's rolling out goto redirects on search links. Here's what changes for rank trackers, backlink tools, and analytics.
On August 26, 2026, Google confirmed something SEO practitioners had been watching for two months: search result links are being routed through a google.com/goto passthrough URL before landing on the destination page. A Google spokesperson told Search Engine Land the company has "a long history of deploying technical measures against evolving forms of abuse, and we regularly take steps to protect our services and users." That's the entire official explanation. Everything else about what this does to rank trackers, backlink monitoring tools, and site analytics comes from what practitioners have pieced together since.
How this went from a rumor to a confirmed rollout
The first public sighting traces to June 23, 2026, when Alex Greenland posted on X that Google was rewriting result links to "google•com/goto to fight AI and SEO scrapers," his own guess at the motive, not anything Google had said. Search Engine Roundtable's Barry Schwartz compiled the earliest reports on July 8 and was upfront about how thin they were: three named observers, one unnamed reader, and Schwartz himself couldn't reproduce the pattern in his own searches. "I only spotted three people so far who noticed this and I cannot see it myself, yet," he wrote at the time.
That changed fast. By late August, Derek Perkins of the rank-tracking platform Nozzle told Search Engine Land he was seeing goto links in "nearly 100%" of search results across several residential IP providers. Google's confirmation followed within days.
What the redirect does
Instead of a search result linking straight to a destination page, the link now points to google.com/goto?url=[encoded destination]. Clicking it sends the browser to Google's own endpoint first, which then forwards it to the real page. Greenland described the encoded destination as "a custom base64-like encoding," not something you can read or decode by inspection.
Google hasn't said what problem this solves beyond "evolving forms of abuse," but the timing lines up with an ongoing fight over search-result scraping. Google sued SerpAPI over scraping its results and lost a recent motion in that case. A redirect layer that can't be parsed the same way a plain URL can makes large-scale automated collection of search results measurably harder, whatever else it's also doing.
The direct hit: tools that read search results at scale
This is where the change stops being a curiosity and starts being an operational problem for a specific category of tool. Rank trackers, backlink discovery platforms, and any service that scrapes Google's result pages to see what's ranking where has historically pulled destination URLs straight out of the page markup. With links now wrapped in an encoded passthrough, that no longer works. Techgenyz's coverage of the rollout is direct about the consequence: these tools now have to follow each redirect individually to find out where it leads, rather than reading the destination off the page in bulk. That makes large-scale collection slower and more resource-intensive, and Search Engine Roundtable has reported that Ahrefs' own systems are already picking up and flagging the wrapped URL pattern in their data.
If you run or rely on a backlink monitoring tool, this is the part worth asking your vendor about directly: do they unwrap the goto redirect automatically, or are wrapped URLs showing up unresolved in your exports and reports.
The quieter risk: what it could do to your own analytics
There's a second-order question nobody has a confirmed answer to yet: what happens to organic-traffic attribution when a redirect hop sits between the search result and your site. Google's own Analytics documentation names redirects as a known cause of stripped tracking signals, sessions that should register as google / organic can fall back to (direct) / (none) when the referrer or campaign parameters don't survive the hop. Whether the goto redirect strips those signals in practice hasn't been published by anyone outside Google, and it's entirely possible it passes a clean referrer through without issue. But if you've noticed organic traffic looking soft in Google Analytics while Search Console still shows steady clicks, a widening gap between those two reports is the signal to watch for, not a ranking problem to chase.
There's a smaller, more certain side effect too: hovering over a search result no longer shows the real destination URL, just the encoded google.com/goto address. That's a minor loss for anyone who used to preview a link before clicking to check it wasn't a phishing page.
What to check this week
Ask whatever backlink or rank-tracking tool you use whether they've adapted to the redirect, specifically whether they resolve goto links automatically or leave them encoded in your data. Separately, pull your Google Analytics organic sessions against Search Console clicks for the same date range and see if they're still moving together. That comparison costs a few minutes and gives you a real baseline instead of a guess, in case the gap between the two starts to widen later.
This isn't the first time a Google-side change has made backlink or traffic numbers look wrong without anything on your site changing. Google Search Console's links report has already thrown a similar curveball this year, a reporting bug that made real backlinks vanish and phantom ones appear with no underlying cause on the publisher's end. And Google's own crawl budget documentation rewrite is part of the same pattern: Google adjusting the infrastructure between its search results and the rest of the web, with third-party tools left to reverse-engineer what changed and why.
