On-Page.ai Editorial · Updated August 28, 2026 · News Analysis

google.com/goto Is Live: What the Black-Box SERP Breaks for Rank Trackers, SERP APIs and Your Attribution

Google confirmed on August 26 that passthrough /goto URLs now wrap nearly every result link, after four months of bucketed testing. Rank trackers now need 500 to 1,000 requests to resolve a single keyword’s results. Here is what is confirmed broken, what is only feared, and the baselines to set this week.

Google has spent two years closing the public SERP as a data source. On August 26, 2026, it confirmed the biggest step yet: result links are now rewritten as google.com/goto?url=[opaque token] passthroughs before a click reaches your page. A Google spokesperson told Search Engine Roundtable and Search Engine Land: “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.”

The wording is careful. The engineering is not ambiguous. Derek Perkins, founder of the rank-tracking company Nozzle, measured the change at “nearly a 100% rollout across several residential IP providers,” after roughly four months of intermittent testing. And this is not a change to your rankings. It is a change to who can read the SERP at all, and at what cost. That hits rank trackers, SERP APIs, in-house scripts, and, in a mode nobody has confirmed yet but Google’s own documentation makes plausible, your GA4 attribution.

What actually changed in the result link

For most of Google Search’s history, the anchor behind an organic listing carried the destination address. Any tool that fetched the results page could parse that address without ever contacting your site. That assumption underpins every rank tracker, share-of-voice dashboard, and SERP API in the industry. The rollout replaces the address with an encoded token that cannot be decoded locally. The only way to learn where a result points is to request the /goto URL and follow the 302 redirect.

We ran our own check on August 28. A logged-out Google search fetched from a datacenter IP through our crawler returned result links in the form https://www.google.com/goto?url=CAES…, so the wrapper is being served to datacenter addresses as well as the residential providers Nozzle measured. When we requested one of those /goto URLs, it resolved to the correct destination. Single resolutions work if you are not being throttled. The breakage lives at scale, and it arrived in stages.

The math nobody else ran: one tracked keyword now costs 500 to 1,000 requests

The /goto rollout is the second step in a two-step repricing of SERP data. Step one was the deprecation of the num=100 parameter in September 2025, which cut the results a single request could return from about 100 to about 10. Step two is what happened this week: each of those ~10 links per page now needs its own redirect-follow request to resolve. Combining Nozzle’s measured range, reported by PPC Land, with the pre-existing pagination reality gives this progression for tracking one keyword to position 100:

“The goto links can’t be decoded, so providers will have to follow the redirect links,” Perkins told Search Engine Roundtable. “While that works in small scale tests, Google seems likely to make that tough, since each SERP will have hundreds of links to decode.” PPC Land adds that HEAD requests, the cheap way to resolve a redirect without downloading the target page, are refused, which forces full GET requests on the target or the redirect hop.

What breaks, by tool category

Rank trackers

Any tracker that parses hrefs from fetched SERPs loses its URL source of truth. The symptoms are already documented: Places Scout ranking reports began showing the impact in July per a comment on Schwartz’s first article, and Serpdino described a subtler failure, verification interstitials returning HTTP 200 with a correct page title but an empty results container, which a parser can misread as “no rankings.” One scraping operator on r/SEO reported blocks starting within hours of the confirmation, at “a ~60% block rate” on standard SERP pages. Rankings did not move; the measurement layer did.

SERP APIs

The API providers are adapting at different speeds, and the gaps are informative. DataForSEO published its numbers on August 27: it resolves organic /goto URLs for 99.99% of returned SERPs, but the remaining unresolved links cluster in the newest SERP features.

SerpApi, the company Google sued over scraping in December 2025 and then lost to in court on July 20, 2026, appeared to have a workaround within a day: one Redditor posted a test showing SerpApi returning direct links again. Expect that cat-and-mouse dynamic to define the category for the rest of the year, with another hearing in the case scheduled for late September per PPC Land.

In-house scripts and AI scrapers

The quiet casualties are internal: ranking sheets, Looker Studio connectors, and competitive scripts that marketing teams maintain themselves, all of which read hrefs and have nobody paid to keep them alive. AI companies that scrape SERPs at scale are the other intended target, per the anti-abuse framing. As Crawl Vision put it, the right frame for website owners is “keep an eye on your tools, not your rankings.”

Your attribution: what is real and what is only feared

This is where the coverage has been sloppiest, so the honest split matters. Nobody has reported confirmed organic undercounting in GA4 as of this writing. The mechanism, however, is real and documented by Google itself: GA4’s documentation lists redirects as a cause of stripped referrer, campaign, and click-ID signals, with sessions falling into (direct) / (none), as Digital Applied laid out in its July analysis. Several mitigating details keep this in the “watch” column for now:

The failure mode that would actually hurt you is silent: GA4 undercounting google / organic while (direct) / (none) inflates, with no alert fired. The telltale is divergence between Search Console clicks and GA4 organic sessions. Set the baseline before you need it:

• Record this week’s Search-Console-clicks-to-GA4-organic-sessions ratio as a dated baseline, plus your organic-to-direct split.
• Reconcile GSC against GA4 weekly for the next month. If GSC clicks hold while GA4 organic drops, suspect the redirect hop, not your content.
• Check that no new referral sources of the form google.com/goto are appearing in your reports, and add them to GA4’s referral exclusions if they fragment the organic channel.
• Ask every vendor three questions: do you resolve /goto URLs today, what is your unresolved rate for AI Overviews and local packs, and will pricing or refresh frequency change.
• Hold off on reacting to any rank-tracker alert this week until the tool confirms its parser is /goto-aware.

Why now: the lawsuit Google lost became the infrastructure Google shipped

The timing is the part of this story that explains the motive. Google filed its scraping suit against SerpApi in December 2025. On July 20, 2026, the U.S. District Court for the Northern District of California granted SerpApi’s motion to dismiss. Schwartz was direct about the connection: the rollout is “likely to try to make it more difficult for SerpApi, who Google sued and is struggling to beat in court, from scraping its search results.” What Google could not win as a legal argument it shipped as a 302 redirect, five weeks later, with a spokesperson statement about “evolving forms of abuse” that names no target.

Read as a sequence, num=100 in September 2025 and /goto in August 2026 form one policy: the SERP is no longer a public dataset. It is a rendered experience that Google meters. Every business built on reading it cheaply, trackers, APIs, in-house scripts, AI engines, now pays in requests, proxy bandwidth, and adaptability. The tools will adapt, as Schwartz notes, because they always have. The price of that adaptation, per the math above, just went up by two to three orders of magnitude, and some of it will land in your subscription.

What to watch next

Three signals will tell you where this stabilizes: whether logged-in users start seeing /goto (early reports show it on logged-out searches but not logged-in ones, which would change the calculus for any scraper that authenticates), whether Google begins throttling the redirect resolutions themselves, which is the move Perkins expects, and the late-September hearing in the SerpApi case, where the court may weigh in on whether the technical blockade interacts with the dismissed claims. We will update this analysis as providers publish their unresolved-URL rates.

Sources

1. Barry Schwartz, Google Testing google.com/goto As Tracking URLs In Search Results, Search Engine Roundtable, Jul 8, 2026.
2. Barry Schwartz, Google Search Rolling Out google.com/goto Tracking Parameters (with Google confirmation), Search Engine Roundtable, Aug 26, 2026.
3. Barry Schwartz, Google confirms deploying goto URL redirects to search results links, Search Engine Land, Aug 26, 2026.
4. Luis Rijo, Google forces rank trackers into 500 to 1,000 requests per query, PPC Land, Aug 27, 2026.
5. DataForSEO, Google’s Goto Rollout: We Already Resolve 99.99% of URLs, Aug 27, 2026.
6. Digital Applied Team, Google’s goto Tracking URLs: What Happens to Attribution, Jul 10, 2026.
7. Sagar Rauthan, Google Search google.com/goto URLs: Major SEO Impact, Crawl Vision, Aug 27, 2026.
8. Federal Court Grants SerpApi’s Motion to Dismiss Google’s Lawsuit, Jul 23, 2026; docket at CourtListener, Google LLC v. SerpApi, 4:25-cv-10826.
9. Google Ends &num=100, Logical Position, Sep 16, 2025.
10. Practitioner discussion, r/SEO, Aug 27, 2026.
11. On-Page.ai firsthand test, Aug 28, 2026: logged-out SERP fetched from a datacenter IP served google.com/goto links; one /goto URL followed to the correct destination; direct /search fetch returned Google’s anti-bot interstitial.