Architecture
Client-side rendering vs server-side rendering
For anything that needs to be found, server rendering wins decisively. Client-side rendering delivers an empty document to crawlers that do not execute JavaScript — which is most AI crawlers — and puts four sequential steps between the request and the first pixel.
Side by side
| Compared on | Client-side | Server-side |
|---|---|---|
| Googlebot sees content | Eventually, via a deferred render queue | Immediately |
| AI crawlers see content | No | Yes |
| First paint | After the bundle downloads and executes | On first response |
| Server cost | Low — static files | Higher — rendering per request |
| Best for | Logged-in application screens | Anything indexable |
| Interaction cost | Full hydration | Hydration only where needed |
When Client-side rendering is the right choice
- Application screens behind a login that should not be indexed
- Highly interactive tools where the first paint is not the point
- Internal dashboards with no search requirement
When server-side rendering is the right choice
- Any page you want indexed or cited
- Any page where first paint speed affects conversion
- Anything an AI assistant might be asked about
- Content that must be readable without JavaScript
The test that settles it
View the page source — not the Elements panel. If the body is an empty container and a script tag, your content does not exist until execution. Count the words in view-source against the rendered page; a large gap is the entire problem stated as one number.
Why this matters more than it used to
"Google renders it eventually" was defensible when Google was the only consumer that mattered. When a buyer pastes your URL into an assistant and asks whether you are any good, that fetch does not render — and an empty response is the answer they receive.
The verdict
Client-side rendering is a legitimate choice for application screens and a mistake for anything that needs to be found. If the page should appear in search or in an AI answer, the content must be in the HTML.
If you want the full treatment
JavaScript SEO: the difference between what you see and what gets indexed covers this in about 3 minutes — free, ungated, written from client work.
Who wrote this comparison
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada and Pakistan. Where a comparison involves something I sell, the page says so — and every comparison here has to name at least two situations where each side wins, because a comparison one option always wins is an advert with a table in it.