# Google-Agent

> Agents hosted on Google infrastructure navigating the web and taking actions on a user's request. Google names one prefix list for it — user-triggered-agents.json — and is separately experimenting with Web Bot Auth under the identity https://agent.bot.goog.

| field | value |
|---|---|
| operator | Google |
| category | User-triggered fetchers |
| robots.txt token | `Google-Agent` |
| user-agent contains | `Google-Agent` |
| robots.txt | not governed by robots.txt (user-initiated, by operator policy) |
| verify by | published IP ranges |
| published IP ranges | https://developers.google.com/static/search/apis/ipranges/user-triggered-agents.json |
| prefixes mirrored | 3 IPv4 / 1 IPv6 |
| operator docs | https://developers.google.com/search/docs/crawling-indexing/google-user-triggered-fetchers |
| last reviewed | 2026-09-14 |

## What blocking it costs you

Google-hosted agents cannot complete a task on your site for a user who asked them to. This is the agentic-commerce fetch: blocking it removes you from what an assistant can actually do rather than from what it can say.

## Full user-agent string

```
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko; compatible; Google-Agent; +https://developers.google.com/crawling/docs/crawlers-fetchers/google-agent) Chrome/W.X.Y.Z Safari/537.36
```

## Block it

```
User-agent: Google-Agent
Disallow: /
```

## Allow it

```
User-agent: Google-Agent
Allow: /
```

## Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

- **How do I prove a request really is Google-Agent?**  
  `curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=google-agent&s=client-dossiers'`  
  The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.
- **Is 136.121.16.0 really Google-Agent?**  
  `curl -s 'https://www.pathwren.workers.dev/tools/verify-crawler?ip=136.121.16.0&ua=Google-Agent&s=client-dossiers'`  
  That address checked against every prefix this host mirrors. 136.121.16.0 is the first address of 136.121.16.0/24, one of the ranges listed on this page — so the link is a worked example that returns a match. Swap in an address from your own log.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error.

JSON: https://www.pathwren.workers.dev/crawler/google-agent.json · index: https://www.pathwren.workers.dev/llms.txt