Troubleshooting guide
Why ChatGPT Can't See Your Website: 6 Technical Causes
When ChatGPT or another AI tool cannot see your website, the cause is usually technical: robots.txt blocks the bot, a firewall refuses it, the content only appears after JavaScript runs, or the page is marked noindex. Work through six causes in order and test each one.
Separate Two Problems First
There are two different problems: the AI cannot reach your page, or it can reach it but does not choose to mention you. This guide covers the first, which is technical and fixable. Whether an AI recommends you also depends on your content, reputation and what it knows, and no tool can promise a mention.
The Six Technical Causes
| Cause | What happens | How to check |
|---|---|---|
| robots.txt blocks the bot | The bot reads your rules and stays away | Open /robots.txt and look for Disallow rules for AI bots. See [robots.txt for AI bots](/geo/robots-txt-ai-bots) |
| Firewall, CDN or host block | The server answers 403 or 429, or a challenge page, even though robots.txt allows the bot | Test as the bot. See [Cloudflare blocking AI bots](/geo/cloudflare-blocking-ai-bots) |
| Content needs JavaScript | Some crawlers read the raw HTML only, so a page that fills in after scripts run looks empty | View the page source and search for your text |
| noindex or canonical issues | The page tells search systems to leave it out | Check the robots meta tag and X-Robots-Tag header |
| Login, cookie or popup wall | The bot lands on a gate instead of your content | Open the page in a private window |
| Slow or failing server | Timeouts and errors mean the bot gives up | Check the status code and response time |
The JavaScript Problem in Plain Words
If you right-click your page, choose View Source and cannot find your main text in it, a crawler that does not run JavaScript will not find it either. Some bots may render pages and some do not, and vendors do not always say which, so the safe approach is to make the important content available in the HTML the server sends. Server-side rendering or pre-rendering does this.
Test All Six in One Run
The free GeoLint audit tests the first five at once: it reads robots.txt for each AI search bot, requests your page as each bot, loads it with and without JavaScript and checks noindex signals. How GeoLint works explains the checks.
After fixing, give crawlers time. Even when the page is reachable, it can take a while before a change shows up in AI answers, and nobody can guarantee a mention. If you want help, see the done-for-you fix. To learn the wider topic, read what GEO is.
ChatGPT and Your Website: Common Questions
Why does ChatGPT say it cannot access my website?
The page may be blocked by robots.txt, refused by a firewall or CDN, or hidden behind a login. It may also load slowly or fail. Test the page as an AI bot to see which one applies.
Is my site invisible to ChatGPT if it is built with React or another JavaScript framework?
Not necessarily, but content that only appears after scripts run is a risk for crawlers that read raw HTML. Server-side rendering or pre-rendering removes the risk.
Do I need an llms.txt file to be seen?
No. It is an optional convention, not a switch that makes AI tools see you. Access, readable HTML and useful content matter more. See the [llms.txt guide](/geo/llms-txt).
How long until ChatGPT shows my site after I fix this?
Nobody can promise a time. Fixing access removes a blocker. Whether and when an AI tool mentions you depends on its own indexing and on your content.
Check your own website for free
GeoLint asks each AI search bot for your page, loads it with and without JavaScript and shows what is blocking you. It is free, needs no signup and takes about 20 seconds.