Server-side rendering (SSR)
Server-side rendering (SSR) means a web page's HTML is generated on the server for each request, so browsers and bots receive complete content immediately.
With client-side rendering, the server sends a nearly empty page and JavaScript builds the content in the browser. With SSR, the server runs that code first and sends finished HTML, which then becomes interactive.
In more detail
SSR improves first load speed and makes content visible to every crawler, including those that do not run JavaScript. It is supported by frameworks like Next.js, Nuxt and Astro. The trade-off is server work on each request, which caching reduces. For pages that rarely change, static site generation goes further by building the HTML once at deploy time.
Why it matters
For any page that needs to rank or be cited, SSR or static generation is the safest choice. It solves most JavaScript SEO problems at the root.
A product catalogue switches its listing pages from client-side rendering to SSR. Search engines now see product names and prices in the HTML, and LCP improves because content arrives with the first response.