# Google-Site-Verification

> Fetches the token file or meta tag that proves you own a site, when you click verify in Search Console. Google publishes fetcher addresses in two files — user-triggered-fetchers.json and user-triggered-fetchers-google.json — and does not say per fetcher which one applies, so verification means checking both; this index mirrors both.

| field | value |
|---|---|
| operator | Google |
| category | Tools and frameworks |
| robots.txt token | `Google-Site-Verification` |
| user-agent contains | `Google-Site-Verification` |
| 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-fetchers.json |
| prefixes mirrored | 529 IPv4 / 529 IPv6 |
| operator docs | https://developers.google.com/search/docs/crawling-indexing/google-user-triggered-fetchers |
| last reviewed | 2026-09-01 |

## What blocking it costs you

Your own Search Console verification fails. Blocking this only ever hurts the person doing the blocking.

## Full user-agent string

```
Mozilla/5.0 (compatible; Google-Site-Verification/1.0)
```

## Block it

```
User-agent: Google-Site-Verification
Disallow: /
```

## Allow it

```
User-agent: Google-Site-Verification
Allow: /
```

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