Site blocking ChatGPT: how to tell if it's happening to you

If you're wondering whether your site is blocking ChatGPT without you knowing it, you're not alone. Many professionals discover by chance, perhaps by searching for their own business on ChatGPT, that their site is never mentioned. And often the reason isn't the quality of the content, but a line of code forgotten years ago.

Imagine asking an AI assistant: "check if my site blocks ChatGPT bots". That's exactly the right question to ask, because the answer can be found in a few minutes, without advanced technical skills. You just need to know where to look.

Why a site can block ChatGPT without the owner knowing

The most common case is this: the site was built by an agency or with a WordPress theme that, out of caution or by mistake, set overly restrictive rules in the robots.txt file. Other times it's a security plugin that automatically blocks any bot not recognised as Google. In both cases, the result is the same: the systems powering ChatGPT, Perplexity or Gemini can't read the pages, and so can never cite you as a source.

How to check your site's robots.txt

The robots.txt file is the first place to check. It's always found at the same address: just type your domain followed by "/robots.txt" in the browser bar. For example, if your site is www.yoursite.com, you'll go to www.yoursite.com/robots.txt.

Once the page is open, look for lines containing names like these:

• GPTBot (OpenAI's crawler, used for ChatGPT)
• ChatGPT-User (another agent linked to OpenAI)
• Google-Extended (relates to Gemini and Google's AI products)
• PerplexityBot (Perplexity's crawler)
• CCBot (used for some training datasets)

If next to one of these names you find "Disallow: /", it means you're blocking that bot across the whole site. If instead you see "Allow: /" or the bot's name doesn't appear at all, there are generally no explicit blocks.

A practical example of a GPTBot block in robots.txt

Here's what a typical block against GPTBot looks like:

• User-agent: GPTBot
• Disallow: /

These two lines alone prevent ChatGPT from reading any page on the site. It often happens that they were added automatically by a theme or plugin without anyone noticing.

Is robots.txt enough to be sure you're not blocking AI bots?

No, and this is a point that causes confusion. The robots.txt file is only the first level of control. There are other ways a site can block AI bots without them appearing in that file:

• Server-level or firewall rules (often set by the hosting provider)
• Security plugins that block unknown user-agents before they even reach robots.txt
• CDNs like Cloudflare, which can have specific settings to block AI crawlers, separate from robots.txt

For this reason, if you want to be one hundred percent sure, it's worth also checking your Cloudflare panel (if you use it) and asking your hosting provider whether any firewall rules against AI bots are active. If you want to understand in more depth how the relationship between your site and ChatGPT works, this guide to ChatGPT designed for non-technical readers may help.

What to do if you discover you're blocking AI bots

If you find blocking lines you no longer want, the fix is almost always simple: just edit the robots.txt file, removing the "Disallow" lines relating to the bot you want to let in, or replacing them with "Allow: /". If the file is generated automatically by a plugin, the change needs to be made in the plugin's own settings, not by hand.

Before making changes, though, it's also worth asking the opposite question: are you sure you want all AI bots to read your site? For a local business that relies on direct bookings, for example, the choice may be different from that of a business aiming to be cited as a source in AI-generated answers. There's no one-size-fits-all answer, but it's a decision that should be made consciously, not by accident.

Is blocking AI bots always the wrong choice?

Not necessarily. Some sites choose to block specific bots for reasons related to content, intellectual property or business considerations. That's a legitimate choice. The problem arises when the block isn't a choice at all, but an unwanted side effect of a theme, a plugin, or a configuration inherited from whoever built the site years ago. The difference lies entirely in awareness: knowing what you're blocking and why.

A periodic check is worth doing

The robots.txt file can change without warning, for example after a theme update, a hosting migration, or the installation of a new security plugin. That's why an occasional check, perhaps every time you make a major change to the site, helps avoid surprises. If you want to better understand the overall approach for assessing your site's visibility in traditional search engines and AI systems, you can check the methodology page or browse the other articles in the blog.