OAI-SearchBot

What OAI-SearchBot does

OAI-SearchBot builds and refreshes the index behind ChatGPT's search features. OpenAI documents it as separate from GPTBot: it is not used for model training, and blocking one does not block the other. It arrived in 2024 alongside OpenAI's push into search, and its existence is itself informative - OpenAI splitting search indexing from training collection was a concession to publishers who wanted referral upside without donating training data.

Why it visits your site

It indexes pages so ChatGPT can surface and cite them when users search. Fresh, factual, well-structured pages attract it. Seeing it arrive for the first time is a small milestone: it means ChatGPT search considers your site worth indexing.

The bigger picture: AI search bots

AI search bots are the closest thing the AI era has to the old search bargain: they index your pages so an answer engine can cite and link them. When ChatGPT search or Perplexity answers with your page as a source, the crawl that preceded it is what made the citation possible. Referral volume from these engines is still small next to Google, but it is qualitatively different traffic - a reader who clicks through from a cited answer arrives having already been told your page is the authority on their question.

The strategic mistake to avoid is lumping these bots in with training crawlers under one blanket "block AI" rule. The major operators deliberately split their tokens so that training and search indexing can be controlled separately. A site that blocks everything AI-shaped removes itself from the one AI channel that links back - usually the opposite of what the blanket rule intended.

Should you block it?

For most sites, no - this is the crawler that can actually send you readers, since ChatGPT search links out with citations. The common publisher stance is: block GPTBot (training), allow OAI-SearchBot (referrals). Given ChatGPT's audience size, exclusion from its search index is a real visibility cost. Block it only if you want out of AI search entirely.

Block via robots.txt

Add these lines to the robots.txt at your site root to ask OAI-SearchBot to stay away:

User-agent: OAI-SearchBot
Disallow: /

Remember that robots.txt is a request, not a lock - compliance is voluntary, and enforcement happens at the server. Viz's AI Control pairs robots.txt rules with server-level 403 responses and then probes your site to verify the block is actually holding.

How to see OAI-SearchBot traffic on your site

You have three windows onto it, each with a catch. Raw hosting access logs contain every OAI-SearchBot request, but many managed WordPress hosts don't expose them, and when they do you are grepping text files by hand. A CDN dashboard sees the traffic at the edge, but it lives outside WordPress and speaks in totals, not in your site's terms. And JavaScript analytics - GA4 and friends - will never show it at all, because OAI-SearchBot doesn't run scripts.

Viz's answer is the request log: filter to OAI-SearchBot and read exactly which URLs it fetched and when, right inside wp-admin - then watch the same filter after any blocking decision to see whether the visits stopped, slowed, or kept coming.