Why ChatGPT can’t read your JavaScript site (and how to check in 10 seconds)

Here’s a fact that surprises even experienced developers: most AI crawlers do not execute JavaScript. Googlebot renders JS (eventually, at cost). GPTBot, ClaudeBot, PerplexityBot and friends largely don’t — they read your raw HTML and move on.

What that means in practice

If your site is a classic server-rendered page (WordPress, most e-commerce platforms, anything with real HTML in view-source), you’re fine. If it’s a single-page app — a React, Vue or Angular shell whose HTML is essentially <div id="root"></div> plus a script tag — then to an AI crawler, your site is blank. Not poorly optimized. Blank.

Blank pages don’t get quoted, don’t get cited, and don’t get recommended. You can win every classic SEO metric and still be invisible to the fastest-growing recommendation channel on the internet.

The 10-second check

Paste any URL into our free “Can AI read this page?” checker. It fetches your page exactly the way AI crawlers do — no JavaScript — and shows you the verdict: how many words are actually readable, whether a JS-framework shell was detected, and the first text an AI would see.

If the verdict is bad

• Server-side rendering (SSR) — Next.js, Nuxt, and friends all support it; content arrives in the HTML.
• Static generation for content pages — the blog and marketing pages rarely need to be an app.
• Prerendering as a patch — serve rendered HTML to bots if a rebuild isn’t realistic this quarter.

Then verify the fix with the same checker, and start tracking whether AI actually mentions you — readable is the prerequisite, recommended is the goal.