OAI-AdsBot

OpenAI · Validates safety and relevance of landing pages submitted as ads on ChatGPT; not used to train foundation models

By Vinespire Editorial Team, Editorial ·

Update: Verified against OpenAI operator documentation for OAI-AdsBot.

See our sourcing methodology →

This page is the operator/profile guide for OAI-AdsBot. To paste a full robots.txt and check OAI-AdsBot plus other AI crawlers in one pass, use the Robots.txt AI Crawler Validator. Short definitional entries also live in the AI search glossary.

Related free utilities are in free AI SEO tools.

What is OAI-AdsBot?

OAI-AdsBot is documented on OpenAI’s official crawlers page as the agent used to validate the safety of web pages submitted as ads on ChatGPT. When an advertiser submits an ad, OpenAI may visit the landing page to check policy compliance and may use landing-page content to determine when the ad is most relevant to show. OpenAI states that OAI-AdsBot only visits pages submitted as ads and that data collected by OAI-AdsBot is not used to train generative AI foundation models. The full user-agent string is documented as Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; OAI-AdsBot/1.0; +https://openai.com/adsbot, with published IP addresses at openai.com/adsbot.json. robots.txt product token matching uses OAI-AdsBot. OpenAI’s advertiser guidance states that OpenAI crawlers respect robots.txt and that advertisers must allow OAI-AdsBot for ad validation workflows; if robots.txt disallows access, crawling stops. OAI-AdsBot is separate from GPTBot (training-oriented crawl), OAI-SearchBot (ChatGPT search indexing), and ChatGPT-User (user-initiated fetches). Enterprise and growth teams running ChatGPT ads should treat this agent as ads infrastructure, not as a general web-wide training crawler.

How to block OAI-AdsBot

Add this group to robots.txt to disallow OAI-AdsBot. Path rules can be narrowed if you only need to protect parts of the site.

User-agent: OAI-AdsBot
Disallow: /

How to allow OAI-AdsBot

For most public marketing and documentation sites, allowing well-behaved AI agents is the default recommended stance for AI visibility—while remaining a factual robots.txt Allow rule you can reverse later.

User-agent: OAI-AdsBot
Allow: /

Should you block OAI-AdsBot?

If you run or plan ChatGPT ads that land on your site, allowing OAI-AdsBot on those paths is aligned with OpenAI’s advertiser guidance—blocking can prevent successful ad validation. If you never submit ads to ChatGPT, OAI-AdsBot traffic should be rare because OpenAI documents that it only visits pages submitted as ads. Blocking sitewide is still a valid licensing or traffic choice, but it can break advertising workflows later if paths remain Disallowed. Blocking OAI-AdsBot does not configure GPTBot, OAI-SearchBot, or ChatGPT-User. Prefer allowing the specific landing paths you use for ads while keeping private app areas authenticated. After robots or WAF changes, re-check OpenAI’s bot docs and adsbot.json IP list so security tooling does not false-positive the crawler. robots.txt is not a substitute for access control on non-public content.

Category: Dataset / other

Official documentation (OpenAI)

Last verified: . Re-check operator docs after major crawler announcements.

OAI-AdsBot FAQ

  • OpenAI’s advertiser guidance states that OpenAI crawlers respect robots.txt and that disallowing access stops crawling. Use User-agent: OAI-AdsBot with Allow or Disallow as needed.