Is Your Website Blocking ChatGPT? How to Fix It

How ChatGPT actually reads your website

ChatGPT builds local answers from the open web plus some licensed sources like Yelp. To read the open web, OpenAI uses a few different bots. Each one has a job, and they follow different rules. This matters because you can accidentally block the one that feeds ChatGPT search while leaving the others alone.

Here are the three OpenAI bots that matter most, straight from OpenAI's own crawler documentation.

If you want the deeper comparison of ChatGPT against your other listings, see ChatGPT Hub vs GBP, Yelp, Bing, and Apple.

Problem 1: Your robots.txt is blocking OpenAI's bots

Your robots.txt is a small text file at the root of your site. It tells bots what they can and cannot visit. A lot of sites ship with rules that block AI bots, often added by a plugin, a theme, or a well-meaning web person who read a scary article about AI scraping.

How to check it in 30 seconds

• Open a browser and go to your domain followed by /robots.txt. For example, yoursite.com/robots.txt
• Look for any lines that mention OAI-SearchBot, GPTBot, or ChatGPT-User
• Also look for a blanket rule like User-agent: * followed by Disallow: /, which blocks everyone from everything

What a blocking rule looks like

If you see something like this, OAI-SearchBot is blocked and you are invisible to ChatGPT search:

• User-agent: OAI-SearchBot
• Disallow: /

What to change it to

You want OAI-SearchBot and ChatGPT-User allowed. The simplest safe setup is to make sure there is no Disallow rule aimed at them, and no site-wide Disallow: / that catches everyone. If you want to opt out of AI training but stay visible in search, you can block only GPTBot:

• User-agent: GPTBot
• Disallow: /
• User-agent: OAI-SearchBot
• Allow: /
• User-agent: ChatGPT-User
• Allow: /

For a full walkthrough of common blocking setups, I wrote more in Is Your Website Blocking ChatGPT and the related verification fixes in ChatGPT Verification Problems and Fixes.

Problem 2: Your site only shows content after JavaScript runs

This is the sneaky one. Your site looks perfect to you and your customers. But a lot of modern sites, especially ones built with page builders or app-style frameworks, send a nearly empty page first and then fill it in with JavaScript once a browser runs the code. People do not notice because browsers run that code instantly.

Bots are different. The safe working assumption today is that ChatGPT reads the raw HTML your server sends and not much more. OpenAI's search bot has shown some signs of running JavaScript on some pages, but it is inconsistent, and the training crawler GPTBot has been found not to run JavaScript at all. So if your services, service areas, and phone number only appear after scripts run, ChatGPT may see a blank or thin page.

How to test it yourself

• Open your home page and a key service page in a browser
• Right-click and choose View Page Source (not Inspect, that shows the rendered version)
• Use Find on the page and search for your phone number, your main service, and a city you serve
• If you cannot find that text in the raw source, ChatGPT probably cannot either

How to fix it

The goal is to get your important content into the HTML the server sends, before any JavaScript runs. This is called server-side rendering or prerendering. How you do it depends on your platform:

• WordPress with a normal theme: usually fine already. Check anyway.
• Wix, Squarespace, GoDaddy builders: mostly server-rendered, but test your key text as above.
• React, Next.js, or a custom app-style site: ask your developer to enable server-side rendering or static rendering for your public pages.
• If none of that is possible fast, at minimum put your phone number, services, and service areas in plain HTML text on the page, not inside images or scripts.

A simple do-this-now checklist

Here is the order I use when a home service site is not showing up right in ChatGPT. Do these in sequence and you will catch most problems.

• Step 1: Open yoursite.com/robots.txt and confirm OAI-SearchBot and ChatGPT-User are not blocked. Remove any Disallow: / aimed at them or at everyone.
• Step 2: View Page Source on your home page and top service page. Confirm your phone number, services, and cities are in the raw text.
• Step 3: Run your site through the readiness checker to confirm.
• Step 4: If you already claimed your profile, re-check your info. If you have not, start with How to Claim Your Business in ChatGPT.
• Step 5: Give it time. Bots re-crawl on their own schedule. There is no verified button that forces an instant re-read, so do not expect same-day results.

What this does not fix (and what to check next)

Unblocking your site is necessary, but it is not the whole game. If ChatGPT can read your page and still says little about you, the problem is usually that there is not much for it to find across the web, or your details do not match from place to place.

Other things ChatGPT leans on

• Yelp and other licensed sources. ChatGPT pulls from these for local answers, so a thin or wrong Yelp page hurts. See Does ChatGPT Use Yelp.
• Consistent name, address, and phone number everywhere. Mismatches confuse the answer.
• Clear service and city pages. If you are a service area business, read Can a Service Area Business Claim ChatGPT.
• Your mentions and clicks in the Hub, once you claim. I explain those numbers in ChatGPT Mentions and Clicks Explained.

Think of it like this. Fixing robots.txt and rendering opens the door. The content across the web decides what ChatGPT says once it walks in.

Frequently asked questions