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

AdsBot-Google-Mobile

Google · Tools and frameworks · json

User-agent: AdsBot-Google-Mobile
Disallow: /


robots.txt token	`AdsBot-Google-Mobile`
User-agent contains	`AdsBot-Google-Mobile`
Operator	Google
Category	Tools and frameworks
robots.txt	ignores the * group; obeys rules named for its own token
Verify by	published IP ranges
Published ranges	136 IPv4 + 136 IPv6 · json · source

What it is

The mobile-web landing page checker for Google Ads. Same rules as AdsBot-Google: the * group does not apply to it, its own token does.

What blocking it costs you

Mobile ad landing pages go unscored and the ads pointing at them rank worse. No effect on organic search.

Full user-agent string

Mozilla/5.0 (Linux; Android 5.0; SM-G920A) AppleWebKit (KHTML, like Gecko) Chrome Mobile Safari (compatible; AdsBot-Google-Mobile; +http://www.google.com/mobile/adsbot.html)

Allow it instead

User-agent: AdsBot-Google-Mobile
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=adsbot-google-mobile&s=client-dossiers'

/tools/verification-methods?crawler=adsbot-google-mobile
How do I prove a request really is AdsBot-Google-Mobile? 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=AdsBot-Google-Mobile
Is 108.177.2.0 really AdsBot-Google-Mobile? 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/google-special-case-crawlers
Machine copies: json · markdown
Policies that name this crawler: allow-all · maximum-ai-visibility