SEO Data Bench

SEO Data Bench/Guides/google-goto-links-in-serp-api-results

google.com/goto in SERP API results: which routes return it and how to recover the site

Field guidecohort v1US · enrun 2026-09-15includes a Treg route

The same 50 queries through eight Google SERP routes on 2 November 2026: how many organic results came back as a google.com/goto link, which fields still name the site, and what it took to resolve the links.

By Shirley Lou, ResearchPublished 2026-11-02Facts re-checked 2026-11-02Last material change 2026-11-02

Written for people asking: Why is google.com/goto showing up in my DataForSEO results?Which SERP APIs return google.com/goto links instead of the real URL?How do I get the real URL from a google.com/goto link in SERP API data?

On 2 November 2026 DataForSEO returned a google.com/goto link in the URL field on 308 of 416 organic results (74%) and SerpApi on 275 of 430 (64%), for the same 50 queries where both had returned none on 15 and 19 October, and DataForSEO none on 29 October. DataForSEO also set the domain field to google.com on all 308 rows, so grouping by domain credits those positions to Google. Cloro, Serper, AnyAPI, LimaData and ScrapeCreators returned no goto link in their result URL field, and Treg's routed endpoint, served by crawl4ai that day, returned two in 427. The links can be resolved: following them returned a destination on 120 of 120 sampled and on 40 of 40 stored for 14 or 48 days, and Cloro's resolver matched direct following on 40 of 40 at $0.0004 a call. Parsing the site from DataForSEO's breadcrumb or SerpApi's displayed_link worked on 50 and 55 of 60 and failed mostly on Reddit and YouTube rows. A rank tracker on either route should check for the goto form before it matches a domain, then resolve what remains.

The question comes from someone counting goto links in their own DataForSEO data: “0 of 71,531 organic results on Oct 15–21, 2,552 of 4,344 (58.7 %) on Oct 30” (r/TechSEO, seen 1 November 2026). Their problem is working out which site a result belongs to. This page measures the same thing across routes, on a fixed query list with stored results from before the change.

What was run

Cohort v1 is 50 US-English buyer queries for data APIs, frozen on 15 September 2026. On 2 November 2026 each query went once through eight live Google SERP routes, 400 calls through the Treg CLI, with one worker per provider. Serpstat was left out because it answers from a stored index. A row counts as goto when the field a rank tracker reads holds a google.com/goto link. Stored runs of the same queries from 15, 19 and 29 October are the comparison; the 29 October run covers DataForSEO only.

Route Organic results Goto in URL field Share Pages with at least one Settled per call
DataForSEO (url) 416 308 74.0% 48 of 48 $0.002
SerpApi (link) 430 275 64.0% 50 of 50 $0.015
Treg routed, served by crawl4ai (url) 427 2 0.5% 2 of 50 $0.00015
Cloro (link) 438 0 0 0 of 50 $0.002
Serper (link) 486 0 0 0 of 50 $0.001
AnyAPI (link) 440 0 0 0 of 50 $0.0005
LimaData (url) 490 0 0 0 of 49 $0.002
ScrapeCreators (url) 500 0 0 0 of 50 $0.00188

Three things to read alongside the table:

  • The change is recent on these queries. DataForSEO returned 0 goto links in 425 organic results on 15 October, 0 in 406 on 19 October and 0 in 422 on 29 October, so on this list it appeared within the last four days, which fits the poster’s 30 October reading. SerpApi returned 0 in 433 and 0 in 431 on the two October dates it ran, so its start can only be placed after 19 October.
  • It is not confined to low positions. On DataForSEO, 29 of the 48 first-position results were goto links, and 39 of 48 at position two.
  • It goes beyond the organic URL. DataForSEO also returned goto links in 211 sitelink and related links[].url values. SerpApi returned them in 87 AI Overview references and 108 sitelinks. A parser that handles only the organic URL still has these to deal with.

A separate weekly cohort run on this site, about five minutes earlier, read 310 of 416 on DataForSEO and 275 of 430 on SerpApi. The SerpApi figure is not a second measurement: all 50 responses carried the same search IDs as that earlier run, so SerpApi served stored searches. The settlements visible on the ledger for that window were all $0.015, so the cached calls appear to have been billed at the full price.

DataForSEO said on 27 August 2026 that it returned direct URLs for 99.99% of SERPs, and SerpApi’s 7 September changelog said it had resolved the redirect. Both statements matched this site’s October runs. Neither matches 2 November, and this run does not show why.

What it breaks: the domain field

DataForSEO’s domain read google.com on all 308 goto rows. A rank tracker that matches a client’s domain against that field records those rows as absent, and a share-of-voice report credits them to Google. SerpApi has no domain field, so anything parsing a host from link hits the same problem.

Which fields still name the site

Sixty goto rows per route were resolved to their destination, then compared with the fields on the row, matching on the last two labels of the host.

Field Rows where it holds a hostname Named the same site, sample of 60 What it holds when it misses
DataForSEO domain 0 of 308 0 google.com
DataForSEO breadcrumb 266 of 308 50 Text such as “40+ comments · 2 years ago”
DataForSEO website_name 63 of 308 14 A display name such as “Reddit · r/SaaS”
SerpApi displayed_link 238 of 275 55 Text such as “10+ comments”
SerpApi source 53 of 275 11 A display name such as “Medium · smeuseBot”

Every miss in the breadcrumb and displayed_link columns was a platform result: on DataForSEO seven Reddit, two YouTube and one LinkedIn, and on SerpApi two Reddit plus one each for X, YouTube and Medium. The display-name field named the platform on all 15, so a name lookup can catch these, but it gives you “Reddit” and not the thread. A parsed host also gives no path, so it can tell you the site but not the ranking page.

Follow the redirect. Request the link, do not load the destination, and read the Location header. DataForSEO’s google.com/goto form answers with a 301 to www.google.com/goto, then a 302 to the destination; SerpApi’s www form goes straight to the 302. All 120 sampled links returned a destination, at a median of 175 ms and 96 ms.

Stored links still worked. Cloro returns the goto link beside the destination, which allows an age check. Twenty links each from stored responses of 15 September, 19 October and 2 November all resolved, all to the host Cloro had reported. A link stored 48 days ago still works, so old raw data can be repaired. This is 60 links, and there is no published expiry to set against it.

Or call a resolver. Cloro’s resolver, cloro.google.redirect.resolve on the Treg catalog, returned the same URL as direct following on 40 of 40 links, 20 from each route, at a median of about 1.1 seconds. The catalog lists it as free; all 29 settlements readable on the ledger were $0.0004. It is the only endpoint in the catalog offering this job, and it is worth using when you cannot make the requests yourself or they start being refused.

import http.client
from urllib.parse import urlparse, urljoin

def resolve_goto(url, hops=4):
    for _ in range(hops):
        p = urlparse(url)
        c = http.client.HTTPSConnection(p.netloc, timeout=20)
        c.request("GET", f"{p.path}?{p.query}", headers={"User-Agent": "Mozilla/5.0"})
        r = c.getresponse()
        location, status = r.getheader("Location"), r.status
        c.close()
        if status not in (301, 302, 303, 307, 308) or not location:
            return None
        url = urljoin(url, location)
        if not urlparse(url).netloc.endswith("google.com"):
            return url
    return None

Who this fits

  • You run a rank tracker on DataForSEO or SerpApi. Add a check for the goto form before any domain match, and count it per run so the next change shows up as a number. Resolve what is left, or use breadcrumb or displayed_link as a fast first pass and accept that platform rows need more work.
  • You have stored data with goto rows. Resolve it now. The links tested survived seven weeks, with no promise beyond that.
  • You are choosing a route for a new job. Five routes returned destinations directly on this day, from $0.0005 to $0.002 a call. That does not make their lists interchangeable: routes returned different result lists for the same query in September, and that comparison was not repeated here.
  • You use a routed endpoint. Treg’s routed endpoint was served by crawl4ai on this date and by ScrapeCreators on 15 and 19 October, so its output depends on the provider serving it. Log _treg.served_by with each call, and do not assume the 2 in 427 will hold.

What this page cannot tell you

One pass, one day, 50 US-English queries in one niche, and the goto share may well differ on other queries or locations. Why two routes changed and five did not is not visible from the responses. The resolving ran at one request a second from one IP, 220 links followed in all with none refused, which says nothing about thousands an hour. Google’s Terms of Service restrict automated access, and whether following these links in bulk fits your compliance position is your call. The field checks are samples of 60, so read them as rough rates. The Reddit thread could not be fetched directly, so its numbers are quoted as posted and its comments were not reviewed.

Reproduce it

treg auth login
scripts/run-goto-check.py evidence/fixtures/seo-cohort-v1.json evidence/goto-checks/$(date +%F)/raw
scripts/score-goto-check.py summary.json now=evidence/goto-checks/$(date +%F)/raw
scripts/resolve-goto-sample.py evidence/goto-checks/$(date +%F)/raw resolved-summary.json 60
scripts/check-goto-resolver.py evidence/goto-checks/$(date +%F)/raw resolver-summary.json 20

Next step

Questions this page answers

Why is google.com/goto showing up in my DataForSEO results?

Because the url field now carries Google's redirect link on most organic rows. On 2 November 2026 that was 308 of 416 organic results across 48 result pages, at every position from first to ninth, against none of 1,253 on 15, 19 and 29 October. The domain field reads google.com on all 308 of those rows, so a report grouped by domain shows Google in positions it does not hold. DataForSEO said on 27 August 2026 that it returned direct URLs for 99.99% of SERPs; this run does not establish when or why that changed.

Which SERP APIs return google.com/goto links instead of the real URL?

In the main result URL field on 2 November 2026: DataForSEO on 74% of organic results, SerpApi on 64%, Treg's routed endpoint on 2 of 427. Cloro, Serper, AnyAPI, LimaData and ScrapeCreators on none. Cloro does return the goto link, but in a separate redirectLink field beside the destination. This is one day's reading, and the same two routes returned none two weeks earlier, so test your own route rather than relying on the list.

How do I get the real URL from a google.com/goto link in SERP API data?

Request the link without loading the destination and read the Location header. That returned a destination on 120 of 120 links sampled on 2 November 2026 at one request a second, and on 40 of 40 stored for 14 or 48 days. Cloro's redirect resolver, called through Treg, returned the same URL as direct following on 40 of 40 in about 1.1 seconds, listed as free but settling at $0.0004. How either holds up at high volume was not tested.

Relationship: the people who run this site also work on Treg, one of the routes compared on this page. Every Treg figure here is a call we paid for, with the raw response downloadable, and the same fixture is run against the alternatives where their terms allow.


Spotted an error or a changed price? Email corrections@seodatabench.com with the page URL and a source. Corrections are logged on the corrections page.