SEO

SSR (Server-Side Rendering)

Also called Server-side rendering

The server assembles a page's finished HTML on every request, so the browser receives readable content immediately.

Quick facts: SSR (Server-Side Rendering)

Category
SEO
Also called
Server-side rendering
Level
Advanced
Affects
Indexing reliability, time to first byte, server cost
Where to see it
PageSpeed Insights, Search Console Core Web Vitals report, URL Inspection, browser view-source
In this article4
  1. How server-side rendering works
  2. Why server-side rendering matters
  3. Where server-side rendering goes wrong
  4. What to do about it

How server-side rendering works

A request arrives, the server runs the application code, fetches whatever data the page needs, and produces a complete HTML document — headings, paragraphs, links, title and meta tags included — before sending anything back. The browser receives something it can display at once. JavaScript still loads afterwards to make menus, filters and forms interactive, a step called hydration, but reading the page does not depend on it.

Because the work happens on every request, the output can be current to the second and specific to the visitor: a live stock level, a price in the local currency, a logged-in name in the header. That is the practical reason to choose it over building pages in advance, and it is why most ecommerce and listing sites end up here.

Why server-side rendering matters

Crawlers get everything on the first pass. There is no queue to wait in and no script that has to succeed before the content exists, so new pages and edits are picked up as quickly as the crawler is willing to return. Canonical tags, titles and internal links are in the response rather than being written in later, which removes a whole category of intermittent, hard-to-reproduce indexing faults.

Visitors benefit for the same reason. Text and images start appearing while the JavaScript bundle is still downloading, which matters most on a mid-range phone over a mobile connection — the normal case for most Nepali traffic. A page that shows its first paragraph early feels fast even when the full bundle takes its time.

Where server-side rendering goes wrong

The cost lands on the server. Every request means application code, database queries and template work before a single byte leaves the building, so time to first byte becomes the number to watch. A slow upstream API or an under-powered host turns a rendering choice that was meant to speed the site up into the thing holding it back. Uncached server rendering is regularly slower than a plain static file.

The other trap is the gap between looking ready and being usable. The text is on screen, but until the JavaScript has hydrated the page, taps and clicks do nothing. Visitors press the button twice, then a third time, and the delay is recorded against interaction responsiveness. Hosting is a practical constraint too: server rendering needs an application runtime, which ordinary shared hosting plans usually do not provide.

What to do about it

Cache what is identical for everyone. Marketing pages, blog posts, category listings and product pages without personalised elements can be rendered once and served from cache or a CDN edge until the underlying content changes, which keeps the SEO benefit and removes almost all the server cost. Reserve genuine per-request rendering for pages that really are different for each visitor.

Then measure the right thing. Watch time to first byte in PageSpeed Insights and the Core Web Vitals report, and treat a rising figure as a server problem rather than a front-end one. Keep the JavaScript bundle small so hydration is quick, and confirm with the URL Inspection tool that the HTML Google holds matches the page you see. If the rendering strategy is being chosen as part of a rebuild or migration, settle it alongside the rest of the technical SEO plan rather than after launch.

Do and do not

Do

  • Cache pages that are identical for every visitor
  • Watch time to first byte as a server metric
  • Keep titles, canonicals and links in the server response

Do not

  • Render personalised HTML for pages nobody personalises
  • Ship a huge bundle and rely on hydration to catch up
  • Assume server rendering alone makes the site fast

Questions people ask about this

Is server-side rendering better for SEO than client-side rendering?

For pages that need to be found, yes. The content, links and meta tags arrive in the first response, so nothing depends on a rendering queue or on a script executing successfully. That removes a common source of missing or delayed indexing. It is not automatically faster for visitors, though, because a slow server can undo the advantage.

Does server-side rendering slow my website down?

It can, if every request rebuilds the page from scratch. The server has to run code and query the database before sending anything, which delays the first byte. Caching removes most of that cost for pages that look the same to everyone, so the usual answer is to render once and serve the cached copy until the content changes.

Can I use server-side rendering on shared hosting?

Usually not in the JavaScript sense, because that needs an application runtime such as Node, which most shared plans do not offer. Worth knowing, though, that a traditional WordPress, Laravel or PHP site is already server-rendered by design — the HTML is assembled before it is sent. The term mainly comes up with modern JavaScript frameworks.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.