GEO / Agent Readiness

Server-side rendering (SSR)

Also known as SSR · Pre-rendering · Server-rendered content

Delivering the page's core text and markup in the initial HTML response, so it is readable without executing client-side JavaScript.

What it is

Server-side rendering produces the full HTML of a page on the server (or at build time as static pre-rendering) so the meaningful content arrives in the first response. This contrasts with client-side rendering, where the initial HTML is a near-empty shell and JavaScript fetches and paints the content in the browser. Hydration can still add interactivity on top of server-rendered HTML.

Why it matters

Many AI crawlers and agents do not execute JavaScript, or do so inconsistently and with delay, so content that only appears after JS runs may be invisible to them. Server-rendering core text ensures answer engines, LLM fetchers, and traditional crawlers all see your actual content, which is a prerequisite for being read, indexed, and cited.

How to verify

Run curl -s https://example.com/page and confirm the raw HTML contains the real headings and body copy rather than an empty <div id="root"></div> shell. You can also use view-source in the browser or disable JavaScript and reload; if the page goes blank, content is client-rendered only.

How to fix

Adopt SSR, static site generation, or pre-rendering (for example Next.js, Nuxt, Astro, or a pre-render service) so the core content is in the initial HTML. If a full rewrite is impractical, add server-rendered fallbacks or a pre-render layer for bots, and avoid hiding primary content behind client-only data fetches.

In the checklist

This concept maps to a check in the GEO Score checklist.

Use the checklist

Related terms

Official references

External, opens in a new tab.

Put this into practice.

Work through every check by hand and turn it into a shareable GEO Score report — or scan your site automatically in seconds.