Googlebot
Crawls pages for Google Search using desktop and smartphone variants.
Web searchTHE SIGNAL
Mobile ad checks can fail even when the desktop page works.
Test the mobile redirect chain and the content returned at the campaign URL.
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.
Use Google’s published IP ranges for this crawler class and its forward-confirmed reverse DNS procedure.
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: /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.
Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.
See their requests. Find the pages that matter.
See your agent traffic