OAI-SearchBot
OAI-SearchBot is OpenAI’s crawler for search: it indexes pages so they can be surfaced and cited in ChatGPT’s search features. It is controlled by its own robots.txt token, independent of GPTBot (training) and ChatGPT-User (user-triggered fetches).
OAI-SearchBot in Practice
OpenAI’s documentation states that OAI-SearchBot is for search and that GPTBot is the separate control for content that may train its models, so a site can permit the first and refuse the second ([OpenAI](https://developers.openai.com/api/docs/bots)). Most robots.txt mistakes here come from collapsing them into one decision: a blanket block meant to opt out of training also removes the site from ChatGPT search eligibility ([iCoda](https://icoda.io/blog/gptbot-guide/)). OpenAI also notes that ChatGPT-User fetches happen because a user asked, so robots.txt rules may not apply to them. If Northloom’s returns page returns a 403 to OAI-SearchBot because of a firewall rule, ChatGPT can’t index it, and it won’t be cited for questions about returns.
How OAI-SearchBot Activity Is Tracked
Filter logs for the OAI-SearchBot user agent and verify requests against OpenAI’s published SearchBot IP ranges ([xSeek](https://www.xseek.io/docs/openai-crawlers-and-user-agents)). As a downstream check, look for sessions from chatgpt.com in GA4’s Session source / medium report — the click-through side of the same pipeline.
Why OAI-SearchBot Matters
Allowing OAI-SearchBot makes pages eligible for ChatGPT search results; it doesn’t guarantee citation. Crawl access is the entry requirement, not the ranking factor — structure, clarity, and relevance decide whether an eligible page is actually used.
Terms Related to OAI-SearchBot
GPTBot ·
AI Referral Traffic ·
robots.txt for AI Crawlers
Citation Share
FAQ
Does allowing OAI-SearchBot let OpenAI train on my content?
No — OpenAI documents GPTBot as the separate control for training, so the two can be set independently ([SEO Nest](https://seonest.uz/blog/oai-searchbot)).
