Web crawler lookup

What is AdsBot-Google?

AdsBot-Google is a generic crawler. Use this crawler profile to identify user-agent tokens, operator signals, platform hints, and recommended handling.

AdsBot-Google

Unknown · Generic crawler

Version
Unknown
First seen
May 24, 2026
Last seen
May 24, 2026
Confidence
Inferred user-agent token

What is AdsBot-Google?

AdsBot-Google is a generic crawler. AdsBot-Google is classified as a generic crawler that may fetch pages for search, SEO, monitoring, or data collection workflows.

AdsBot-Google was inferred from a bot-like product token in the user-agent string.

How to identify AdsBot-Google in logs

Search server logs for AdsBot-Google. Matching those tokens is useful for discovery, but IP verification is still recommended before trusting the identity.

AdsBot-Google

AdsBot-Google (+http://www.google.com/adsbot.html)

Use this as a web-crawler lookup reference for identifying how this user-agent presents itself in server logs.

User-agent signals

Product tokens
AdsBot-Google
Contact
None found
Platform
Unknown · Unknown
Browser profile
Unknown · Unknown
Browser-like UA
No
HTTP library
Unknown
Spoof risk
High

Questions answered by this crawler profile

What is AdsBot-Google?

AdsBot-Google is classified as a generic crawler that may fetch pages for search, SEO, monitoring, or data collection workflows.

Who operates AdsBot-Google?

The operator for AdsBot-Google is not known from the user-agent alone.

How do I identify AdsBot-Google in logs?

Search server logs for AdsBot-Google. Matching those tokens is useful for discovery, but IP verification is still recommended before trusting the identity.

Should I allow AdsBot-Google?

Verify IP ownership or behavior before making security decisions because user-agent strings can be spoofed. Monitor crawl rate and paths, then allow normal traffic or rate-limit/block if behavior becomes abusive.

Does AdsBot-Google respect robots.txt?

Robots.txt compliance cannot be proven from a user-agent string alone. Check the crawler operator documentation and your own logs before assuming behavior.