Glossary · Technical SEO

SSR (Server-Side Rendering)

Also called: static site generation, SSG, prerendering

Definition

SSR (server-side rendering) generates a page's full HTML on the server, so browsers and crawlers receive complete content without running JavaScript first.

SSR explained

With client-side rendering, the server sends a skeleton page and the browser builds the content. With server-side rendering, the server runs the code and sends finished HTML, which the browser then makes interactive. Static site generation goes a step further and builds pages ahead of time.

For SEO and AI visibility, SSR and static generation are the safest options because every crawler, including the many AI bots that don't execute JavaScript, sees the same complete content as a visitor. They also usually improve how quickly the main content appears, which helps Largest Contentful Paint.

Frameworks such as Next.js, Nuxt and SvelteKit support server rendering out of the box, and many can mix approaches page by page. Dynamic rendering, where bots get a different prerendered version from users, is described by Google as a workaround and not a long-term solution; Google recommends server-side rendering, static rendering or hydration instead.

Example

Your documentation site was built as a single-page app, and AI assistants rarely cite it. Moving the docs to server-side rendering means crawlers receive the full article text in the first response, and the pages start appearing as sources.

Why it matters

Rendering important pages on the server removes a whole class of crawling and indexing risks and often speeds pages up.

Related service

Technical SEO

Crawlability, indexing, structured data and rendering fixes so search engines and AI crawlers can read your site.

Technical SEO services

FAQ: Can AI crawlers read JavaScript?

Published by Vidern, founded and led by Malhar Shah. Updated .

Find out what's holding your site back

Get a free SEO audit with prioritized fixes, delivered within 48 hours.