curl -s https://www.pathwren.workers.dev/crawler/google-cws.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-CWS

Google · Tools and frameworks · json

User-agent: Google-CWS
Disallow: /


robots.txt token	`Google-CWS`
User-agent contains	`Google-CWS`
Operator	Google
Category	Tools and frameworks
robots.txt	not governed by robots.txt (user-initiated, by operator policy)
Verify by	published IP ranges
Published ranges	529 IPv4 + 529 IPv6 · json · source

What it is

The Chrome Web Store fetcher. It requests the URLs a developer put in the metadata of a Chrome extension or theme. 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.

What blocking it costs you

Chrome Web Store listings that point at your pages cannot fetch them. Relevant only if you publish extensions.

Full user-agent string

Mozilla/5.0 (compatible; Google-CWS)

Allow it instead

User-agent: Google-CWS
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-cws&s=client-dossiers'

/tools/verification-methods?crawler=google-cws
How do I prove a request really is Google-CWS? The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.
/tools/verify-crawler?ip=107.178.192.0&ua=Google-CWS
Is 107.178.192.0 really Google-CWS? That address checked against every prefix this host mirrors. 107.178.192.0 is the first address of 107.178.192.0/27, 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. All of them.

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