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

Storebot-Google

Google · Search engines · json

User-agent: Storebot-Google
Disallow: /


robots.txt token	`Storebot-Google`
User-agent contains	`Storebot-Google`
Operator	Google
Category	Search engines
robots.txt	obeys robots.txt (documented)
Verify by	published IP ranges
Published ranges	136 IPv4 + 136 IPv6 · json · source

What it is

Checks shopping and checkout flows for Google's shopping surfaces.

What blocking it costs you

Product listings may lose shopping-specific enrichment. Irrelevant to non-commerce sites.

Full user-agent string

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Safari/537.36 (compatible; Storebot-Google/1.0; +https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers)

Allow it instead

User-agent: Storebot-Google
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=storebot-google&s=client-dossiers'

/tools/verification-methods?crawler=storebot-google
How do I prove a request really is Storebot-Google? 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=108.177.2.0&ua=Storebot-Google
Is 108.177.2.0 really Storebot-Google? That address checked against every prefix this host mirrors. 108.177.2.0 is the first address of 108.177.2.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/overview-google-crawlers
Machine copies: json · markdown
Policies that name this crawler: allow-all · allow-ai-search-only · maximum-ai-visibility