Skip to content
Leadee
Free tool

ChatGPT bot access test

Enter a URL and Leadee checks robots.txt for OpenAI's three documented bots — OAI-SearchBot, ChatGPT-User and GPTBot — then live-fetches the homepage with each bot's own user agent (where OpenAI publishes one) to tell a robots.txt rule apart from a firewall or CDN silently blocking the bot. Not affiliated with or endorsed by OpenAI.

Updated

  • No email needed
  • Free, no sign-up

1 of 3 blocked

  • OAI-SearchBot: allowed
  • ChatGPT-User: blocked by firewall (robots.txt allows it)
  • GPTBot: allowed

Example result

Run it now

Leadee is not affiliated with, endorsed by, or sponsored by OpenAI. “ChatGPT”, “GPTBot” and the other names on this page are OpenAI's own, used only to describe what this tool measures.

At a glance

3 items
What it checks
4
Questions answered
No email needed
To get a result
Can AI read my site?
Answers

What does it check?

  • robots.txt rule for OAI-SearchBot

    robots.txt rule for OAI-SearchBot, ChatGPT-User and GPTBot

  • A live fetch with each bot's own user

    A live fetch with each bot's own user agent (OAI-SearchBot, ChatGPT-User), to catch a WAF/CDN block robots.txt would not show

  • Which bot is blocked, and whether the

    Which bot is blocked, and whether the block is robots.txt, a firewall, or neither

What does a result look like?

1 of 3 blocked

  • OAI-SearchBot: allowed
  • ChatGPT-User: blocked by firewall (robots.txt allows it)
  • GPTBot: allowed

Sample from a real run, 10 Nov 2026.

How do I read and fix the result?

A bot blocked by robots.txt is a policy choice you made (or inherited) and is simple to change; a bot blocked by a firewall/CDN even though robots.txt allows it is usually invisible until a live fetch catches it — that row needs an allow-list change at the firewall or CDN, not in robots.txt.

  1. Enter the URL you want to check.

  2. Read the robots.txt verdict and the live-fetch result for OAI-SearchBot and ChatGPT-User.

  3. If a bot is blocked by robots.txt, update the rule; if blocked by a firewall/CDN, allow-list that bot there instead.

  4. Re-run the test after you change anything, to confirm the block is gone.

Who is it for?

An engineer in a hard hat and safety vest reading a tablet on the shop floor

Manufacturers

Product and spec pages AI engines need to parse correctly.

Three consultants reviewing a document on a tablet

Professional services firms

Service pages that need clear Organization and entity markup.

A businessman in a suit shaking hands with a supplier in an office

B2B suppliers

Catalogue and partner pages AI crawlers must be able to read.

What are the limits?

Good to know

What are the limits?

The live fetch spoofs each bot's User-Agent header from Leadee's own server — a real firewall often verifies a bot by IP range instead, so a "not blocked" result here is an indicator, not proof the real bot gets through, and a "blocked" result from an IP-only firewall may not show up here at all. GPTBot is training-only and is not live-fetched (see the FAQ).

Questions

Is this tool affiliated with or endorsed by OpenAI?

No. Leadee is not affiliated with, endorsed by, or sponsored by OpenAI. OAI-SearchBot, ChatGPT-User and GPTBot are OpenAI's own bot names, documented at developers.openai.com/api/docs/bots.

What does each of the three bots do?

OAI-SearchBot crawls to surface sites in ChatGPT's search features. ChatGPT-User fetches a page in real time when a ChatGPT user (or a Custom GPT) asks for it. GPTBot is a training crawler, unrelated to any single live ChatGPT answer — blocking it is a legitimate policy choice, not a visibility problem.

Why is GPTBot not live-fetched like the other two?

GPTBot only trains future models — it is never the bot that fetches a page while answering a live ChatGPT question, so there is no "can it reach me right now" moment to probe; its row only carries the robots.txt verdict.

My robots.txt allows all three bots — why would one still be blocked?

A firewall, CDN or bot-management rule (the kind that blocks "unrecognized" user agents by default) can block a request before it ever reaches the server robots.txt is served from. The live fetch catches that case; the fix is an allow-list rule at the firewall/CDN, not a robots.txt change.

Can GEO guarantee results?

No. AI answer engines change their output frequently, and no vendor — including Leadee — can guarantee a ranking or a mention. Leadee publishes confidence intervals on every metric so you can see how much a result can vary run to run.

How does Leadee measure AI visibility?

Leadee runs your prompt set against each AI engine on a weekly to daily schedule, depending on plan, through official vendor APIs (OpenAI, Gemini, Perplexity, Anthropic, DataForSEO) — never by scraping consumer chat interfaces — and reports mention rate, citation rate, average position, share of voice and sentiment with a 95% confidence interval.

Who do I talk to?

Email support@leadee.ai or use Talk to an expert at https://leadee.ai/contact-sales — the Netbase JSC team behind Leadee replies by email or WhatsApp — or WhatsApp the CEO directly at https://wa.me/84937869689.

Monitor AI bot access on a schedule.

Sign up for a free account to get notified the moment a bot gets blocked, instead of checking by hand.