OAI-SearchBot

nounalso called ChatGPT search crawler or OpenAI search bot

Definition

OAI-SearchBot is OpenAI’s search crawler, the bot that surfaces websites in ChatGPT search answers, which makes it the OpenAI user agent to allow for ChatGPT visibility — unlike GPTBot, which collects content only for model training.

Updated 5 min read5 cited sources

On this page8 sections

Why it matters for founders and small teams

OAI-SearchBot is the one OpenAI crawler that decides whether ChatGPT search can cite you, and a forgotten robots.txt line or CDN setting shuts it out without any error you’d notice. For a small team competing with bigger brands for a place in ChatGPT’s shortlists, confirming it can reach your pages is a ten-minute check that every other piece of AI-search work depends on.

What does OAI-SearchBot do?#

OAI-SearchBot crawls web pages so OpenAI can surface them in ChatGPT’s search features, which makes it the crawler that decides whether ChatGPT search answers can show and cite your site.

OpenAI’s crawler documentation says OAI-SearchBot is used to “surface websites in search results in ChatGPT’s search features,” and spells out what blocking it costs: “Sites that are opted out of OAI-SearchBot will not be shown in ChatGPT search answers, though can still appear as navigational links.” OpenAI recommends allowing both the bot and requests from its published IP ranges. Its current user agent:

code
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36; compatible; OAI-SearchBot/1.4; +https://openai.com/searchbot

Match on the OAI-SearchBot token rather than the full string, which changes between versions. ChatGPT search also draws on third-party providers — OpenAI names Microsoft — so being indexed by Bing matters too. But OAI-SearchBot feeds OpenAI’s own index, and allowing it is the only inclusion rule OpenAI documents. The ChatGPT SEO guide covers the rest of the pipeline.

OAI-SearchBot vs GPTBot: what's the difference?#

OAI-SearchBot crawls for ChatGPT search, so blocking it removes you from ChatGPT’s cited answers, while GPTBot crawls for model training, so blocking it only opts you out of training; OpenAI treats the two as independent settings.

OAI-SearchBotGPTBotChatGPT-User
JobIndex pages for ChatGPT searchCollect content for model trainingFetch a page for a user’s conversation or custom GPT
Block it and…You’re not shown in ChatGPT search answersYour content shouldn’t be used in trainingChatGPT can’t read your page mid-conversation
Honors robots.txtYesYesNot always: rules “may not apply”
IP listopenai.com/searchbot.jsonopenai.com/gptbot.jsonopenai.com/chatgpt-user.json
AdviceAllowYour callAllow

Confusing the two is the most expensive robots.txt mistake in AI search: a site that blocks OAI-SearchBot to avoid training disappears from ChatGPT’s answers and gains nothing, because training runs on a different bot. If training is your concern, the bot to block is GPTBot. When both are allowed, OpenAI says it may use one crawl for both jobs, so allowing both doesn’t double your server load.

Worked example

The ChatGPT Reachability Audit

A way to measure how much of your site OAI-SearchBot can actually read, gate by gate. The inputs are illustrative, for a fictional project management company called Plannora — run the same steps on your own sitemap.

  1. 1

    Start with the pages you want cited

    Every URL in Plannora’s XML sitemap.

    180 URLs

  2. 2

    robots.txt lets OAI-SearchBot in

    A leftover Disallow: /blog/ under User-agent: * blocks the blog, because OAI-SearchBot has no group of its own. 60 URLs fail.

    120 URLs

  3. 3

    The CDN lets it through

    A rate-limit rule challenges bot traffic on /docs/, and the bot’s requests get a 403 on 25 URLs.

    95 URLs

  4. 4

    The answer is in the raw HTML

    The pricing and integration pages build their tables with JavaScript; grep finds the key sentence missing on 15 URLs.

    80 URLs

  5. =

    Reachable share

    80 ÷ 180: the share of the site ChatGPT search can currently read and cite.

    44%

The result: Each gate has a known fix: give OAI-SearchBot its own group, exempt OpenAI’s published IPs from the rate limit, and server-render the two templates. That lifts Plannora to all 180 URLs without writing a word of new content — which is why access is the first thing to audit.

Free to use and adapt. If you cite it, link to rankbox.xyz/glossary/oai-searchbot.

How do I allow OAI-SearchBot?#

Allow OAI-SearchBot by giving it its own Allow: / group in robots.txt, then making sure your CDN, firewall and bot-protection settings let its published IP ranges through — robots.txt alone isn’t enough if a security layer blocks the request first.

robots.txt
# ChatGPT search: required to be cited
User-agent: OAI-SearchBot
Allow: /
Disallow: /account/
Disallow: /checkout/
  1. Check for blanket blocks. A User-agent: * group with Disallow: / shuts OAI-SearchBot out unless it has a group of its own.
  2. Copy your private paths. A named group ignores the * group entirely, so repeat any Disallow lines you still need, as above.
  3. Open the CDN. Allowlist the IPs in openai.com/searchbot.json and don’t serve them challenges. From 15 September 2026, new Cloudflare domains block Training and Agent bots by default on pages with ads while allowing Search bots — check what your own plan and settings actually do.
  4. Wait about 24 hours. That’s how long OpenAI says robots.txt changes take to reach its systems.
  5. Serve the answer in HTML. OpenAI documents no JavaScript rendering, and Vercel’s crawler study saw OpenAI’s crawler fetch scripts without running them. See server-side rendering.

How do I check whether OAI-SearchBot visits my site?#

Check whether OAI-SearchBot visits your site by searching your access logs for its token, verifying the IPs against openai.com/searchbot.json, and requesting a key page with its user agent to confirm your server returns the real content rather than a challenge.

bash
# OpenAI bot hits by type
grep -oE "OAI-SearchBot|ChatGPT-User|GPTBot|OAI-AdsBot" access.log | sort | uniq -c
 
# Does the bot get your real content?
curl -s -A "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; OAI-SearchBot/1.4; +https://openai.com/searchbot" \
https://yoursite.com/pricing | grep -c "Plans start at"
 
# 0 = the text is rendered by JavaScript, or a WAF is serving a challenge

No hits at all usually means one of three things: the bot is blocked (look for 403s in your CDN’s firewall log), the site is new and hasn’t been discovered, or requests are dropped before they reach your logs. Remember that a curl from your own machine only tests user-agent rules; an IP-based bot rule can still treat the real bot differently. Logs prove access, not citations. To see whether ChatGPT actually cites you, run a fixed set of buyer prompts on a schedule, which is prompt tracking, and watch AI referral traffic from chatgpt.com.

Common mistakes with OAI-SearchBot#

The most common OAI-SearchBot mistakes are blocking it while trying to block training, leaving a CDN or bot-fight setting that challenges it, and using a robots.txt Disallow to hide a page that needs a noindex instead.

Myth

Blocking GPTBot keeps me out of ChatGPT.

Reality

GPTBot is training only. ChatGPT search visibility is OAI-SearchBot, and the two settings are independent.

Myth

A Disallow removes a page from ChatGPT.

Reality

A disallowed URL can still surface as a navigational link. To keep a page out, allow the crawler and use noindex — it has to fetch the page to see the tag. See robots.txt.

Myth

robots.txt is the only setting that matters.

Reality

CDN bot protection, block-AI toggles and rate limits act before robots.txt is ever consulted. Allowlist OpenAI’s published IPs and check your firewall log for challenges.

Myth

Allowing both OpenAI bots doubles the crawl load.

Reality

OpenAI says that when both are allowed, it may use the results from one crawl for both search and training.

Sources

  1. 1.Overview of OpenAI crawlersOpenAI · developers.openai.com
  2. 2.ChatGPT searchOpenAI Help Center · help.openai.com
  3. 3.How Google interprets the robots.txt specificationGoogle Search Central · developers.google.com
  4. 4.Your site, your rules: new AI traffic options for all customersCloudflare · blog.cloudflare.com
  5. 5.The rise of the AI crawlerVercel · vercel.com

Know someone who’d find this useful? Send it their way.

Written by

Rankbox Team

The team behind Rankbox. We study how ChatGPT, Perplexity, Gemini, and Google AI Overviews choose their sources, and publish what we learn so you can put it to work.

See which AI answers cite you today

Enter your site to see how often ChatGPT, Perplexity, Gemini, and Google cite your brand, and exactly what to publish next.

No credit card required · Free 7-day trial