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

Googlebot-Video

Google · Search engines · json

User-agent: Googlebot-Video
Disallow: /


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

What it is

The video half of Googlebot. It crawls video files and the pages around them for Google Video search, and it is matched by a robots.txt group for Googlebot as well as by its own token.

What blocking it costs you

Your videos leave Google video search. A rule for Googlebot already covers it, so blocking this token alone is usually a mistake of precision rather than of intent.

Full user-agent string

Googlebot-Video/1.0

Allow it instead

User-agent: Googlebot-Video
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=googlebot-video&s=client-dossiers'

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