Ad review

AdsBot-Google-Mobile

Checks mobile landing pages for Google Ads.

See your agent traffic
PurposeAd review
HTTP identifierAdsBot-Google-Mobile
IdentityVerify beyond the name

THE SIGNAL

What this visit tells you

Mobile ad checks can fail even when the desktop page works.

Landing-page responses
Redirect chains
Failed checks

Your next move

Test the mobile redirect chain and the content returned at the campaign URL.

The technical details

Markdown
How to identify it

Look for the AdsBot-Google-Mobile identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.

How to check identity

Use Google’s published IP ranges for this crawler class and its forward-confirmed reverse DNS procedure.

Access and robots.txt

Google documents named robots.txt rules for this client; the wildcard * group may be ignored. Review the product-specific rule before blocking.

Optional full-site opt-out. Merge with existing rules only if intended. robots.txt does not secure private content.

User-agent: AdsBot-Google-Mobile
Disallow: /
Seeing 403 or 404 responses?

403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.

Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.

SourcesReviewed 2026-09-14

Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.

APOSTL Pulse

See AdsBot-Google-Mobile in context

See their requests. Find the pages that matter.

See your agent traffic