curl -s https://www.pathwren.workers.dev/crawler/adsbot-google-mobile-apps.json   # this page, as JSON

AdsBot-Google-Mobile-Apps

Google · Tools and frameworks · json

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

What it is

Checks Android app landing pages for Google Ads. It obeys a group named for its own token and, per Google, follows the AdsBot-Google rules otherwise.

What blocking it costs you

App-install ad landing pages go unscored. Nothing organic changes.

Full user-agent string

AdsBot-Google-Mobile-Apps

Allow it instead

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

• /tools/verification-methods?crawler=adsbot-google-mobile-apps
  How do I prove a request really is AdsBot-Google-Mobile-Apps? 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-Apps
  Is 108.177.2.0 really AdsBot-Google-Mobile-Apps? 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