OpenAI Adds OAI-AdsBot to Crawler Docs for ChatGPT Ads
▼ Summary
– OpenAI added OAI-AdsBot to its crawler documentation, bringing the total number of documented bots to four.
– OAI-AdsBot only visits pages submitted as ChatGPT ads to check policy compliance and help determine ad relevance.
– Data collected by OAI-AdsBot is not used to train OpenAI’s generative AI foundation models.
– No public IP list for OAI-AdsBot has been published, making verification of real bot visits difficult.
– The bot may be blocked by aggressive bot protection tools, which could create validation issues for advertisers.
OpenAI has quietly added a new entry to its public crawler documentation: OAI-AdsBot. This bot is designed to visit pages submitted as ChatGPT advertisements, where it verifies policy compliance and helps determine ad relevance. The addition brings OpenAI’s documented bot roster to four, joining OAI-SearchBot, GPTBot, and ChatGPT-User.
According to OpenAI, OAI-AdsBot only targets pages that have been submitted as ads. Crucially, the data it collects is not used to train the company’s generative AI foundation models. This distinction keeps it separate from GPTBot, which handles training data collection, and from OAI-SearchBot, which powers content in ChatGPT search. ChatGPT-User, meanwhile, fetches pages during user-initiated browsing.
How OAI-AdsBot Works
Per OpenAI’s documentation, OAI-AdsBot may visit an ad’s landing page after submission. Its primary task is to check whether that page complies with OpenAI’s ad policies. It may also use content from the landing page to help decide when to show the ad to ChatGPT users. The bot identifies itself with the user-agent string: `Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; OAI-AdsBot/1.0; +https://openai.com/adsbot`. Unlike OAI-SearchBot and GPTBot, which are both at version 1.3, OAI-AdsBot is limited strictly to ad landing pages. It does not crawl the wider web.
What OAI-AdsBot Does Not Do
Because its data is excluded from generative AI training, OAI-AdsBot operates in a separate lane from GPTBot. It also remains distinct from OAI-SearchBot and ChatGPT-User in function. While OAI-SearchBot and GPTBot can be controlled independently through robots.txt, ChatGPT-User is user-initiated and may not respect those rules. The OAI-AdsBot entry does not specify how it handles robots.txt, leaving some ambiguity for site owners.
Missing IP Lists Create Verification Challenges
OpenAI publishes IP range files for its three earlier bots at dedicated URLs: `openai.com/searchbot.json`, `openai.com/gptbot.json`, and `openai.com/chatgpt-user.json`. However, as of publication, no equivalent `openai.com/adsbot.json` file exists. Without a published IP list, verifying a genuine OAI-AdsBot visit becomes harder. User-agent strings can be spoofed, and the IP lists provide a way to cross-check for the other bots. For OAI-AdsBot, that cross-check is not yet available.
Why This Matters for Advertisers and Site Operators
OAI-AdsBot serves two key audiences. For advertisers buying placements on ChatGPT, the bot must reach their landing pages for ad validation to succeed. For anyone tracking AI bot activity in server logs, this adds a new user-agent to monitor, one tied to paid inventory rather than search or training. Aggressive bot protection tools like Cloudflare or Akamai may block OAI-AdsBot before it reaches the page, potentially creating validation friction for advertisers with strict mitigation settings.
What to Watch For
ChatGPT’s ad program has moved quickly since OpenAI began testing advertisements on February 9. As access expands to more advertisers, OAI-AdsBot traffic will increasingly appear in server logs. Keep an eye out for an eventual IP range file at `openai.com/adsbot.json` if OpenAI chooses to publish one. For now, the user-agent string is the only tool available for identification.
(Source: Search Engine Journal)
