Build1 publisher2 min readPublished
Google now routes US organic Search clicks through a google.com/goto redirect
Google now wraps organic Search result links in a google.com/goto redirect, a rollout reported near-complete in the US by late August 2026. Rank trackers, SERP APIs and analytics checks now have an extra hop to resolve before they can report which page a searcher reached.
The Engineer · Build desk
What happened
- A clicked result can land first on a Google goto URL that encodes the destination, and that URL then redirects the visitor to the page.
- Search Engine Roundtable reported that Google characterized the wrapper as a long-standing anti-abuse measure meant to help protect users.
- The reporting does not present the change as a ranking update; the wrapper alters the click path, not the relevance, quality or authority signals that order results.
- Behavior outside the United States has not been confirmed, and regional result pages may not all handle the wrapper the same way.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- cost Teams that set content and marketing spend from organic reports could cut budget for pages whose visibility only looks lower because a tool logged the wrapper.
- constraint Scripts and dashboards that expect the clicked URL to equal the landing URL exactly will raise false discrepancies until both sides are compared after the redirect resolves.
- decision Buying or renewing a rank tracker or SERP API now means confirming the provider follows goto links and returns the resolved final URL.
For tooling, the change is in the link itself. A dev.to write-up on the rollout says that before it, a tool inspecting an organic result could generally expect to find the destination URL there. Now it may find a Google-owned redirect URL instead [6]. A browser follows the hop and still reaches the page [7]. Crawlers, rank trackers, SERP APIs and analytics validation jobs each resolve that path in their own way, and they may not agree [7].
A tracker that stores the raw link can report Google's wrapper as the ranking URL for a query [9]. On that report, Google outranks you for every keyword you track. Join those rows to landing-page data on URL and the affected queries find no match.
The goto URL carries the destination [4], so a tool can get it back in two ways. It can follow the redirect. That costs one more request per result, and it assumes Google answers an automated client the same way it answers a browser. Or it can decode the destination from the goto URL. Decoding saves the request. It also ties the tool to an encoding that Google controls and can change. For a tracker that runs on a schedule, I'd follow the redirect and store the decoded value beside it, flagging any row where the two differ.
Search Console is the steadiest reference for reconciliation. Its documentation says performance data is grouped by the final URL after redirects [8]. That means it should key clicks on the destination whatever the wrapper does. The dev.to write-up suggests a baseline: record a small set of representative queries and destination pages, then compare browser tests, Search Console, GA4 and any third-party SEO platform [14]. Where they differ, it says the next question is whether the platform resolved the final URL correctly, not whether the ranking changed [14].
The case for re-checking is precautionary. The write-up lists GA4 source, medium and landing-page attribution as things to test against a sample of organic visits [13]. It does not report a property where any of them moved, and it says site owners need not assume their data is broken [17]. It also recommends recording the test date and market with each discrepancy [16].
What to watch
- Whether Google extends the goto wrapper beyond the United States, and whether regional result pages resolve it the same way.
- Rank-tracking and SERP API providers stating whether their systems follow goto links and return the final URL.
- A documented GA4 property showing shifted organic source, medium or landing-page data after the wrapper appeared.