What Is OAI-SearchBot?

OAI-SearchBot is the OpenAI crawler used to surface websites in search results in ChatGPT's search features. For a health practice, it is the bot that matters most if you want ChatGPT to be able to show and link to you when a patient asks for a provider. OpenAI recommends allowing it so your site can appear in ChatGPT search results.

How OAI-SearchBot works

When a patient asks ChatGPT a question that needs fresh information, such as who offers a service nearby, ChatGPT can search the web. OAI-SearchBot is the crawler OpenAI documents for surfacing sites in those search features. It reads pages so they can be considered when ChatGPT builds an answer.

Your control is the robots.txt file, a plain-text file at yourpractice.com/robots.txt. A rule names a bot and says whether it may read the site. OpenAI is clear about what happens when you say no. Sites opted out of OAI-SearchBot will not be shown in ChatGPT search answers, though they can still appear as navigational links. A navigational link is a plain link to your site and not content quoted in the answer. OpenAI does not say when these links appear.

It helps to see this bot next to its two siblings.

• OAI-SearchBot surfaces sites in ChatGPT search. Blocking it has a direct visibility cost.
• GPTBot crawls content that may be used to train models. OpenAI ties it to training and says each bot setting is independent. See GPTBot.
• ChatGPT-User visits a page when a person asks for it. OpenAI says robots.txt rules may not apply, because a user starts the visit.

OpenAI states that each setting is independent. It also says that if a site allows both GPTBot and OAI-SearchBot, it may use the result of one crawl for both purposes, to avoid crawling twice. And it says it can take about 24 hours from a robots.txt update for its systems to adjust.

Two cautions. First, robots.txt is a request. Google's documentation says these files cannot enforce crawler behavior, and compliance is up to the crawler. Second, the file is not the only layer. On July 1, 2025, Cloudflare changed its default to block AI crawlers unless they pay creators. A site behind Cloudflare, or another security service, can refuse a bot even when robots.txt allows it. So an owner who sees "Allow" in the file but still has trouble should ask the developer about the security layer.

For the broader picture of what ChatGPT's search is and how it picks sources, see ChatGPT search.

Allowing the bot is access, which is a separate step from a page being indexed, so check both.

One practical note on timing. OpenAI's 24 hour figure is about its systems adjusting to your file. It is not a promise about when your pages will start appearing in answers. Treat it as the earliest point at which a retest means something. If you also want to decide about training bots, the trade-off is laid out under AI bot blocking.

Example: OAI-SearchBot at a health practice

Consider a chiropractic group that asked its developer to "block AI scrapers." This example is illustrative, not a transcript of a real site.

The developer pasted in a list of AI bot names from a blog post. The list included GPTBot, which fit the owner's wish, and also OAI-SearchBot. The group's pages are fine on Google, because Googlebot was not on the list. Nobody checked anything else.

Months later, the owner asks ChatGPT for a chiropractor for lower back pain in the group's city. The group is not shown. Many things decide who is named, and I cannot say this one setting is the whole cause. Nobody outside OpenAI can. But OpenAI's own page spells out the direct effect of opting out of OAI-SearchBot, which is that the site will not be shown in search answers.

The owner opens the robots.txt file, finds the line, and sees the problem within a minute.

User-agent: OAI-SearchBot
Disallow: /

The fix is to delete those lines, or to replace them with an explicit allow, and to leave the GPTBot rule in place if the owner still wants to opt out of training.

User-agent: OAI-SearchBot
Allow: /

After that, OpenAI says to allow about 24 hours. The owner then runs the same patient question several times in a fresh ChatGPT temporary chat and records whether the group is named. Answers vary from run to run, so a single run tells you little. The group is now at least eligible. Being named still depends on the quality of its pages and its presence elsewhere on the web.

The group also learns a second thing. Its pages were reachable to Google the whole time, so its normal reports looked fine. The loss was invisible unless somebody went looking, which is why the 60 second check below is worth putting on a calendar.

Block the bot that matches your goal, and check that the block does not also remove you from search.

How to check yours in 60 seconds

1. Open yourpractice.com/robots.txt in a browser.
2. Look for the name OAI-SearchBot.
3. If you see it with "Disallow: /" under it, ChatGPT search has been told to skip your site.
4. Also check for a broad rule, "User-agent: *" followed by "Disallow: /", which tells all bots to stay out.
5. Ask your developer whether Cloudflare or a security plugin blocks AI bots separately.
6. Save the date and what you found, so you can compare after your next site update.
7. If the file is blank or missing, no special rules exist, but still ask about the security layer.

What to do about it

1. Decide whether you want to be visible in ChatGPT search. For most practices that want new patients, the answer is yes.
2. Remove any rule that disallows OAI-SearchBot, and any broad rule that blocks every bot.
3. If you want to be explicit, add the allow rule shown above.
4. Keep your training decision separate by giving GPTBot its own rule.
5. Wait about 24 hours, the time OpenAI says its systems can take to adjust.
6. Test with real patient questions in a ChatGPT temporary chat, running each question several times because answers vary.
7. Log the results and watch for visits from ChatGPT in your analytics. See ChatGPT referral traffic.
8. Decide separately about the training bots, using the guidance on GPTBot.
9. Write down who owns this check, so it does not depend on someone remembering.
10. Recheck robots.txt every quarter and after any rebuild, since plugins and host changes can rewrite it.