CSR (Client‑Side Rendering)
Rendering a web page in the browser using JavaScript. Bad for SEO without pre‑rendering or SSR, as search crawlers may not see the content.
Client‑Side Rendering (CSR) is an approach where the server sends an almost empty HTML and all content rendering happens in the browser via JavaScript. For SEO, additional handling like dynamic rendering, pre‑rendering, or hybrid SSR is required.
What is CSR
Rendering in the browser. Bad for SEO unless pre‑rendering is configured. In CSR the HTML arrives almost empty; content is assembled in the browser via JavaScript.
SEO Problems
Crawlers execute JS but with delays and limits. Without extra measures, important content may not render in time — indexing suffers.
Solutions
- SSR or SSG — deliver pre‑built HTML (Next.js, Nuxt, Astro)
- Prerendering (Prerender) — serve static HTML to bots, SPA to users
- Dynamic rendering — detect bot by User‑Agent and serve a simplified HTML
When CSR is Acceptable
For transactional and commercial pages, CSR without pre‑rendering/SSR risks under‑indexation. CSR makes sense for logged‑in applications (dashboard, CRM) that don't need indexing.
Common questions
Discuss your project?
Share your goals and website context — I will suggest a practical next step.