Why does OAI-SearchBot read only robots.txt and leave?
The short answer: we do not know yet. What we do know: on our site pw.migurei.ai, OpenAI's search bot OAI-SearchBot (IP-checked) came 49 times between 1 October 2026 and 26 October 2026 15:58, and every time it read /robots.txt and nothing else. Of the 29 pages in our sitemap it fetched 0. In the same period, bots of other search services built for AI did fetch pages (ShapBot 19, KeenableBot 19†). We checked that nothing in front of the site blocks it. We added an OAI-SearchBot group to robots.txt and made the sitemap's update dates accurate; pages fetched stayed at zero. Possible reasons are listed below as untested hypotheses.
Recorded 26 October 2026 15:58 (Japan time). Every number comes from the server log of one site of ours, counted on the recording date.
Words used on this page
- We / our: migurei (a subsidiary of HBLAB), which runs Parallel World and the test site pw.migurei.ai ("pw" below).
- IP check: anyone can claim a bot's name (UA, user agent), so we count a request only when its IP address is in the list the bot's operator publishes.
- Page fetched: a request for the content of a URL listed in the sitemap.
/robots.txtand/sitemap.xmlare not counted.
Day by day
IP-checked requests in pw's server log, counted per day in Japan time (the KeenableBot column alone is counted by the name it gave†). "Pages" is the number of sitemap URLs fetched that day.
| Date (Japan time) | OAI-SearchBot: robots.txt reads | OAI-SearchBot: pages | GPTBot: pages | ShapBot: pages | KeenableBot: pages† |
|---|---|---|---|---|---|
| 2026-10-01 | 1 | 0 | 0 | 0 | 0 |
| 2026-10-02 | 1 | 0 | 0 | 0 | 0 |
| 2026-10-03 | 2 | 0 | 0 | 0 | 0 |
| 2026-10-04 | 1 | 0 | 0 | 0 | 0 |
| 2026-10-05 | 2 | 0 | 0 | 0 | 0 |
| 2026-10-06 | 1 | 0 | 0 | 0 | 0 |
| 2026-10-07 | 2 | 0 | 0 | 0 | 0 |
| 2026-10-08 | 1 | 0 | 0 | 0 | 0 |
| 2026-10-09 | 2 | 0 | 0 | 0 | 0 |
| 2026-10-10 | 1 | 0 | 0 | 0 | 0 |
| 2026-10-11 | 2 | 0 | 0 | 0 | 0 |
| 2026-10-12 | 1 | 0 | 0 | 0 | 0 |
| 2026-10-13 | 2 | 0 | 0 | 0 | 0 |
| 2026-10-14 | 1 | 0 | 0 | 0 | 0 |
| 2026-10-15 | 2 | 0 | 0 | 0 | 0 |
| 2026-10-16 | 2 | 0 | 15 | 0 | 0 |
| 2026-10-17 | 3 | 0 | 0 | 0 | 1 |
| 2026-10-18 | 2 | 0 | 0 | 0 | 0 |
| 2026-10-19 | 3 | 0 | 0 | 19 | 0 |
| 2026-10-20 | 2 | 0 | 0 | 0 | 0 |
| 2026-10-21 * | 3 | 0 | 0 | 0 | 0 |
| 2026-10-22 | 2 | 0 | 0 | 0 | 9 |
| 2026-10-23 | 3 | 0 | 0 | 0 | 9 |
| 2026-10-24 | 2 | 0 | 0 | 0 | 1 |
| 2026-10-25 | 3 | 0 | 0 | 0 | 0 |
| 2026-10-26 | 2 | 0 | 18 | 0 | 0 |
| Total | 49 | 0 | 23 | 19 | 19 |
* On 21 October 2026 at 18:45 Japan time we deployed the changes described under "What we tried".
Compared with other bots
Same period, same site, same sitemap (29 URLs, read 26 October 2026 15:58).
| Bot (operator) | Job (operator's description) | Requests | robots.txt | sitemap.xml | Pages fetched |
|---|---|---|---|---|---|
| OAI-SearchBot (OpenAI) | ChatGPT search | 49 | 49 | 0 | 0 / 29 |
| GPTBot (OpenAI) | Training AI models | 66 | 0 | 11 | 23 / 29 |
| ShapBot (Parallel Web Systems) | Search API for AI agents | 43 | 0 | 2 | 19 / 29 |
| KeenableBot (Keenable)† | A search index that answers queries from AI agents and applications | 25 | 2 | 2 | 19 / 29 |
- Split by how it named itself, OAI-SearchBot's 49 requests were:
OAI-SearchBot/1.4; robots.txt;(permission check only) 11,OAI-SearchBot/1.038, and the page-fetchingOAI-SearchBot/1.40. OpenAI's official page (https://developers.openai.com/api/docs/bots, read 18 October 2026) describes the first two as robots.txt checks. - OAI-SearchBot has never fetched pw's
/sitemap.xml. pw's robots.txt has aSitemap:line. - GPTBot is OpenAI's other bot; the pages it fetched are bunched on 16 October 2026 and 26 October 2026. OpenAI says that when a site allows both bots it "may use the results from just one crawl for both use cases" (more in Is ChatGPT visiting your site?).
† KeenableBot is outside our automatic IP check (Keenable's list is not in our bot registry yet); it is counted by the name it gave only. We matched it by hand against Keenable's published list (https://app.keenable.ai/bot/keenablebot.json); on 24 October 2026 all 24 requests were from listed addresses.
It was not blocked in front of the site
Our first suspect was Cloudflare (the service that relays traffic in front of our site). What we found on 21 October 2026:
- All of Cloudflare's AI-bot settings were off.
- On Cloudflare's side too, every request to pw from a visitor calling itself OAI-SearchBot was for
/robots.txtand was answered normally (HTTP 200). Block events: 0.
So OAI-SearchBot was not stopped on its way to pages; it read robots.txt and nothing else. One gap: we could not read Cloudflare's custom WAF rules (permissions). On pw there were 0 blocks from such rules.
What we tried
On 21 October 2026 at 18:45 Japan time we deployed two changes together.
- A robots.txt group just for OAI-SearchBot. Before, one
User-agent: *group saidAllow: /to every bot. The permission is the same, but we added an explicitUser-agent: OAI-SearchBotgroup, thinking a robots.txt change might prompt OpenAI to look at the site again. The basis was thin: once, after a robots.txt change on our company site migurei.ai on 12 October 2026, GPTBot crawled the whole site. - Sitemap `<lastmod>` set to the day a page's content really changed. The date moves only when a hash (a value computed from the content) of the page body changes. Google and Bing say they use lastmod only when it is accurate.
What happened
- After the change, OAI-SearchBot first read robots.txt at 21 October 2026 22:43 Japan time, 4.0 hours after deployment.
- From the change to 26 October 2026 15:58, OAI-SearchBot came 13 times, every time for
/robots.txt. Pages fetched: 0;/sitemap.xmlreads: 0. - "Change robots.txt and OpenAI looks at the site again" now holds for us 1 time in 2 (yes on migurei.ai, no on pw).
- As OAI-SearchBot has not read
/sitemap.xml, lastmod most likely has not reached this bot. Its effect on Google and Bing we could not measure cleanly, because we corrected the lastmod dates several times during the same period.
Possible reasons (none of them tested)
These are hypotheses. We do not know which one holds, whether several combine, or whether the reason is something else.
- It finds pages by following links, and pw gives it nowhere to start. On another site we monitor (logs from June to October 2026), 784 of the 853 times (92%) OAI-SearchBot fetched a new page for the first time, the page was linked from a page OAI-SearchBot itself had just fetched. On pw it has fetched no page yet, so that path cannot start. This is an observation on one other site, not something we tested on pw.
- Checking robots.txt and fetching pages are separate jobs. OpenAI documents separate names for the check. Regular robots.txt reads may be permission checks only, not a sign that page fetches will follow.
- GPTBot's crawl is enough. OpenAI says one crawl may serve both search and training. GPTBot has fetched pages, so OAI-SearchBot may have no need to come for them. Whether they were in fact used for search, our log cannot tell.
- New, barely linked sites wait. pw is a new site, public since early October 2026, with almost no links from other sites. An article on Zenn (by hirajo, 11 October 2026, https://zenn.dev/hirajo/articles/crawler-google-vs-chatgpt) reports that on a new site OAI-SearchBot read only robots.txt for the first days and began fetching pages two days after an article went up (one report, not checked by us). On pw the robots-only period has lasted longer than that.
What this record does not show
- The reason. None of the hypotheses above has been tested.
- More than one site over a few weeks. The numbers are counts, not rates or trends. Your site may differ.
- That zero means never. It only means not by the recording date.
- That pages not fetched are missing from ChatGPT search. If content reaches ChatGPT through GPTBot's crawl or another company's search results, our log does not show it.
- That pages fetched by other bots appear in their search. Fetching, indexing and being cited in an answer are different things.
- Which change did what. We deployed both changes together, once each.
- An independent check. We wrote this and we measured it.
How we measured
- Log: pw runs on Cloudflare Workers and records each request that reaches it (time, path, UA, source IP, status code). It does not record page bodies or form contents.
- IP check: matched against the lists each operator publishes (OpenAI, Parallel Web Systems); only requests from listed addresses are counted. We use dated, saved copies of the lists. KeenableBot alone is counted by the name it gave, because Keenable's list is not in our bot registry yet.
- Excluded: requests during our own trials that put questions to AI apps (Runs), and our scanner's requests.
- Sitemap: pw's
/sitemap.xmlas read on 26 October 2026 15:58 (29 URLs). - Counting: our tool
log-import bot-crawl(code 788c947, bot list bots-2026-10-24). Dates are in Japan time.
If your log shows the same
The order in which we checked. These rule out a block; they do not find the cause.
- Separate the names:
OAI-SearchBot/1.4; robots.txt;andOAI-SearchBot/1.0are checks. Count the page-fetchingOAI-SearchBot/1.4on its own. - Check the IP: count only requests from the IP lists on OpenAI's official page.
- Check what sits in front: make sure robots.txt does not disallow it and that your CDN (Cloudflare or another) does not block it through its AI-bot settings.
This page is part of the test too
After publishing, we will record whether OAI-SearchBot comes to fetch this page and add the result here, including if it does not. Our expectation before publishing is "it will not": on pw, OAI-SearchBot has read nothing but robots.txt.
Records this page uses
knowledge/claims/oai-searchbot-polls-only-robots-on-pw.md(our observation, updated 14 to 26 October)knowledge/claims/agent-search-crawlers-fetch-more-pw-pages-than-oai-searchbot.md(our observation)knowledge/claims/oai-searchbot-follows-links-from-fetched-pages.md(our observation, another site, hypothesis)knowledge/claims/openai-one-crawl-may-serve-search-and-training.md(outside source: OpenAI's official page)knowledge/claims/sitemap-lastmod-used-if-accurate.md(outside sources: Google, Bing; and our observation)knowledge/claims/new-site-oai-searchbot-reads-pages-after-articles.md(outside source: one Zenn article)