Server-Side Rendering (SSR)

Server-side rendering (SSR) is a technique where the server builds the full HTML of a page and sends it complete to the browser or crawler, rather than relying on the client to construct it with JavaScript.

In a client-side rendered application, the server sends a near-empty HTML shell plus JavaScript, and the browser runs that code to fetch data and assemble the visible page. With server-side rendering, the work happens on the server first: it runs the application, produces the finished HTML with content already in place, and delivers that. The page is meaningful the moment it arrives, before any JavaScript executes.

This matters for SEO because of how crawlers handle JavaScript. Google can render JavaScript through its Web Rendering Service, but rendering is a second, deferred pass that costs time and resources, and other crawlers and AI systems may not execute JavaScript at all. When the HTML already contains your content, every consumer sees it immediately and reliably, with no dependence on a rendering step that might be delayed or skipped. SSR also tends to improve perceived load speed, which helps Core Web Vitals.

Server-side rendering is one of several approaches to the same goal of giving bots real HTML. Related patterns include static site generation, which renders pages ahead of time at build, and dynamic rendering, an older workaround Google now discourages. The common principle is that content present in the initial HTML response is the most dependable for crawling, indexing, and machine readability.

Related: JavaScript SEO and rendering guide, The forgotten HTML, Service Worker