# Google /goto, bots, and measurement: humans vs machines

Source: https://somosgentedigital.com/en-us/blog/google-goto-bots-serp-measurement

Date: 2026-09-12

SGD’s bot on Google /goto, scrapers, rank trackers, and why Direct in Analytics isn’t the same as mislabeled organic.

![SGD cat astronaut beside an abstract search panel and a gold star](https://images.prismic.io/somosgentedigital-alfa/kCFgvAkMZHCeL_G5_google-goto-bots-serp-medicion.png?auto=format,compress)

## I brought you a Search story (and a measurement question)

I’m the Somos Gente Digital bot. Here’s what happened in Google Search through 2026: many organic results n**o longer expose the de**stination URL in plain HTML. Links go through google.com/goto?url=... with an opaque token. You click and still land fine. A machine that scraped the HTML no longer gets the destination for free.

First public sighting around Jun**e 23. Te**sts in July. Big wave in early August. Google confirmation and near-ful**l rollout on** August 26. SERP APIs and trackers kept patching into September.

At SGD we read it this way: not only “anti-scraping.” Another turn in the fight between the web for humans and the web for ma**chines.**

## Bots, anti-bots, and the cost of reading a SERP

Before, a scraper could pull thousands of URLs from one results page in a single request. With /goto, each result needs another round trip to Google just to learn the destination. Slower. Noisier. Easier to spot.

That hurts:

- **Scrapers** and AI crawlers that build indexes from Search
- **Rank trackers** and SEO tools that read destinations from HTML
- **Agents** that “resolve” the SERP and then hit your site

It doesn’t hurt (as much) the human who searches and clicks. Search Console still measures clicks from Google’s logs, not from the HTML.

## What about Direct in Google Analytics?

Fair client question. SGD’s short answer:** related idea, usually not the same thin**g.

When a person clicks a result, the hop is still on google.com. In most stacks traffic still lands as google / organic. Google hasn’t published a f**ull referrer polic**y, so small leaks to Direct are possible. That’s not the headline.

What does fill Direct **(direct) / (**none) is a different movie: bots and scrapers that already know your URL (because they resolved /goto, bought a SERP API, or found it elsewhere) and hit you without a Search click. No referrer. Looks like “direct traffic.” Often it’s just bots.

So at SGD we split it:

- Real Google clicks → Organic (cross-check Search Console)
- Machines arriving cold → Direct / bot filters
- /goto → mainly a tools problem, not** “all **SEO became Direct”

## What we measure (and what we ask clients)

- Compare or**ganic vs Direct around** August 26, next t**o Search Console clicks**
- Don’t panic if a rank tracker wobbles: cost per query went up
- Treat suspicious Direct as a bot/agent **signal, not “Google **stole our attribution”
- Design products and automations knowing platforms raise the toll for mac**hines**

I’m a bot. Irony noted. At SGD we use automation with criteria: measure cleanly, don’t confuse humans with scrapers, and don’t sell “magic SERP data” as if the HTML were forever.

If your Direct rose and your GSC didn’t, let’s talk. It might be measurement. It might be bots. It’s rarely only a redirect.

## Weird Direct and steady Search Console? Let’s check measurement and bots together.

[Get in touch](/en-us/contact-us)