Google’s google.com/goto Links Are Live: What the Change Means for Your Rankings and Your Data

Google just made a quiet change to the plumbing of its search results, and it has the SEO world talking. If you clicked a Google result this week and glanced at the address bar, you may have seen something new: instead of jumping straight to the website, your browser passed through a google.com/goto link first, then landed on the page.

It sounds small. It is not. This change touches how ranking tools read Google, how AI companies scrape it, and possibly how your analytics counts organic traffic. Here is what happened, what is confirmed, what is still just a theory, and what you should actually do about it.

What changed?

For most of Google’s history, the link behind a search result carried the real destination address. You could hover over a result, see the website’s URL, and any tool reading the page could pull that address without ever contacting the site.

That is what changed. Google is now rewriting many of those result links into a passthrough format that looks like google.com/goto?url=[encoded destination]. When you click, Google’s server receives the request, decodes it, and redirects you to the real page. For a normal person searching, nothing looks different. The page still loads. The site name and address still show in the results. The only visible tell is when you hover over or copy a link and see google.com/goto instead of the actual domain.

Under the hood, the redirect is handled server side and returns a 302 status, which is a temporary redirect. That detail matters, because a 302 tells crawlers the wrapper is not meant to replace the real address in any index. In other words, this is not Google changing your URLs in the rankings. It is Google changing how the link behaves at the moment of the click.

The timeline: two months of testing, then a fast finish

This did not appear overnight. It rolled out in buckets, which is why some people saw it for weeks while others could not reproduce it at all.

The first public sighting came on June 23, 2026, when Alex Greenland posted on X that result links were being rewritten to the google.com/goto format with an encoded destination. He guessed the motive was to fight AI and SEO scrapers, though that was his read, not anything Google said.

On July 2, 2026, Brodie Clark of SERP Alert documented the same pattern across both ads and organic listings and confirmed the 302 redirect behavior. A day later, Derek Perkins of the rank tracking platform Nozzle noted his team had actually been seeing this kind of server side wrapping for months, mostly in sessions where JavaScript was disabled, which is exactly the environment scraper tools tend to run in.

Then came the confusing part. On July 8, 2026, Barry Schwartz of Search Engine Roundtable reported the behavior but said he could only find three people who had seen it and could not reproduce it himself. That gap between the people seeing it and the people who could not is the signature of a limited, bucketed test.

The picture changed on August 26, 2026. Perkins published a chart covering roughly four months of testing and reported a sharp jump: “as of this morning, we’re seeing near 100% rollout across several residential ip providers.” The same day, Google confirmed the rollout to Search Engine Roundtable with a carefully worded statement: “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.” Search Engine Land confirmed the same. So this is no longer a rumor. It is happening.

Worth noting where this actually played out. Almost all of it happened on X, not in an official Google channel. Search Engine Roundtable pointed to Derek Perkins’ own X post as the proof of the near total rollout, and Google only confirmed after Barry Schwartz emailed to ask. There is still no Search Central announcement, no help doc, and no Search Console note about it. That detail matters: Google acknowledged this when a reporter pushed, it did not announce it. So expect the specifics to keep coming from practitioners on X before they come from Google.

Why Google is doing this

Google did not spell out the mechanics, but the direction is clear from the design. When the destination is encoded inside a goto link, a tool cannot simply read the results page and grab every URL. To find out where a link actually points, the tool has to follow the redirect, one link at a time.

That is the whole point. As Perkins put it, Google has been “testing anti-bot measures that eliminate all client side links in favor of google.com/goto … server side redirects.” The links “can’t be decoded, so providers will have to follow the redirect links.”

This lands hardest on the companies scraping Google at scale: rank trackers, share of voice dashboards, competitive intelligence platforms, and the AI companies pulling search data to feed their models. It also fits Google’s ongoing legal fight with SerpApi, a scraping service Google sued and has struggled to beat in court. Making the results mechanically harder to parse is a way to fight that battle in the product rather than the courtroom.

The real cost for measurement tools

Here is the part that reframes the whole story. A rank tracker used to read one search results page and pull every ranking position in a single request. With goto links that cannot be decoded, the tool now has to follow each redirect to learn where it goes. By one estimate in the reporting, a single query can balloon into 500 to 1,000 requests instead of one. Perkins put it plainly: each results page carries “hundreds of links to decode.” He also noted that head requests, a lightweight way to check a link without downloading it, are being blocked, which removes the cheap shortcut.

That is a massive jump in cost and complexity. Small scale tests still work. At full scale, following hundreds of links per results page, on every keyword, every day, for every client, gets expensive fast, and Google can throttle or flag that traffic more easily. Expect this to hit the tools you rely on for reporting. Some will adapt, some will get slower, and some will quietly get less accurate. As Barry Schwartz noted, third party tools always adapt eventually. The question is how much it costs them, and whether that cost lands on your subscription.

A side effect worth knowing: searchers lose the URL preview

There is one more change that has nothing to do with analytics, and it affects real people. When a result is wrapped in a goto link, hovering over it no longer shows the destination address. You see an encoded google.com/goto string instead of the actual domain. For years, glancing at the URL before clicking has been a basic way to catch a spoofed or sketchy site. That quiet safety check goes away. It is minor for most searches, but it is exactly the kind of change that can draw attention well beyond the SEO world if the rollout keeps expanding.

Does this hurt your rankings?

If you run a local business and someone forwarded you this news in a panic, take a breath. This does not change where your site ranks. Google announced no ranking algorithm change alongside goto, and the redirect is a temporary 302 that does not replace your real URL in the index. Your customers still see your site name and address in the results, and they still land on your page when they click. From the searcher’s side, nothing is different.

What this changes is how the industry measures Google, not how Google judges your website.

The one thing worth watching: your analytics

There is a legitimate second order risk, and it deserves honesty rather than hype. A redirect hop can strip the signals that arrive with a click, things like the referrer and campaign parameters. Google’s own GA4 documentation lists redirects as a known cause of stripped signals and traffic getting misfiled as “direct / none.”

So the theoretical failure mode is this: if goto altered those referrer signals at scale, GA4 could start undercounting your Google organic traffic while your “direct” traffic quietly inflates. The telltale sign would be Search Console clicks and GA4 organic sessions drifting apart.

To be clear, this is a risk to monitor, not a fire to put out. As of now there is no confirmed widespread evidence that goto is breaking organic attribution in GA4, and Google has not detailed how the redirect handles those signals. The smart move is not to panic, it is to baseline your numbers now so you would actually notice if something shifted.

What to actually do this week

You do not need to change your site. You need to protect your ability to see clearly.

First, baseline your organic versus direct traffic split in GA4 so you have a “before” picture. Second, set up a simple reconciliation check between Search Console clicks and GA4 organic sessions, and watch for the two diverging over the coming weeks. Third, know where GA4’s referral exclusion settings live before you ever need them. Fourth, if you lean on a rank tracker for client reporting, ask your vendor directly how they are handling goto links and whether their data or pricing is affected.

The bigger takeaway is a mindset one. Google is steadily making its results harder to read by machines, and that trend is not reversing. The teams that win are the ones who lean on first party data, on Search Console, on GA4, on their own conversion tracking, instead of depending entirely on third party tools to tell them how they are doing. Own your numbers. That is the real lesson hiding inside a small change to a link.