Why does my server log show GPTBot but not OAI-SearchBot?

OpenAI runs several crawlers, and as of October 2026 its bots documentation describes them as separate controls. GPTBot crawls content that may be used to train OpenAI's foundation models. OAI-SearchBot is used to surface websites in ChatGPT's search features. OpenAI's own wording is that "each setting is independent of the others."

So a log full of GPTBot requests is not evidence that ChatGPT search can see you. The two bots follow their own robots.txt groups, arrive on their own schedules, and can be treated differently by your firewall. Our GPTBot vs OAI-SearchBot guide covers the full split.

The consequence of missing OAI-SearchBot is specific. OpenAI says sites opted out of OAI-SearchBot "will not be shown in ChatGPT search answers, though can still appear as navigational links." That makes this the crawler to fix first if ChatGPT search matters to you.

There are three likely causes, and you should rule them out in this order:

1. robots.txt disallows OAI-SearchBot.
2. A firewall, CDN or bot-management rule rejects it.
3. It hasn't fetched your pages yet, or your log view hides it.

Open /robots.txt and look for any group that names OAI-SearchBot, plus the User-agent: * group. Under the Robots Exclusion Protocol (RFC 9309), a crawler obeys the most specific group that matches its name. A dedicated OAI-SearchBot group with Disallow: / blocks it even when the wildcard group allows everything.

The common failure is a blanket "block AI bots" list copied from a template. It often names OAI-SearchBot alongside GPTBot, sometimes after someone later re-allowed GPTBot. To allow search while keeping your other rules, a minimal group looks like this:

User-agent: OAI-SearchBot
Allow: /

If you want to keep training off and search on, follow the block training, keep search playbook. For a quick read of your current file, the free ChatGPT search block check parses it for you.

robots.txt is only half of OpenAI's requirement. Its help center says that to make a site eligible, you should allow OAI-SearchBot to crawl "and confirm that the website host or content delivery network allows traffic from OpenAI's published searchbot IP addresses." The conjunction matters.

This is the case that matches your symptom most often. A bot-management rule, a WAF challenge or a rate limit can treat the two user agents differently. If the block happens at the CDN edge, the request may never reach your origin server. Your origin logs then show nothing for OAI-SearchBot, which looks exactly like "never visited."

What to check:

• Your CDN or WAF dashboard for blocked, challenged or 403 requests from OAI-SearchBot.
• Any allowlist built from IP ranges. OpenAI publishes OAI-SearchBot's ranges at openai.com/searchbot.json, separate from GPTBot's.
• Whether your origin is reachable over IPv4. When our evidence base was verified in August 2026, OpenAI's published ranges were IPv4 only. See whether ChatGPT's crawlers can reach an IPv6-only site.

The step-by-step method is in testing whether your firewall lets AI crawlers in. The AI Crawler Checker requests a page as each AI crawler and shows which ones your firewall turns away.

Before concluding OAI-SearchBot is blocked, make sure your log view isn't hiding it.

• Search raw access logs for the string OAI-SearchBot, not a dashboard category. Analytics tools often group unknown bots under "other."
• Look at CDN logs as well as origin logs, for the reason above.
• Read the status codes. A 200 is a pass. A 403, 429 or challenge page is a block. Our guide to reading server logs for AI crawler status codes explains each one.
• Verify identity. Anyone can fake a user-agent string, so match the request IP against the ranges OpenAI publishes for that bot.

If robots.txt allows it, the network lets it through, and the logs are clean, the remaining explanation is that it hasn't fetched yet. OpenAI doesn't publish a crawl schedule for OAI-SearchBot. Our page on how often AI search engines crawl covers what is and isn't known.

You control access: robots.txt groups, firewall rules, CDN settings and IP reachability. These are the levers with documented consequences from OpenAI itself.

You don't control what happens after that. Passing both gates makes your pages eligible for ChatGPT search. It doesn't decide whether ChatGPT retrieves them for a given question or cites them. OpenAI's only ranking disclosure is that it uses "multiple factors" and that placement is not guaranteed.

If OAI-SearchBot does visit and you still never appear, the problem has moved past access. Start with what else blocks a site that robots.txt already allows.

Does blocking GPTBot remove me from ChatGPT search? No. OpenAI states each crawler setting is independent. A site can disallow GPTBot to signal that content shouldn't be used for training while allowing OAI-SearchBot so it can appear in ChatGPT search answers. The reverse also holds: allowing GPTBot does nothing for search. If ChatGPT search matters to you, the bot to check is OAI-SearchBot.

What is ChatGPT-User, and why does it show up instead? ChatGPT-User fetches pages when a person's action in ChatGPT triggers a visit. OpenAI says it is not used to determine whether content may appear in search, and that robots.txt rules may not apply to it because the request is user-initiated. Seeing ChatGPT-User in your logs proves the network path works for that agent, but it says nothing about OAI-SearchBot.

Will allowing OAI-SearchBot get me cited in ChatGPT? It makes you eligible, nothing more. OpenAI describes ChatGPT search ranking as using multiple factors and says placement is not guaranteed. ChatGPT also decides per question whether to search at all and rewrites the query before searching. Fixing access removes a block. It doesn't control which pages ChatGPT retrieves or cites for a given answer.

How do I confirm a log line really came from OpenAI? Check the IP address, not just the user-agent string, because user agents are easy to fake. OpenAI publishes separate IP range files for its crawlers, including openai.com/searchbot.json for OAI-SearchBot. Match the request IP against the file for the bot it claims to be. Treat any mismatch as an impostor and don't base access decisions on it.