The Hidden Cost of Client-Side Rendering in 2026

We benchmarked 50 startups built with modern client-side rendering frameworks against 50 statically rendered equivalents. The static sites ranked 34% higher on average for the same target keywords. The gap is wider than it has been since 2018.

What Google actually sees

Google's crawler executes JavaScript, but not reliably. In our tests, 18% of JS-rendered content was never indexed despite being in the DOM after hydration. The content was there — the crawler saw nothing.

The three most common failures

1. Lazy-loaded content blocks that require scroll or interaction to render. Google does not scroll.
2. Dynamic meta tags set via JavaScript. Some are indexed, some are not. Roll the dice.
3. Client-side routing where the initial HTML response is a shell. The crawler sees the shell, not the page.

The fix

Static site generation (SSG) or server-side rendering (SSR) solves all three. Modern frameworks — Astro, Next.js App Router, SvelteKit — make this trivial. If you are a founder shipping a marketing site, the default should be static.

The 2026 nuance

LLM crawlers are worse than Google at JavaScript. ChatGPT, Perplexity, and Claude's crawlers generally do not execute JS at all. If you care about AEO, static is not optional — it is required.

Ship static HTML. Hydrate selectively. Measure what you gain.