Technical SEO
Server-side rendering
Server-side rendering is generating a page’s HTML on the server so the content arrives complete in the initial response.
What is server-side rendering?
Server-side rendering is generating a page’s HTML on the server so the content arrives complete in the initial response. The alternative, client-side rendering, builds the page in the browser after JavaScript executes.
What it affects
Many systems that matter, including several AI retrieval layers and most social preview fetchers, do not execute JavaScript, so client-rendered content is invisible to them.
What the work looks like
Implemented by the framework rendering on request or at build time. The test is comparing raw HTML against rendered HTML for content, links and structured data.
What it is not
The fact that one major crawler executes JavaScript does not mean all retrieval systems do. Parity between raw and rendered output is what makes content universally visible.
It is a small idea with a disproportionate effect on how a site performs.
Where this comes up in the work
It is part of Entity and Semantic SEO, and more specifically of Topical authority mapping. Across the rest of the work it shows up in:
- Content and Editorial, where it sets the ceiling on deciding which formats this audience actually finishes
- Lifecycle and Email, because working out whether low open rates are a subject line or a deliverability problem depends on it
- Analytics and Measurement, in which it shows up as accepting that some agent activity leaves no session at all
- Brand and Creative, where it decides shipping a system people use instead of a document people ignore
What to check
Two questions that establish whether this is actually in order on a given site:
- Whether it was verified in the logs or inferred from a dashboard
- Whether there is a named owner, or whether it falls between two teams
More in Technical SEO
Common questions
How is server-side rendering audited?
Implemented by the framework rendering on request or at build time. The test is comparing raw HTML against rendered HTML for content, links and structured data.
Who owns server-side rendering in a business?
It needs one named owner rather than a shared responsibility. The natural home is Technical SEO, since giving the site a shape that distributes authority deliberately is where the consequence lands.
How much work is server-side rendering?
Less than people expect to check and sometimes more than they expect to fix. Implemented by the framework rendering on request or at build time.
Where does server-side rendering sit in the priority order?
High if it is actually broken, low if it is merely imperfect. The check tells you which.
How do you prove server-side rendering is worth fixing?
Many systems that matter, including several AI retrieval layers and most social preview fetchers, do not execute JavaScript, so client-rendered content is invisible to them. The evidence is specific to the site, which is why the check comes before the recommendation. SaaS and technology is the prerequisite. Travel and hospitality is what it makes possible.
Is server-side rendering just another name for something?
The fact that one major crawler executes JavaScript does not mean all retrieval systems do. Parity between raw and rendered output is what makes content universally visible. Worth clarifying before agreeing to work on it. Brand and Creative is the part that scales. Conversion Rate Optimization is the part that never will.
See the gaps before you spend against them
Send what you have. We read it before the call, so the call is about decisions rather than discovery.