curl -s https://www.pathwren.workers.dev/crawler/google-safety.json   # this page, as JSON

Google-Safety

Google · Tools and frameworks · json

User-agent: Google-Safety
Disallow: /

What it is

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.

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

Allow it instead

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.

curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=google-safety&s=client-dossiers'

• /tools/verification-methods?crawler=google-safety
  How do I prove a request really is Google-Safety? 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. All of them.

Operator documentation: https://developers.google.com/search/docs/crawling-indexing/google-special-case-crawlers
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-disputed · maximum-ai-visibility