DocsContentServer-side rendering
Server-side rendering
Whether the content exists before JavaScript runs. Most agents never run it.
Set up Server-side rendering on your site
Why an agent often sees an empty page, and how to check what yours returns before any script runs.
Free
Serve content without JavaScript
Why an agent cares
Many crawlers and answer engines read only the raw HTTP response, so content that appears after hydration is invisible to them. This is measured as a heuristic comparison of the raw body against the rendered DOM, not as a spec check.
Adoption
Web baseline. Standard equipment on the web. Its absence is the exception rather than its presence.
Direction of travel: ► flat, as at .
The default posture of every mainstream framework, and long-standing Google JavaScript-SEO guidance.
What we check
Absence is never a finding. Every check below runs only when this technology is detected, so a site that has not adopted this is not assessed on it and appears in no report. 3 of these 4 can fail it. In Lumar these appear on each page's own row.
| Check | Severity | Raises | On whose authority |
|---|---|---|---|
| SSR Primary Content Empty | high | usability | our inference |
| SSR Content Only After JS | high | usability | our inference |
| SSR Boilerplate Only | medium | usability | our inference |
| SSR Low Static Share | informational | nothing | Lumar readiness bar |
Specifications
| Document | Revision | Kind |
|---|---|---|
| WHATWG HTML — the main element | Living Standard | specification |
| Google Search: JavaScript SEO basics | Living document | guidance |
Last re-read against the published documents: .