Google now routes most search result clicks through a google.com/goto redirect before the visitor lands on your site. For nonprofits, the practical impact on your Google Analytics organic reporting is small so far. The confirmed disruption is to third-party rank-tracking tools, not to your donor and member traffic numbers.
The short version
- Google confirmed on August 26, 2026 that it is wrapping search result links in google.com/goto passthrough URLs, live for nearly all users by late August.
- Google's only stated reason is defending its services against "evolving forms of abuse." The popular anti-scraping explanation is the industry's read, not Google's.
- The confirmed casualty is rank tracking. Ahrefs reported temporary data inconsistency while SE Ranking and Semrush reported no impact on position data.
- No one outside Google has published a header-level test of what referrer survives the hop, so claims that it will wreck your GA4 organic numbers are speculation.
- Search Console measures clicks at Google's side, before the redirect, so it stays reliable and is your best source of truth right now.
What Google actually changed
Google stopped putting your destination URL directly in the search result link and started wrapping it in a redirect. Hover over a result now and you see a google.com/goto address; click it and Google bounces you through its own servers before delivering you to the page. Testing started in July 2026, and by the time Google confirmed the change to Search Engine Roundtable on August 26, it was rolled out to nearly everyone.
Google's statement was deliberately vague: "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." Notice what is not in that sentence. Google did not name scrapers, artificial intelligence (AI) companies, or rank-tracking vendors. The anti-scraping interpretation, tied to Google's litigation against services that scrape its results pages, comes from analysts like Barry Schwartz and Derek Perkins, not from Google. You can read the confirmation and full statement here.
Why the panic is about the wrong thing
The loudest takes claim /goto will quietly reclassify your organic search visitors as direct traffic. That is a mechanical possibility, not an observed fact, and the distinction matters when you are the one explaining a traffic dip to a board.
Here is the mechanical part. Redirects can strip the signals analytics uses to attribute a visit. Google's own GA4 documentation lists redirects as a cause of traffic landing in the (direct) / (none) bucket, because a redirect can drop the campaign parameters attached to a URL. So the fear is not irrational on its face.
Here is the part the panic skips. Nobody outside Google has published a header-level analysis of what referrer a destination site actually receives after the /goto hop. The redirect lives on google.com, so it is entirely plausible that the referrer your site sees is still a google.com address and your organic attribution holds. Until someone tests the live headers, "it will destroy your analytics" is a guess dressed up as a warning.
When I pulled a legal-services nonprofit's GA4 the week after the rollout was confirmed, I compared their August Search Console clicks against their GA4 organic sessions and the ratio held within its normal range. Organic did not collapse into direct. One account is not proof for every site, but it is a lot more than the zero evidence behind the doom posts.
What is genuinely affected: rank tracking
The real, confirmed disruption is to tools that read your ranking positions by scraping the results page. When the destination URL is buried inside a redirect, a tracker can no longer read your ranking straight from the HTML. It has to follow the redirect chain, which multiplies the requests needed for a single check.
The vendors have split. Ahrefs acknowledged temporary data inconsistency while it adapts. SE Ranking and Semrush reported no impact on position data. SerpApi confirmed several products were affected with fixes in progress. The practical takeaway for a nonprofit: if your keyword rankings looked jumpy in late August or early September, the redirect is a likelier cause than a mysterious algorithm hit. Check your tool's status page before you rewrite a page that was ranking fine.
The AI citation wrinkle
There is a quieter side effect worth watching. Generative engines such as ChatGPT and Perplexity that pull results from Google can capture the /goto redirect URL instead of your real address as the citation. That creates an attribution gap: your organization can appear as a cited source in an AI answer while your citation-tracking tool, looking for your real domain, sees nothing.
If you have started measuring Generative Engine Optimization (GEO) or Answer Engine Optimization (AEO) performance, do not read a flat citation report as proof that AI engines are ignoring you. The citation may be landing on a wrapped URL your tool does not recognize yet.
What to actually do this quarter
None of this calls for a code change on your site. It calls for measurement hygiene, and it is quick.
First, set a baseline now. Pull your August Search Console clicks and your GA4 organic sessions and record the ratio between them. That ratio is your early-warning system: if organic sessions fall while direct rises and the ratio breaks, you have something to investigate. If the ratio holds, the redirect is not costing you attribution.
Second, treat the Search Console Performance report as your source of truth for organic clicks this quarter. It counts the click at Google's side, before the redirect, so it is not exposed to any referrer question. Google's own guidance is clear that Search Console and Analytics measure different things and will not match exactly, so watch the trend, not the gap.
Third, before your next board or leadership report, add one sentence noting that Google changed how search links are delivered in late August, so a single month of organic movement should be read with caution. That protects you from over-explaining ordinary noise as a strategy failure.
If you want to go deeper on which reports actually deserve your attention, I wrote a companion piece on the GA4 reports that matter for nonprofits, and on reading Search Console once AI Overviews entered the picture.
What this does not cover
This is a measurement and reporting piece, not a forensic one. I am not giving you a header-level teardown of the redirect, because no credible one exists yet; when someone publishes tested referrer behavior, that changes the analysis. It also does not cover Google Ads, where click tracking runs on its own gclid parameter and is unaffected. It is separate from the AI Overviews opt-out and the Preferred Sources controls, which are different changes. And it is not legal commentary on Google's scraping lawsuits.
FAQ
Does google.com/goto hurt my SEO rankings?
No. The redirect changes how the link is delivered on the results page, not how Google ranks your pages. Your rankings are unaffected. What changes is some third-party tools' ability to read those rankings cleanly.
Will my Google Analytics organic traffic drop because of the redirect?
There is no confirmed evidence that it will. Watch the ratio between your Search Console clicks and your GA4 organic sessions. If organic falls while direct rises with nothing else changing, investigate it, but do not assume /goto is the cause without checking.
Is Search Console data affected by the redirect?
No. Search Console counts the click on your result at Google's side, before the visitor is redirected, so its numbers are not exposed to any referrer change. That is why it is the more trustworthy source right now.
Do I need to change anything on my website?
Nothing structural. This is a change on Google's side, not yours. Your work is measurement hygiene: baselines, ratios, and a note in your reporting, not code.
Why is Google doing this?
Google says only that it protects its services against "evolving forms of abuse." The widely repeated explanation that it targets scrapers and AI data collectors is industry interpretation, not something Google has stated.
Ready to reconcile your numbers?
If your organic numbers looked strange in your last report and you cannot tell whether it was this redirect, an algorithm update, or a tracking gap, I will reconcile your Search Console and GA4 data and tell you which one it was. Book a 20-minute traffic-data read-out and bring your August and September numbers.