SquishPixel Blog · SEO · Web performance · Browsers

Most AI crawlers do not run JavaScript, so client-side content can be invisible to them

DEV Community published an article on how JavaScript affects what crawlers see. Pages built with React, Vue or Angular can look complete in a browser yet arrive almost empty if the content is added by JavaScript after the page loads. This is client-side rendering. With server-side rendering, the content is already in the HTML the server sends.

Google runs JavaScript with an evergreen version of Chromium, so it sees the finished page. The article says the old worry that JavaScript harms Google SEO is out of date. OpenAI, Anthropic and Perplexity document their crawlers, but according to the article none states whether they execute JavaScript.

The article points to measurements. In December 2024, Vercel and MERJ analysed network logs and found that none of the major AI crawlers they tested rendered JavaScript. ChatGPT's and Claude's crawlers downloaded JavaScript files but did not run them. The article notes that Vercel sells hosting built around server-side rendering. It also says Gemini and AppleBot do render, as does Bing.

In August 2025, Glenn Gabe tested a fully client-side-rendered site. ChatGPT said it could not read the page because it relied on JavaScript. Perplexity failed to find the content on every URL tested, and Claude reported no visible content. Control pages without JavaScript worked on all three. The article's advice is to put the main content, metadata, links and structured data in the initial HTML, and to avoid serving bots a separate version of the page, which Google has deprecated.

Why it matters

A site can rank well in Google and still be unreadable to the AI tools that might quote it. The article says this affects structured data too: JSON-LD (a code format that describes a page to machines) injected by JavaScript is invisible to crawlers that do not run scripts.

The article stresses that this is measured behaviour, not published policy, so it could change. The practical rule is that what you want quoted should be in the HTML your server sends. Interactive extras can stay client-side.

Source: DEV Community. This brief summarises their reporting; read the original for the full detail.