What Is Client-Side Rendering (CSR)? The AI Visibility Blind Spot

Client-side rendering (CSR) is the architecture in which the server sends a minimal HTML shell plus a JavaScript bundle, and the browser executes that JavaScript to build the actual page content. It became the default output of single-page-application frameworks in the 2010s — and it is the single largest technical cause of AI invisibility today, because the machines reading the web on behalf of answer engines do not run JavaScript.

Which crawlers execute JavaScript?

The rendering capability table is short and lopsided:

Everything below the second row consumes raw HTML. A pure CSR page therefore exists for Google, marginally for Bing, and not at all for the crawlers behind ChatGPT, Claude, and Perplexity answers.

How do you test for the gap?

Three methods, from fastest to most thorough. First, curl https://yoursite.com/page and search the output for a sentence you can see in the browser — absence means CSR blindness. Second, use browser view-source (which shows the delivered HTML) rather than DevTools' Inspect panel (which shows the JavaScript-built DOM); the difference between the two is exactly what bots miss. Third, crawl the site twice with a tool like Screaming Frog, once with JavaScript rendering on and once off, and diff the extracted content — the delta is your at-risk inventory.

What are the remediation paths?

The durable fix is moving public pages to server-side rendering or static generation, which frameworks like Next.js and Nuxt support route-by-route, so the migration can start with the highest-value templates. The retrofit fix is prerendering — serving bots a pre-executed HTML snapshot — which works but adds an infrastructure dependency. Either way, the goal is measurable: the raw HTML response for every page you want cited by AI engines must contain its full content. Google's JavaScript SEO guidance frames rendering as a two-wave process even for Googlebot; for AI crawlers there is no second wave.