Standard Definition
Server-Side Rendering (SSR) refers to the architecture in which the HTML content of a web page is generated on the server and delivered as finished HTML to the user's browser. The browser thus receives the complete content on first request — in contrast to the Single-Page Application architecture, in which the browser initially receives an almost empty HTML shell plus JavaScript and renders the content client-side. SSR is established web architecture since the 2000s (classically with PHP, Ruby, Python, Java), in the modern JavaScript world implemented through frameworks like Next.js, Nuxt, Remix, SvelteKit, Astro, and since 2024 TanStack Start. Follow-up interactions on the page can become interactive after initial render through hydration.
What this means in mandate practice
SSR has become the practical standard in modern web development — for three structural reasons.
First, search engine crawlers see full content on first crawl with SSR. Googlebot now renders JavaScript, but with delay of days to weeks — which substantially slows indexing speed. With Single-Page Applications without SSR, content is often only fully indexed after several weeks; some AI crawlers don't process JavaScript at all. SSR structurally bypasses this problem.
Second, performance perception is better. SSR pages show content at First Paint — users immediately see what the page contains. SPA pages often show a loading spinner for weeks until JavaScript is loaded and executed. This affects both user engagement and Core Web Vitals metrics like LCP (Largest Contentful Paint).
Third, AI search systems structurally work better with SSR. ChatGPT Search, Claude Web, Perplexity draw content from the server's first HTML response. SPA sites without SSR are often invisible to these systems — even though Googlebot now processes JavaScript. Calvarius has carried out several mandate migrations from SPA to SSR since 2024 — typical observation: AI search system visibility begins 4-8 weeks after SSR migration; classical Google visibility improves substantially in 2-6 months. Migration effort varies strongly: for a site with 10-15 routes typically 12-25 hours, for larger sites correspondingly more.