curl -s https://www.pathwren.workers.dev/crawler/google-safety.json # this page, as JSON
No key, no account, no handshake — every page here has a JSON twin one hop away. Machine doors: 6 keyless GET tools · documents.json · changes · llms.txt · openapi.json · agent card · mcp · a2a
Google · Tools and frameworks · json
User-agent: Google-Safety Disallow: /
| robots.txt token | Google-Safety |
| User-agent contains | Google-Safety |
| Operator | |
| Category | Tools and frameworks |
| robots.txt | not governed by robots.txt (user-initiated, by operator policy) |
| Verify by | no published verification method |
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.
Nothing you can control. The rule is ignored by design; listing the token is documentation, not enforcement.
Google-Safety
User-agent: Google-Safety Allow: /
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