OpenAI · Other AI
OAI-AdsBot
Fires only against URLs somebody has already submitted as a ChatGPT ad landing page: OpenAI states it visits only pages submitted as ads. That visit does two jobs: screening the page for policy compliance, and reading its content to judge when the ad is most relevant to show. The trigger is commercial rather than editorial, which puts it outside the pattern the other three OpenAI tokens share, and OpenAI says what it collects is walled off from foundation-model training.
- Operated by
- OpenAI
- Purpose
- Other AI
- robots.txt token
- OAI-AdsBot
- Verification
- IP verified
AI-adjacent traffic that does not fit the three purposes above.
How to verify OAI-AdsBot
OpenAI publishes the IP ranges OAI-AdsBot crawls from, and we fetch that list on a schedule. A request claiming to be OAI-AdsBot can therefore be checked against 2 published ranges: one that does not match is not this crawler.
Published ranges last confirmed by us on .
User agent
OpenAI publishes this user agent for OAI-AdsBot. Match on the OAI-AdsBot product token rather than the whole string: vendors revise the surrounding version and URL fragments without notice.
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; OAI-AdsBot/1.0; +https://openai.com/adsbotrobots.txt for OAI-AdsBot
Yes. OpenAI's advertiser guidance is unambiguous that its crawlers respect robots.txt and that crawling stops immediately where access is disallowed, and it shows the token used directly as a robots.txt user-agent directive.
Block
User-agent: OAI-AdsBot
Disallow: /Allow
User-agent: OAI-AdsBot
Allow: /robots.txt is a request, not an enforcement mechanism. It is honoured by convention, and a crawler that ignores it is stopped at your edge, not in a text file.
What blocking OAI-AdsBot costs you
Genuinely nothing for any site that does not advertise on ChatGPT: it will never knock. For anyone who does, the cost is a hard gate rather than a degradation: ads whose landing page it cannot reach do not clear review, and OpenAI explicitly closes the escape hatch, telling advertisers not to rely on a manual bypass but to fix robots.txt, WAF, CDN, authentication and rate-limiting blocks instead. The realistic failure mode is accidental: an agency buys ChatGPT ads while the site's WAF silently returns 403 to the bot, and nobody connects the two.