Google Now Routes Result Clicks Through google.com/goto: What It Means for Tracking

Have you hovered over a Google result lately and seen a google.com/goto address instead of the page you expected? You are not imagining it. The google goto redirect is real. On 26 August 2026 Google confirmed it now sends clicks on search result links through its own /goto address first. Then it passes the visitor on to the website.

The short answer for most site owners: visitors still arrive. Nothing Google has said points to a change in how organic visits are credited. But there is now an extra hop between the click and your page. So I’d do a quick check that your analytics, logs and campaign tracking still work as before.

What Google Actually Confirmed

The confirmation was short. The SEO press asked about the new links. A Google spokesperson said the company has a long history of using technical measures against changing forms of abuse. The spokesperson added that Google often takes steps to protect its services and users.

That is all of the official position. Here is what that statement does and does not cover:

• Confirmed: Google is rolling out google.com/goto links on search results, and it calls the change an anti-abuse measure.
• Not stated by Google: which kind of abuse it targets, whether the rollout covers every country and result type, or whether anything changes in publishers’ reports.
• Not announced: any Search Central documentation, Search Console change or Google Analytics change linked to the redirect.

SEOs had spotted the format in testing during the summer, before Google confirmed it. People who track results at large scale say it now shows on almost every results page they collect. Many in the industry see it as a move against automated scraping of results pages, because the destination can no longer be read in the page code. Google itself did not name scrapers. So treat that as a guess, not a fact. I think it is a reasonable guess, but it is still a guess.

What the google.com/goto Redirect Is

Until now, the link behind a normal Google organic result pointed straight at the page. Your browser read that address from the page, and a click took you there directly.

Now, the link points to an address on Google’s own domain, in the form https://www.google.com/goto?url=…. The part after url= is a coded token, not a readable web address. When someone clicks, the browser goes to Google first. Google’s server then replies with a redirect to the real page.

What a Click Looks Like Now

1. The searcher clicks a result on google.com.
2. The browser asks Google for google.com/goto?url=….
3. Google’s server replies with an HTTP redirect that names the real page.
4. The browser follows it and loads your page.

For the searcher, this takes a split second and looks the same as before. The visible changes are small. Hovering over a result shows the goto address in the browser’s status bar. And a copied link may be the Google address, not your URL.

Is This New for Google?

Not fully. Google has used its own click-through addresses in different places for years. So sending a click through google.com is not new in itself. What changed is that this coded, server-side version now sits on normal organic result links at large scale.

Does the Google Goto Redirect Affect Referrer Data?

This is the question most site owners care about. Analytics tools use the referrer (the address the visitor came from) to label a visit as organic search.

Google search pages have long sent only the origin, https://www.google.com/, as the referrer, not the full search URL. That is why you never see the search query in your referral data. Modern browsers do the same by default. The strict-origin-when-cross-origin policy sends only the origin on requests between sites, as web.dev explains in its guide to Referer and Referrer-Policy best practices.

The new hop starts and ends on google.com. So the request that finally reaches your site still comes from a Google page. By that logic, you should keep seeing google.com as the referrer. That is exactly what analytics tools use to label organic search. No referrer loss had been confirmed when Google announced the change.

Keep two warnings in mind:

• Referrer behaviour depends on the browser. Privacy-focused browsers and extensions can remove or cut referrers, redirect or not. That was true before the change too.
• “Should” is not “does”. Google has not shared technical details of the redirect. So test it on your own site instead of trusting logic alone. The steps further down show how.

Search Console, GA4 and UTM Tags

Search Console

Search Console counts clicks inside Google’s own systems. Its definition of impressions, position and clicks says a click is any click that sends the user to a page outside Google Search. The click is given to the canonical URL (the main version of the page).

A redirect on Google’s side doesn’t change that rule, and Google has announced no change to Search Console reports. That makes Search Console your control data, and it is the first place I’d look. If its clicks hold steady while organic sessions in your analytics drop, you have a measurement problem. You have not lost search demand.

GA4

GA4 decides where a session came from mainly by the referrer and any campaign tags on the landing URL. If the referrer still says google.com, the session is labelled google / organic as before.

The risk is a visit that loses its referrer. GA4 then has nothing to go on, and it usually files the session under (direct) / (none). That is the pattern to watch for. Organic search sessions fall, direct sessions on your landing pages rise by a similar amount, and Search Console clicks don’t drop.

Maybe you already split out AI referrers, as covered in our guide to tracking visits from ChatGPT, Perplexity and Gemini in GA4. If so, check that those channel rules still match correctly. Custom channel rules all depend on the same referrer data. So any change there would show up across all of them.

UTM Parameters and Click IDs

Most organic results don’t carry UTM tags (tracking labels added to a URL), because Google links to the URL it indexed. Where a URL in Google’s index does include a query string, the redirect points to that full address. So the parameters should arrive whole.

Paid search is the area I’d double-check. Some people reported seeing goto links on ads during testing as well. Google has not said whether ads are included. So check that auto-tagged click IDs (gclid) and any manual UTM tags still reach your landing pages, and that Google Ads conversions still match up.

What You Might See in Server Logs

The redirect happens between the searcher’s browser and Google. Google’s server doesn’t fetch your page for the visitor. So your logs keep recording a normal request from the visitor’s own browser and IP address.

In a typical access log line, these are the fields I look at:

• Requested URL: your landing page, exactly as before. You won’t see /goto in your own logs, because that address lives on Google’s server.
• Referer field: it should still read https://www.google.com/ for organic clicks.
• User agent: the visitor’s normal browser details.

A quick check: filter one day of logs from before late August and one day from after. Compare the share of page requests with a Google referer. If that share falls sharply while total human visits stay level, look into it. Our beginner’s guide to log file analysis for SEO shows how to pull and filter these files.

Third-party SEO tools are one more place the change can show up. Rank trackers and SERP feature trackers read Google’s results pages automatically. Now they have to follow each redirect to learn which site a result belongs to. Watch for odd gaps, results credited to google.com, or sudden swings in SERP feature ownership around late August. If you see these, ask the vendor whether it has adapted before you act on the numbers. It is not the first change to hit these tools. Google’s removal of the num=100 parameter in September 2025 also broke rank tracking for a while. Before that, Google’s JavaScript requirement forced many tools to change how they read results.

Privacy: What Changes for Searchers

Google already knows which result you click. Search Console click counts exist because Google records clicks. So the redirect doesn’t create click tracking that didn’t exist before. It changes how the click passes through Google, not whether Google sees it.

What does change for searchers is what they can see. Before, hovering over a link showed where it led. Now it shows a google.com address with a token you can’t read. So you can’t confirm the destination before you click. The URL and breadcrumb in the result snippet are still there, and they are the best guide to where a result leads.

For site owners, Google passes nothing extra about your visitors to you. The referrer is still the Google origin, without the search query, just as before.

What Site Owners Should Check Now

None of this calls for panic. But I’d do a short, step-by-step check in the days after the rollout. The goal is to confirm three things. Google visits still arrive, they are still labelled as organic, and your paid tracking still works.

1. Click through a result yourself. Search for one of your pages in a private window. Hover to confirm you see a goto link, then click it. In your browser’s developer tools (Network tab), check that the final request to your page shows https://www.google.com/ as the referer.
2. Watch it arrive in GA4. With GA4 DebugView or the real-time report open, check that the test visit is credited to google / organic.
3. Compare Search Console clicks with GA4 organic sessions. Look at the daily trend for the weeks before and after late August. The two never match exactly, but the gap between them should stay about the same.
4. Watch direct traffic on organic landing pages. The warning sign is a rise in (direct) / (none) on pages that usually get search traffic, along with a fall in organic sessions.
5. Check paid tracking. Don’t click your own ads. Instead, ask whoever runs Google Ads to confirm that landing page requests still carry gclid values and that conversion counts look normal.
6. Sample your logs. Compare the share of requests with a Google referer before and after the change.
7. Add a note. Mark 26 August 2026 in your reports, so anyone reading trend lines later knows what happened. GA4 annotations are a simple way to do this.

A Practical Example

Imagine a local plumbing firm that gets around 60 percent of its website visits from Google organic. After the rollout, the owner checks GA4. Organic sessions are steady and direct traffic hasn’t changed. Search Console clicks follow their usual weekly pattern. That is the expected result, and nothing needs doing beyond adding the note.

Now imagine a different picture. GA4 organic sessions fall by a fifth in a week. Direct sessions to the same service pages rise by a similar number. Search Console clicks are flat. That points to referrer loss somewhere along the way, maybe in one browser group or in a consent tool. In that case, I’d break the data down by browser and device before drawing any conclusions.

Does It Affect Rankings or SEO?

Nothing Google said links the redirect to rankings. It changes the link a searcher clicks, not how Google crawls, indexes or ranks your pages. Your canonical tags, internal links and content all work as before.

The real SEO impact is on measurement, especially for teams that rely on third-party rank tracking. If you report on visibility, lean more on your own data from Search Console while the tools catch up. I like a simple dashboard that puts Search Console clicks next to GA4 sessions, like the one in our guide to building a free SEO dashboard in Looker Studio. It makes any gap easy to spot.

It also helps to keep the bigger picture in mind. Search traffic was already harder to read because of AI answers and searches that end without a click. We covered that shift in measuring SEO value in zero-click search. The goto redirect adds one more reason to measure from several sources, not trust one number.

Conclusion

The google goto redirect puts a Google-owned hop between a search result and your site. Google has confirmed the rollout and called it an anti-abuse measure. It has not announced any change to Search Console or to how organic visits are credited.

Your next step is a 15-minute check. Click through one of your own results. Confirm the google.com referrer and the organic label in GA4. Then add a note for 26 August in your reports. If organic and direct traffic start moving in opposite directions while Search Console stays flat, you’ll know exactly where to look.