# Google-Safety

> Google's abuse-investigation fetcher: malware review, phishing reports and similar. Google documents that it ignores robots.txt entirely, and a robots.txt rule for it does nothing.

| field | value |
|---|---|
| operator | Google |
| category | Tools and frameworks |
| robots.txt token | `Google-Safety` |
| user-agent contains | `Google-Safety` |
| robots.txt | not governed by robots.txt (user-initiated, by operator policy) |
| verify by | no published verification method |
| published IP ranges | none published |
| prefixes mirrored | 0 IPv4 / 0 IPv6 |
| operator docs | https://developers.google.com/search/docs/crawling-indexing/google-special-case-crawlers |
| last reviewed | 2026-09-14 |

## What blocking it costs you

Nothing you can control. The rule is ignored by design; listing the token is documentation, not enforcement.

## Full user-agent string

```
Google-Safety
```

## Block it

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

## Allow it

```
User-agent: Google-Safety
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-Safety?**  
  `curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=google-safety&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.

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-safety.json · index: https://www.pathwren.workers.dev/llms.txt