How to Check If AI Can Read Your Website
Before any AI engine can cite your website, three things have to be true: its crawler can reach the page, the content renders as readable HTML rather than script-dependent content, and the engine can extract a clean, self-contained answer from it. You can check all three yourself. The most common silent failure is a page whose content only appears after JavaScript runs, or a robots.txt that blocks the AI crawlers — both of which make a perfectly good page invisible to AI with no error anyone notices.
Why "readable to AI" is a separate question from "looks fine to me"
A page can look perfect in your browser and be unreadable to an AI engine, because your browser runs JavaScript, applies styles, and renders the full experience — and an AI crawler often does not. What the engine sees can be a stripped-down version, or an empty shell if the real content loads only after scripts execute. So "my site looks great" tells you nothing about whether AI can read it. You have to check what the crawler sees, not what you see.
There are three gates a page passes before it can be cited: reachability, readability, and extractability. A failure at any one makes the page invisible, and each is checkable.
Check 1 — Can the AI crawlers reach your pages?
Look at your robots.txt (yoursite.com/robots.txt) and confirm it doesn't block the AI crawlers: GPTBot and OAI-SearchBot (ChatGPT), ClaudeBot, Claude-SearchBot and Claude-User (Claude), PerplexityBot (Perplexity), and Google-Extended (Google's AI). A common, costly mistake: a site blocks ClaudeBot to keep its content out of AI training and accidentally blocks the search and fetch crawlers too — making itself uncitable. Also check that a security layer (a firewall or bot-blocking rule) isn't silently blocking these agents; that produces zero visibility with no visible error.
Check 2 — Does your content render without JavaScript?
This is the most common silent failure. To test it: open one of your key pages, view the page source (right-click → "View Page Source", which shows the raw HTML before scripts run), and search for a sentence you know is on the page. If the text is there, the engine can likely read it. If the source is nearly empty and the content only appears in the rendered view, your page is JavaScript-dependent — and an AI crawler may see an empty shell. You can also disable JavaScript in your browser and reload: if the content vanishes, so does it for the engine.
Check 3 — Can the engine extract a clean answer?
Reachable and readable get you considered; extractable gets you cited. Engines prefer content they can lift as a self-contained unit: a direct answer near the top of a section, under a clear heading, backed by specific facts. Check whether your important pages open with the answer or bury it under paragraphs of preamble, whether headings are real questions or vague labels, and whether claims are specific and verifiable rather than vague superlatives. A page that makes the engine hunt for the answer is far less likely to be cited than one that hands it over cleanly. (The AI citation checklist breaks the extractable structure down signal by signal.)
Check 4 — Ask the engines directly
The most direct test: ask each engine to read your page. In ChatGPT, Perplexity, or Claude, paste your URL and ask "what does this page say about [topic]?" If the engine can summarize it accurately, it can read and extract it. If it returns nothing, a generic guess, or an error, that's a reachability or rendering problem worth running down. Do this across engines — because they read differently, a page readable to one may fail on another.
What to fix if AI can't read your site
The fixes map to the failed check. A reachability failure means correcting robots.txt or a firewall rule. A readability failure means server-side or static rendering so content is in the HTML, not script-dependent. An extractability failure means restructuring pages — direct answers up top, question-based headings, specific facts. These are the technical floor of AI visibility; clearing them doesn't guarantee citation, but failing them guarantees its absence. (For how the engines weigh what they can read, see how AI engines choose sources.)
Frequently asked questions
How do I know if ChatGPT can read my website?
Paste your URL into ChatGPT and ask it to summarize the page. If it returns an accurate summary, it can read and extract your content; if it returns nothing or a vague guess, you likely have a reachability or JavaScript-rendering problem. Also confirm GPTBot isn't blocked in your robots.txt.
Why can't AI read my website even though it looks fine in my browser?
Because your browser runs JavaScript and the AI crawler may not. If your content only appears after scripts execute, the crawler can see an empty shell even though the page looks perfect to you. Check the raw page source for your content, not the rendered view.
What is robots.txt and how does it affect AI?
It's a file at yoursite.com/robots.txt that tells crawlers what they can access. If it blocks the AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended), those engines can't read or cite your pages. A common error is blocking a training crawler and accidentally blocking the search crawler too.
How do I test if my page content is JavaScript-dependent?
View the raw page source (right-click → View Page Source) and search for text you know is on the page, or disable JavaScript and reload. If the content is missing from the source or vanishes without JavaScript, it's script-dependent and may be invisible to AI crawlers.
Does my website need to be readable by all four AI engines separately?
Effectively yes — the engines read differently and from different indexes, so a page readable to one can fail on another. Test across ChatGPT, Perplexity, Claude, and Google's AI rather than assuming one result covers all.
How do I get a full read of where my site stands?
A free, PULSE-powered assessment checks your visibility across all four engines and surfaces where you're being missed, query by query — a fuller picture than a single page-read test.
Related guides
- AI citation checklist: 25 signals that matter — the structural signals behind extractability.
- How AI engines choose which sources to cite — what happens after a page is readable.
- Why ChatGPT ignores your website — the deeper diagnosis when a page is readable but still skipped.
- The 7 SIGNALS dimensions — the full model behind AI citation.