Rendering

SSR

The server builds the full HTML for a page on each request and sends it ready to display.

Instead of shipping the browser a blank page plus a pile of JavaScript that has to assemble the content, the server does the assembly and hands over finished HTML. This means Google and the user both see real content immediately, so it's good for SEO and fast first paint — the tradeoff is that every single request costs server work. Example: a product page showing live inventory renders on the server so the price and stock count are in the HTML the moment it arrives. When you build with AI, know that asking for SSR means you're accepting a running server (or serverless functions) behind your pages, not just static files.