Can AI assistants read a JavaScript website?

Why it matters

Many modern websites send a nearly empty page and build the content in the browser with JavaScript. A person never notices. A crawler that does not run the scripts sees a page with a menu, a cookie banner and little else.

Google renders pages with a full browser, so a JavaScript site can rank well in Google and still be hard for AI assistants to read. A large analysis of crawler traffic published by Vercel in 2024 found that OpenAI’s and Anthropic’s crawlers downloaded JavaScript files but showed no sign of running them. Crawlers change, so treat this as the current picture, not a permanent rule.

What tends to go missing

• Product and service descriptions loaded from an API after the page opens.
• Prices, opening hours and contact details filled in by scripts, which is a common problem for webshops in ChatGPT.
• Tabs, accordions and “read more” sections whose text is not in the HTML until someone clicks.
• Links that only exist as JavaScript click handlers, so crawlers cannot follow them to your other pages.

How to check your own site

1. Open an important page, right-click and choose “View page source” (not “Inspect”).
2. Search the source for a sentence from the page and for your price or phone number.
3. If you cannot find them, a crawler that does not run JavaScript cannot either.

You can also turn off JavaScript in your browser and reload the page. What is left is roughly what these crawlers see.

What to do about it

• Ask your developer for server-side rendering or static generation of the pages that matter, so the content is in the HTML from the start. Most modern frameworks support it.
• Put the key facts in plain HTML text: what you do, for whom, where and what it costs.
• Use ordinary links between pages.
• Make sure the crawlers are allowed in robots.txt in the first place.

Once the content is readable, test your key questions in the assistants again to see whether the answers change.