Uncategorized

JavaScript Rendering and AI Crawlers: What the Evidence Says About Content They Can’t See

A page can look complete in your browser and still arrive nearly empty at a crawler. The public evidence suggests that several AI crawlers read only the HTML a server sends, not what JavaScript builds afterward. For businesses investing in GEO (Generative Engine Optimization, the practice of earning citations in AI answers), that is a technical gap worth ruling out before any content work.

Key Takeaways
  • A December 2024 Vercel and MERJ analysis found that none of the major AI crawlers it tested rendered JavaScript, while Gemini, which uses Googlebot’s infrastructure, did.
  • A January 2026 RESONEO test of eight assistants found ChatGPT, Claude, Gemini and Perplexity fetchers did not execute JavaScript, while Bing Copilot, Grok and DeepSeek did.
  • The two studies measure different bots and different periods, so treat the results as a reason to test your own pages, not as a permanent rule.
  • The check takes minutes: compare what your raw HTML contains with what your browser shows.

Why rendering matters for AI visibility

Client-side rendering: the server sends a minimal HTML shell, and the visitor’s browser runs JavaScript to fetch and display the real content. Server-side rendering: the server sends finished HTML that already contains the text, so no script has to run.

Googlebot has long rendered JavaScript, so many sites built on client-side frameworks rank without trouble. The assumption that every machine reader behaves the same way is where the risk starts.

If an AI crawler does not run scripts, a pricing table, service description or product spec loaded by JavaScript is simply absent from what it reads. A system cannot cite or summarize text it never received. The practical implication is that technical access comes before content quality in any GEO plan.

What the Vercel and MERJ data showed

In a December 17, 2024 analysis, Vercel and the research firm MERJ examined crawler traffic across Vercel’s network over roughly one month. They counted about 569 million GPTBot fetches, 370 million for Claude, 314 million for AppleBot and 24.4 million for PerplexityBot. Googlebot, covering Search and Gemini, made 4.5 billion.

The headline result was that none of the major AI crawlers they tested rendered JavaScript, a list that included OpenAI’s crawlers, ClaudeBot, Meta-ExternalAgent, Bytespider and PerplexityBot. Gemini was the exception because it uses Googlebot’s infrastructure.

One detail is easy to misread. ChatGPT and Claude did download JavaScript files, in 11.50% and 23.84% of their requests respectively, but the analysis found no evidence they executed them. Downloading a script is not the same as running it.

The same analysis reported that 34.82% of ChatGPT’s fetches and 34.16% of Claude’s returned 404 errors, against 8.22% for Googlebot. Stale or broken URLs waste crawler attention, which makes clean internal links and redirects part of the same technical review.

What the 2026 RESONEO test added

In January 2026, the French consultancy RESONEO published a different kind of test. It built a page that placed unique marker strings in 15 locations, including static HTML, delayed JavaScript, fetch() calls, iframes and Shadow DOM, then asked eight assistants to visit it and report which markers they could see.

The test covers only user-triggered fetchers, the bots that run when a person asks an assistant to open a URL. It does not cover the crawlers that build search indexes or training sets. The results are RESONEO’s own and we have not reproduced them.

AssistantExecuted JavaScript in testNotable behavior
ChatGPT (ChatGPT-User)NoRead static HTML, noscript and template content
Claude (Claude-User)NoSame results as ChatGPT
GeminiNoFirst produced content inferred from the URL before fetching
Perplexity (Perplexity-User)NoRead none of the markers, attributed to a header problem
Bing CopilotYesPage timeout of about 53 ms; only agent to read open Shadow DOM and iframes
GrokYesWaited about 2 seconds; read delayed JavaScript and fetch() content
DeepSeekYesTimeout of about 1 second
Google AI ModeNot applicableDoes not fetch live; relies on the Google Search index

The implication is that behavior varies by assistant, and even the ones that execute scripts wait only a fraction of a second to a couple of seconds. Content that loads slowly may still be missed.

What the evidence does not settle

The Vercel data is nearly two years old and measured traffic on one hosting network, so it may not describe the web as a whole. AI vendors change crawler behavior without announcement. We saw one secondary report claiming a change in OpenAI’s rendering but could not confirm it from a primary source, so we left it out.

Neither study measures whether unrendered content reduces citations. Missing text is a plausible cause of lower visibility, but a causal link has not been shown. The right reading is that this is a low-cost risk to eliminate, not a proven ranking factor.

The studies also differ in kind. Vercel observed live crawler traffic, while RESONEO ran a controlled page test on fetchers. Combining them into a single claim about “all AI bots” would overstate both.

How to test your own pages

You do not need a vendor to check this. The sequence below uses tools any developer or technical marketer already has.

  1. Pick five pages that matter commercially: your main service page, pricing, a comparison page and two top articles.
  2. Fetch each page’s raw HTML with a command-line request or the browser’s “view source,” not the inspector, which shows the rendered result.
  3. Search that raw HTML for your key sentences, prices and headings. Note any that are missing.
  4. Repeat with JavaScript disabled in the browser to see the page as a non-rendering reader would.
  5. If critical text is missing, ask your developer about server-side rendering or static generation for those templates.
  6. Review your server logs for AI user agents and check how many of their requests end in 404 or redirects.

This pairs naturally with deciding which bots to admit in the first place, which we cover in our guide to AI crawler access and robots.txt.

Frequently Asked Questions

Do AI crawlers execute JavaScript?

It depends on the crawler. Vercel and MERJ found in December 2024 that the major AI crawlers they tested did not, and RESONEO’s January 2026 test found Bing Copilot, Grok and DeepSeek did while ChatGPT, Claude, Gemini and Perplexity fetchers did not.

Does my site need server-side rendering for AI search?

Only if your important text is loaded by JavaScript. If your raw HTML already contains your key content, you probably do not. Test the raw HTML first, then decide.

Does Google AI Mode read JavaScript content?

RESONEO found that Google AI Mode does not fetch pages live and relies on the Google Search index. Because Googlebot renders JavaScript for indexing, content Google has indexed is the relevant question, not live rendering.

Technical access is the least glamorous part of AI search work and often the cheapest to fix. At Grow with Hafsa we help US and UK teams audit whether their key pages are readable to AI systems before they invest in new content, as part of our AI marketing and search visibility work.

Crawler access is only part of the picture, because blocking a bot may not remove a site from answers either. We cover the evidence in what a 4-million-citation study found about blocking AI crawlers.