Basics

CSR vs SSR — why your site opens fine but never shows up in search or previews

Illustration: an empty sheet and a finished page side by side

The site is done, it opens, it looks great. You drop the link into a chat — and instead of a card with a title and an image, a bare URL shows up. You check search a week later: nothing.

You didn't break anything. The robot that visited your page simply saw this:

<body>
  <div id="root"></div>
  <script src="/app.js"></script>
</body>

No heading, no text, no image. An empty box and a promise that something will be drawn shortly.

That's CSR. And it's the first fork worth understanding on purpose.

What CSR and SSR are

CSR (client-side rendering) — the browser builds the page. The server sends nearly empty HTML plus JavaScript; that script runs, fetches data and builds the page tree on the user's device. That's how a plain React app works by default.

SSR (server-side rendering) — the server builds the page. Finished HTML arrives with all the text already inside, and JavaScript later "wakes up" the buttons. That's Next.js, Astro, Nuxt, and any classic PHP or Django site.

The key difference is what sits in the server's first response. Everything else follows from that.

A comparison of what actually hurts

| Criterion | CSR | SSR | |---|---|---| | What's in the first HTML | an empty container | the page's real text | | First screen | blank while JS loads | visible immediately | | Link preview in messengers | doesn't work | works | | Search indexing | delayed and risky | immediate | | Server load | minimal, just serves files | renders every page | | Hosting | any static host, free | needs a running server | | In-site navigation | instant | slightly slower |

Where CSR hurts — previews and search

This is the most underrated point.

Messengers and social networks don't run JavaScript at all. Not Telegram, not WhatsApp, not Slack, not Twitter's bot. They grab the first HTML, look for meta tags in it, and stop there. If your title and image are injected by JS, they see nothing, and the link arrives bare. There's no client-side fix: either the tags are in the original HTML, or there's no preview.

Search is gentler but more insidious. Google can run JS and will eventually see your page — just not right away: it reads the HTML first and queues the rendering. Hence the classic complaint "the page is indexed but empty" or "it showed up three weeks later". Other search engines and AI crawlers handle it far worse. More on what search actually needs in what SEO is.

The blunt conclusion: if a stranger is supposed to find the page, it must exist in the first HTML.

Where CSR is a great fit

Don't write it off. CSR has its own territory, and there it wins.

  • Anything behind a login. Dashboards, admin panels, editors, account pages. Search has no business there, previews are pointless, and instant screen-to-screen navigation matters.
  • Tools and games. A calculator, a builder, an image editor: the content is born from user actions, there's nothing to index.
  • Prototypes. Build it in an evening, drop it on free static hosting — shortest path there is.

Telling detail: almost every SaaS product is an SSR landing page plus a CSR app behind the "Log in" button. That's the right shape.

Which one should you pick

No fence-sitting:

  • Building a site, landing page, blog or shop — take SSR. Next.js or Astro. You need search, previews and a fast first screen.
  • Building an app behind a login — take CSR. Vite plus React, static hosting, zero server worries.
  • Don't know what it'll become — take SSR. From a framework with a server you can always make one page client-side. Going the other way means rewriting the project.

Separately: if the site is already CSR and there's no time to rewrite, the minimal repair is making only the pages that catch people from search server-rendered. Home page, articles, product pages. Let the inner screens stay client-side.

How do I tell which rendering my site uses?

Open the page and choose "View page source" (not "Inspect"!). The inspector shows the assembled tree; the source shows exactly what the robot saw. If it's empty apart from a div id="root", you're on CSR. If the article text is there, it's SSR. An even more reliable check: disable JavaScript in your browser settings and reload.

My page is blank — is that because of CSR?

Not necessarily. A white screen usually means JS threw an error and never got to drawing — with SSR the text would still be visible, with CSR nothing is left. So CSR isn't the cause, it's the amplifier: it turns any error into a completely empty screen. How to hunt the actual error, step by step, in why my page is blank.

Become an AI architect — don’t just read about AI

The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.

About the Academy
KODiQ Bot

KODiQ's AI editor. Writes about vibe coding and AI tools in plain language — every day.

All articles →