Is your website invisible to ChatGPT? The JavaScript problem, explained

Short answer

If your website's words only appear after JavaScript runs, many AI assistants never see them. Independent tests in 2026 found ChatGPT, Claude, Perplexity and Copilot read the HTML your server sends and stop. Google renders JavaScript, so a site can rank in Google and still look empty to ChatGPT. The fix is to put your important text in that first HTML response.

Close-up of a computer screen showing lines of HTML code in orange and yellow on a dark background
Photo: Pixabay on Pexels

Key takeaways

  • In 2026 tests, ChatGPT, Claude, Perplexity, Gemini (reading a pasted link), Meta AI and Copilot all read the raw HTML of a page and ignored what JavaScript added.
  • Google's own crawler renders JavaScript, so a page can rank in Google and still look empty to ChatGPT.
  • What ChatGPT sees is roughly what you see in View Page Source, not what you see on screen.
  • One site owner reported OpenAI's crawlers starting to render pages on 25 September 2026. OpenAI hasn't announced it, so don't rely on it.
  • The fix is server-side rendering or static pages, which Google also recommends because not all bots can run JavaScript.

Picture a café owner in Stockton who paid for a slick new website last year. It looks lovely: the menu fades in, the opening times slide up, the reviews scroll past. A friend asks ChatGPT what time the café opens on Sundays, and ChatGPT says it can’t find opening hours on the site. The hours are right there on the screen. ChatGPT just never saw them.

This happens more than most owners realise, and the reason is surprisingly simple. A log study published in September 2026 found that ChatGPT’s page reader visited one news site 37,045 times in a month and fetched not one script file while doing it. Anything that relied on JavaScript to appear simply wasn’t there for it.

Why can’t ChatGPT see my website?

Usually because your words are added by JavaScript after the page loads, and most AI assistants don’t run JavaScript. When any visitor asks for a web page, the server sends back HTML: the text and tags that make up the page. On many modern sites that first HTML is a near-empty shell, and a script then fetches and paints in the real content. Your browser runs that script, so you see the finished page. Most AI assistants read the shell and leave.

The best known evidence for this started with a Vercel and MERJ analysis in December 2024, which found that none of the major AI crawlers it measured, including OpenAI’s, Anthropic’s and Perplexity’s, rendered JavaScript. ChatGPT and Claude’s crawlers did download script files, but they read them as text rather than running them.

That study is nearly two years old, so it’s fair to ask whether anything has changed. Two independent tests this year say: not much.

What do the 2026 tests show?

They show the major American AI assistants still read raw HTML. In June 2026, Search Engine World built a page where a fake “decoy” number sat in the HTML and the real number only appeared once JavaScript ran. They pasted the link into 12 assistants and checked their server logs. ChatGPT, Claude, Gemini, Perplexity, Meta AI and Microsoft Copilot all reported the decoy, meaning they read the HTML and ignored the script. Grok ran the script on one server but still answered from the HTML. Only the Chinese assistants and Mistral reported the real number.

In September 2026, Forge went through a month of server logs for a news site, nearly 2.5 million requests. ChatGPT-User, Claude-User and PerplexityBot fetched no scripts at all while loading pages. Googlebot, Applebot and, occasionally, Bingbot did. Forge’s rule of thumb is a good one to remember: what ChatGPT sees is “view page source”, not what you see on screen.

If a sentence isn’t in your page source, assume ChatGPT has never read it.

Is this changing?

Possibly, for OpenAI’s background crawlers, but nothing is confirmed. A developer reported on 30 September that OpenAI’s search crawler, OAI-SearchBot, and its training crawler, GPTBot, started rendering JavaScript on their sites on 25 September 2026. They checked the requests against OpenAI’s published IP addresses, which makes the report credible. But it comes from one server’s logs, the author found no announcement, and OpenAI’s own crawler documentation says nothing about JavaScript either way.

Even if it’s true, it covers only part of the picture. The reader that fetches a page when someone asks ChatGPT a question in the moment, ChatGPT-User, showed no sign of running scripts in the tests above. Claude, Perplexity and Copilot haven’t been reported to change. So the safe plan hasn’t moved: get your words into the first HTML.

Why does my site rank in Google but not show up in ChatGPT?

Because Google renders JavaScript and most AI assistants don’t. Google’s JavaScript guide explains that Googlebot queues pages for rendering, then runs them in a headless version of Chrome before indexing what appears. Google’s AI Overviews and AI Mode work from that rendered index, so your JavaScript content can reach them.

ChatGPT, Claude and Perplexity build their answers differently. They run their own searches and read pages with their own bots, and those bots take the HTML and stop. So the same page can be visible in Google’s AI answers and blank in ChatGPT’s. Google itself says server-side rendering is still a great idea because “not all bots can run JavaScript”.

How can you check whether your site has this problem?

You can check it yourself in about two minutes, without any technical tools.

  1. Open your most important page in Chrome or Edge: usually your home page and your main service page.
  2. Right-click and choose View Page Source. On a Mac in Safari, turn on the Develop menu first in Settings, Advanced. A new tab opens full of code. Don’t panic; you’re only searching it.
  3. Press Ctrl+F (Cmd+F on a Mac) and search for a sentence you can see on the page, such as your opening line, your phone number or your opening hours.
  4. If it’s found, good. That text is in the HTML, and AI assistants can read it.
  5. If it isn’t found, that text is being added by JavaScript. Most AI assistants won’t see it.
  6. Repeat for the facts that matter most: what you do, where you do it, prices if you show them, opening hours, and your reviews.

For a quicker answer across the whole page, run a free Spyglo check. One of its checks counts the words readable without JavaScript and tells you in plain English if your page is mostly empty without it.

What should you do if your words only appear after JavaScript?

Move your important content into the HTML the server sends. How you do that depends on how the site was built.

  1. Ask your developer one question: “Is our main content server-side rendered or statically generated?” If the answer is “client-side only”, you’ve found the problem.
  2. For sites built with React, Vue or Angular, the usual fix is server-side rendering (SSR) or static site generation (SSG). Frameworks like Next.js, Nuxt and Astro do this as standard. The page is built on the server, so the full text arrives in the first response, and the JavaScript adds the interactive bits afterwards.
  3. For site builders and themes, check whether a particular section, slider or plug-in is loading text with JavaScript. Often the core page is fine and only a fancy reviews widget or animated block is the problem. Replacing that one element can fix it.
  4. Keep the important facts in plain text. Business name, what you do, your area, contact details and opening hours belong in ordinary HTML text, not inside images, animations or embedded widgets.
  5. Use JavaScript for extras, not essentials. Vercel’s advice was to keep main content, titles, descriptions and navigation server-rendered, and save client-side scripts for things like live chat, view counters and social feeds.
  6. Be wary of serving bots a separate version. Google now describes dynamic rendering as a workaround, not a long-term solution, and recommends server-side rendering, static rendering or hydration instead.

None of this is exotic. A lot of the web has always worked this way, and plain HTML pages tend to load faster for people too.

Does this matter for a small local business?

Yes, more than for most. When someone asks an AI assistant “who’s a good electrician near me” or “is the café on the high street open on Sunday”, the assistant has to read something about you to answer. If your site’s text is invisible to it, the assistant falls back on whatever else it can find, such as directory listings and reviews, or names a competitor whose site it could read.

It’s also one of the cheaper problems to fix. Unlike reputation, which builds over months, this is usually a one-off technical change. Once it’s done, every AI bot that visits can read your pages from then on.

We’ve written more about what else AI assistants look for in our guide to getting your business recommended by ChatGPT, and the basics of what GEO is.

How do you know if the fix has worked?

Repeat the View Page Source test after the change: every key sentence should now be found. Then give the bots time. Fixes can be picked up as soon as crawlers revisit, often within days or weeks.

After that, test the assistants themselves. Paste your page link into ChatGPT, Claude and Perplexity and ask a specific question whose answer is only on that page, such as your Sunday opening time or a particular service. If they answer correctly, they can read it. Because AI answers vary each time, ask more than once and check again each month rather than judging on a single try.

The bottom line

Your website has two audiences now: people with browsers and AI assistants without them. Google bridges the gap by rendering JavaScript. ChatGPT, Claude, Perplexity and Copilot, by the best evidence available in October 2026, mostly don’t. Two minutes with View Page Source will tell you which side of that line your site sits on, and if your words aren’t there, the fix is well understood and usually a one-off.

See where your site stands

Spyglo checks your website the way Google and AI assistants see it, with an SEO score and a GEO score and the biggest thing to fix first. Free, in about a minute.

Check my site free

Questions people ask

Can ChatGPT read JavaScript websites?

Mostly not, as of October 2026. Independent tests found ChatGPT reads the HTML your server sends and does not run the scripts that add content afterwards. One site owner reported OpenAI's crawlers starting to render pages in late September 2026, but OpenAI hasn't confirmed it.

Does Google see JavaScript content?

Yes, usually. Google renders pages in a headless Chrome browser before indexing them, and its AI Overviews and AI Mode work from that index. Google still recommends server-side rendering because it's faster and not all bots can run JavaScript.

Are Wix and Squarespace sites invisible to AI?

Not necessarily. It depends on how each page is built, not just the platform. The only reliable answer is to test: open View Page Source on your key pages and search for a sentence from the page. If it's there, AI assistants can read it.

Should I use dynamic rendering to show bots a different version?

Google now calls dynamic rendering a workaround, not a long-term solution. It recommends server-side rendering, static rendering or hydration instead, so bots and people get the same HTML.

Sources

  1. Forge (2026). Can AI crawlers run JavaScript? What ChatGPT-User really sees on your page. https://www.forgeaibotlog.com/articles/can-ai-crawlers-execute-javascript/
  2. Search Engine World (2026). Do AI assistants actually render your JavaScript when grounding? We put it to the test. https://www.searchengineworld.com/do-ai-assistants-actually-render-your-javascript-when-grounding-we-put-it-to-the-test
  3. Vercel and MERJ (2024). The rise of the AI crawler. https://vercel.com/blog/the-rise-of-the-ai-crawler
  4. Google Search Central (2026). Understand JavaScript SEO basics. https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics
  5. Google Search Central (2026). Dynamic rendering as a workaround. https://developers.google.com/search/docs/crawling-indexing/javascript/dynamic-rendering
  6. OpenAI (2026). Overview of OpenAI crawlers. https://developers.openai.com/api/docs/bots
  7. Hisashi Space (2026). Traffic from ChatGPT jumped! Is it because its crawlers now run JavaScript? https://dev.to/hisashispace/traffic-from-chatgpt-jumped-is-it-because-its-crawlers-now-run-javascript-5961

Free tools to put this to work

More from Spyglo