Is Your Website Blocked From ChatGPT? How to Check GPTBot in robots.txt
ChatGPT reaches websites through three crawlers: GPTBot, OAI-SearchBot and ChatGPT-User. If your robots.txt file disallows any of them, ChatGPT cannot read or cite your pages — no matter how good your content or your Google rankings are. You can check this in under a minute by opening yoursite.com/robots.txt and searching for those names.
What each OpenAI crawler actually does
GPTBot collects content used to train and improve OpenAI's models. Blocking it keeps your content out of training data, which some publishers want, but it also means the model has less grounding in who you are.
OAI-SearchBot powers ChatGPT's search results and citations. This is the one that matters most for visibility: block it and your business cannot appear as a cited source when someone asks ChatGPT for a recommendation.
ChatGPT-User fetches a page in real time when a user asks ChatGPT to look at a specific link. Blocking it means your page fails to load when a potential customer explicitly asks about you.
How to check your robots.txt in 60 seconds
Open your browser and go to yoursite.com/robots.txt. Search the page for GPTBot, OAI-SearchBot and ChatGPT-User. If you find any of them followed by a line reading Disallow: /, that crawler is fully blocked.
Also check the User-agent: * group at the top. Rules there apply to any crawler that doesn't have its own group, so a blanket Disallow: / blocks the AI crawlers too.
Watch for order: a crawler follows the most specific group that matches its name, and ignores the rest. That means an AI-friendly group further down the file will not undo a block if the crawler already matched an earlier, more specific group.
The robots.txt rules that let AI crawlers in
Add an explicit group welcoming the AI crawlers. Being explicit matters: SEO plugins and security tools regularly rewrite robots.txt, and a stated rule survives those rewrites better than an absence of rules.
Add to robots.txt
User-agent: GPTBot User-agent: OAI-SearchBot User-agent: ChatGPT-User User-agent: ClaudeBot User-agent: PerplexityBot User-agent: Google-Extended Allow: / Sitemap: https://yoursite.com/sitemap.xml
Your robots.txt says allow, but AI still can't read you
This is more common than a straightforward block, and it has three usual causes.
Your CDN overrides the file. Cloudflare's AI Crawl Control injects a managed block into robots.txt ahead of your own rules, disallowing GPTBot, ClaudeBot and Google-Extended. Your file says allow; what the crawler downloads says disallow.
Your content requires JavaScript. Most AI crawlers do not execute JavaScript. If your text only appears after a script runs, the crawler receives an effectively empty page. Press Ctrl+U on your own site — that raw HTML is what AI sees.
Your firewall blocks the bot by IP or user agent before robots.txt is ever consulted. Security plugins and bot-protection rules do this routinely, and it is invisible from the file itself.
Frequently asked questions
Does blocking GPTBot hurt my Google rankings?
▾
No. GPTBot is OpenAI's crawler and has no connection to Googlebot or Google's ranking systems. Blocking it only affects whether your content reaches ChatGPT.
Should I allow AI crawlers or block them?
▾
If you want customers to discover you through AI assistants, allow them — being absent from an answer means a competitor fills that space. Publishers whose business model is selling access to their content often choose to block training crawlers while allowing search crawlers like OAI-SearchBot, which is a reasonable middle ground.
How long until ChatGPT sees my site after unblocking?
▾
Crawlers revisit on their own schedule, typically days to weeks depending on how often your site changes and how much authority it has. There is no way to request an immediate recrawl the way you can with Google Search Console.