resulthack

All AI crawlers /

OAI-SearchBot

OpenAI · AI search · robots.txt: Yes

Crawls the web so that pages can be shown as results in ChatGPT's search features.

Block OAI-SearchBot

User-agent: OAI-SearchBot
Disallow: /

Blocking OAI-SearchBot keeps your pages out of ChatGPT search answers, though OpenAI says they can still appear as navigational links. It does not decide whether your content is used for training; that is GPTBot.

Allow OAI-SearchBot

User-agent: OAI-SearchBot
Allow: /

An allow group only changes anything if a broader rule would block OAI-SearchBot. Under the robots.txt standard (RFC 9309, section 2.2.1) a crawler follows the group that names it and uses the User-agent: * group only when no group does — so this group lets it in even if your * group says Disallow: /. Token matching is case-insensitive.

Put these lines in /robots.txt at the root of each host (each subdomain has its own file). robots.txt is a request to well-behaved crawlers, not access control.

Block or allow it at the server

robots.txt asks; a server rule refuses. Every rule here matches OAI-SearchBot, spelled as in the User-Agent OpenAI documents (“OAI-SearchBot/1.4”), and matches it case-sensitively. The server answers 403.

What a User-Agent rule cannot do: any client can send any User-Agent. Access control by User-Agent is an unreliable technique, since the User-Agent header can be set to anything at all, at the whim of the end user. (Apache HTTP Server 2.4 documentation). A fake OAI-SearchBot is refused by the block rule along with the real one, and a crawler that hides its name passes. The “only the real one” rule is the check: it lets the name in only from OpenAI's published addresses.

Your server

To block it: refuse every request that says OAI-SearchBot

In the server block (or a location)

if ($http_user_agent ~ OAI-SearchBot) {
    return 403;
}

To allow only the real one: refuse OAI-SearchBot claims from outside OpenAI's list

In the http block

geo $oai_searchbot_unlisted {
    default 1;
    104.210.140.128/28 0;
    13.66.216.176/28 0;
    135.234.64.0/24 0;
    172.182.193.224/28 0;
    172.182.193.80/28 0;
    172.182.194.144/28 0;
    172.182.194.32/28 0;
    172.182.195.48/28 0;
    172.182.209.208/28 0;
    172.182.211.192/28 0;
    172.182.213.192/28 0;
    172.182.224.0/28 0;
    172.203.190.112/28 0;
    172.203.190.128/28 0;
    172.203.190.80/28 0;
    20.14.99.96/28 0;
    20.168.18.32/28 0;
    20.169.6.224/28 0;
    20.169.7.48/28 0;
    20.169.77.0/25 0;
    20.171.123.64/28 0;
    20.171.53.224/28 0;
    20.25.151.224/28 0;
    20.42.10.176/28 0;
    23.102.145.48/28 0;
    4.227.36.0/25 0;
    40.67.175.0/25 0;
    40.90.214.16/28 0;
    51.8.102.0/24 0;
    74.7.175.128/25 0;
    74.7.228.0/25 0;
    74.7.228.128/25 0;
    74.7.229.0/25 0;
    74.7.229.128/25 0;
    74.7.230.0/25 0;
    74.7.241.128/25 0;
    74.7.242.128/25 0;
    74.7.243.0/25 0;
    74.7.244.0/25 0;
}
map $http_user_agent $oai_searchbot_fake {
    default 0;
    "~OAI-SearchBot" $oai_searchbot_unlisted;
}

In the server block (or a location)

if ($oai_searchbot_fake) {
    return 403;
}

The geo and map blocks go at http level; nginx's docs give Context: http for both, and for if Context: server, location. By default, the address is taken from the $remote_addr variable (nginx documentation).

To block it: refuse every request that says OAI-SearchBot

In the virtual host, a <Directory> block or .htaccess

<If "%{HTTP_USER_AGENT} =~ /OAI-SearchBot/">
    Require all denied
</If>

To allow only the real one: refuse OAI-SearchBot claims from outside OpenAI's list

In the virtual host, a <Directory> block or .htaccess

<If "%{HTTP_USER_AGENT} =~ /OAI-SearchBot/">
    Require ip 104.210.140.128/28 13.66.216.176/28 135.234.64.0/24 172.182.193.224/28 172.182.193.80/28 172.182.194.144/28
    Require ip 172.182.194.32/28 172.182.195.48/28 172.182.209.208/28 172.182.211.192/28 172.182.213.192/28 172.182.224.0/28
    Require ip 172.203.190.112/28 172.203.190.128/28 172.203.190.80/28 20.14.99.96/28 20.168.18.32/28 20.169.6.224/28
    Require ip 20.169.7.48/28 20.169.77.0/25 20.171.123.64/28 20.171.53.224/28 20.25.151.224/28 20.42.10.176/28
    Require ip 23.102.145.48/28 4.227.36.0/25 40.67.175.0/25 40.90.214.16/28 51.8.102.0/24 74.7.175.128/25
    Require ip 74.7.228.0/25 74.7.228.128/25 74.7.229.0/25 74.7.229.128/25 74.7.230.0/25 74.7.241.128/25
    Require ip 74.7.242.128/25 74.7.243.0/25 74.7.244.0/25
</If>

Apache httpd 2.4. Syntax: <If expression> ... </If> Context: server config, virtual host, directory, .htaccess (Apache HTTP Server 2.4 documentation). Several Require ip lines in one block: When multiple Require directives are used in a single configuration section and are not contained in another authorization directive like <RequireAll>, they are implicitly contained within a <RequireAny> directive. (Apache HTTP Server 2.4 documentation)

To block it: refuse every request that says OAI-SearchBot

Inside the site block

@oai-searchbot header User-Agent *OAI-SearchBot*
respond @oai-searchbot 403

To allow only the real one: refuse OAI-SearchBot claims from outside OpenAI's list

Inside the site block

@fake-oai-searchbot {
    header User-Agent *OAI-SearchBot*
    not {
        client_ip 104.210.140.128/28 13.66.216.176/28 135.234.64.0/24 172.182.193.224/28 172.182.193.80/28 172.182.194.144/28
        client_ip 172.182.194.32/28 172.182.195.48/28 172.182.209.208/28 172.182.211.192/28 172.182.213.192/28 172.182.224.0/28
        client_ip 172.203.190.112/28 172.203.190.128/28 172.203.190.80/28 20.14.99.96/28 20.168.18.32/28 20.169.6.224/28
        client_ip 20.169.7.48/28 20.169.77.0/25 20.171.123.64/28 20.171.53.224/28 20.25.151.224/28 20.42.10.176/28
        client_ip 23.102.145.48/28 4.227.36.0/25 40.67.175.0/25 40.90.214.16/28 51.8.102.0/24 74.7.175.128/25
        client_ip 74.7.228.0/25 74.7.228.128/25 74.7.229.0/25 74.7.229.128/25 74.7.230.0/25 74.7.241.128/25
        client_ip 74.7.242.128/25 74.7.243.0/25 74.7.244.0/25
    }
}
respond @fake-oai-searchbot 403

Like directives, named matcher definitions must go inside the site blocks that use them. (Caddy documentation) On client_ip: This matcher is best used when the trusted_proxies global option is configured, otherwise it acts identically to the remote_ip matcher. (Caddy documentation)

To block it: refuse every request that says OAI-SearchBot

Expression of a custom rule; action Block

(http.user_agent contains "OAI-SearchBot")

To allow only the real one: refuse OAI-SearchBot claims from outside OpenAI's list

Expression of a custom rule; action Block

(http.user_agent contains "OAI-SearchBot" and not ip.src in {104.210.140.128/28 13.66.216.176/28 135.234.64.0/24 172.182.193.224/28 172.182.193.80/28 172.182.194.144/28 172.182.194.32/28 172.182.195.48/28 172.182.209.208/28 172.182.211.192/28 172.182.213.192/28 172.182.224.0/28 172.203.190.112/28 172.203.190.128/28 172.203.190.80/28 20.14.99.96/28 20.168.18.32/28 20.169.6.224/28 20.169.7.48/28 20.169.77.0/25 20.171.123.64/28 20.171.53.224/28 20.25.151.224/28 20.42.10.176/28 23.102.145.48/28 4.227.36.0/25 40.67.175.0/25 40.90.214.16/28 51.8.102.0/24 74.7.175.128/25 74.7.228.0/25 74.7.228.128/25 74.7.229.0/25 74.7.229.128/25 74.7.230.0/25 74.7.241.128/25 74.7.242.128/25 74.7.243.0/25 74.7.244.0/25})

Each expression is one custom rule with the action Block (Cloudflare's own example: Expression: (cf.bot_management.score lt 2 and http.user_agent contains "App_Name 2.0") Action: Block).

Addresses in the “only the real one” rules: OpenAI's list openai.com/searchbot.json, 39 ranges, fetched 8 Oct 2026, list dated 2 Jan 2026. Operators change their lists; compare the date with the live list before you rely on it.

The IP rules compare the address your server sees. Behind a CDN or load balancer that is the proxy's address, so every claim would be refused: restore the client address first, or put the rule at the CDN.

Syntax from each server's own documentation, fetched 9 Oct 2026: nginx (rewrite module, map module, geo module); Apache (Access Control, <If>, expressions, mod_authz_core, mod_authz_host); Caddy (request matchers, respond); Cloudflare (custom rule example, operators, values and lists, http.user_agent). Every line form above is listed with its quote in server-rules-sources.json.

Who blocks it

Of the 1,000 most-visited domains on Tranco list PY35J (generated 2026-10-08), we read 508 robots.txt files on 2026-10-09 and ran each through the same RFC 9309 matcher as the checker, for the path /. 33 block OAI-SearchBot from the whole site by name, 24 block it through their User-agent: * group, and 37 name it with partial rules (some paths closed, the home page open). 15 more name it only to let it in.

33

block it by name 6.5%

24

block it through * 4.7%

37

name it, partial rules 7.3%

Percentages are of the 508 files we could read, not of all 1,000 sites.

Highest-ranked sites that block OAI-SearchBot by name

  1. amazon.com rank 27
  2. tiktok.com rank 58
  3. msn.com rank 72
  4. nytimes.com rank 157
  5. cnn.com rank 205
  6. bbc.com rank 221
  7. bbc.co.uk rank 230
  8. launchpad.net rank 284
  9. weibo.com rank 311
  10. amazon.co.uk rank 336

Each links to the site's live robots.txt, which may have changed since 2026-10-09.

robots.txt is only what a site asks for. A site can also turn a crawler away at its firewall or CDN, or let an operator in under a licensing deal, and neither shows in its robots.txt. A block through * stops every crawler the file does not name, so it says nothing about this one in particular. The files we could not read are not counted: 222 of the 1,000 domains are infrastructure names with no website at the bare domain (CDN and DNS zones, for example), 59 answered our request with 401 or 403, 93 failed (timeout, TLS or server error), 59 have no robots.txt (404 and similar) and 59 answered with an HTML page instead of a robots.txt file. Every agent's count, side by side.

Facts

Operator
OpenAI
Purpose
AI search index
Obeys robots.txt
Yes. OpenAI documents OAI-SearchBot as a robots.txt token and says a robots.txt change can take about 24 hours to reach its search systems.
In your server logs
The user-agent string contains "OAI-SearchBot/1.4" (the version number may change); requests for robots.txt may carry an extra "robots.txt" marker.
How to verify it
Match the request's IP address against OpenAI's published OAI-SearchBot IP list. OpenAI recommends allowing requests from these ranges if you want to appear in ChatGPT search.

Published list: openai.com/searchbot.json — 39 IPv4 ranges when we fetched it, list dated 2 Jan 2026. Always match against the live list; operators update them. To count real and fake OAI-SearchBot requests in your own server log against this list, drop the log into the log reader.

What OpenAI says

Quoted word for word from the operator's documentation.

“OAI-SearchBot is for search. OAI-SearchBot is used to surface websites in search results in ChatGPT’s search features.”

“Sites that are opted out of OAI-SearchBot will not be shown in ChatGPT search answers, though can still appear as navigational links.”

“To help ensure your site appears in search results, we recommend allowing OAI-SearchBot in your site’s robots.txt file and allowing requests from our published IP ranges below.”

“For search results, please note it can take ~24 hours from a site’s robots.txt update for our systems to adjust.”

“Chrome/131.0.0.0 Safari/537.36; compatible; OAI-SearchBot/1.4; robots.txt;”

“Each setting is independent of the others”

Sources

Other crawlers from OpenAI

Same purpose, other operators

← All 49 AI crawlers

Made with AI tools. · Privacy