What is client-side rendering (CSR)?

Client-side rendering (CSR) is when a browser receives a mostly empty HTML page and uses JavaScript to fetch data and build the visible content on the visitor’s device.

Curious how your site handles CSR?

Send me the address. I’ll look under the hood and tell you plainly what I find, free.

No newsletter. Just what you asked for, from me. Privacy

In plain English

With CSR, the first HTML the browser gets is little more than a shell and a link to a JavaScript bundle. Once the script downloads and runs, it fetches content and draws the page.

This is the default for many React and Vue apps. It works well for logged-in tools where SEO doesn’t matter, but it means content isn’t there until JavaScript finishes.

Why it matters for a small business

For a marketing site, CSR is risky. Google can render JavaScript, but it’s slower and less reliable than reading plain HTML. Many AI crawlers don’t run JavaScript at all, so a client-rendered page can look empty to them.

An example

A Calgary startup launches its marketing site as a client-rendered React app. Viewing the page source shows almost no text, and the site barely appears in AI answers about its category. Prerendering the same pages to HTML, with no visual change, gives crawlers the full content.

Common mistakes

Where I see CSR go wrong most often.

  1. Using CSR for public pages that need to rank or be cited.

  2. Judging SEO by what you see in the browser rather than checking the raw HTML.

  3. Loading one large JavaScript bundle for the whole site before showing anything.

FAQ

CSR, answered

  1. View the page source in your browser. If your headings and text are missing and you mostly see script tags, the content is rendered on the client.

  2. For dashboards, logged-in tools and apps where search visibility doesn’t matter and interactivity does.

Keep reading

Let’s begin

Let’s build something you’re proud to share.

Let’s Talk