TECHNICAL · SEO GLOSSARY

Rendering Mode (SEO)

The method by which a web page\'s HTML is generated and delivered to users and search engines — including server-side rendering (SSR), static site generation (SSG), incremental static regeneration (ISR), and client-side rendering (CSR) — with different implications for SEO performance, content freshness, and indexing reliability.

Definition

Rendering mode is the technical mechanism that produces the HTML delivered to browsers and search engine crawlers. Each mode has distinct SEO characteristics: (1) **SSG (Static Site Generation)**: HTML is pre-built at deploy time. Fast CDN delivery, maximum LCP performance, complete HTML for Googlebot on first request, structured data in initial HTML. Limitation: content freshness requires rebuild. Best for: blog posts, documentation, marketing pages, product pages that change infrequently. (2) **SSR (Server-Side Rendering)**: HTML is generated per-request on the server. Content always current, complete HTML for Googlebot. Limitation: server latency affects LCP, higher infrastructure cost. Best for: personalised pages, real-time data, search results pages. (3) **ISR (Incremental Static Regeneration)**: SSG with timed background regeneration. Combines SSG performance with acceptable content freshness. Best for: large catalogues, frequently updated content on established sites. (4) **CSR (Client-Side Rendering)**: Minimal HTML shell delivered; browser executes JavaScript to render content. Limitation: Googlebot receives empty initial HTML, content indexed with significant delay, structured data processed in second rendering wave, LCP is poor (first contentful paint is the shell, not the content). Avoid for SEO-critical content. (5) **Partial hydration / Islands architecture**: Most of the page is SSG; specific "islands" are interactive components rendered client-side. Best of both worlds: fast static content for SEO, interactive components for UX. Frameworks: Astro (islands), Next.js (React Server Components). (6) **Edge SSR**: SSR executed at CDN edge nodes (Vercel Edge Runtime, Cloudflare Workers) rather than a centralised server — reducing SSR latency to near-CDN speeds. Combines SSR freshness with near-SSG delivery speed.

Why it matters for SEO

Rendering mode is the single most impactful technical architecture decision for SEO on modern JavaScript-framework sites. CSR is the most common cause of indexing failures, structured data processing delays, and poor LCP performance on technically sophisticated sites. SSG and SSR (or their hybrid forms ISR and edge SSR) are the baseline requirements for reliable SEO on headless and JavaScript framework sites.

How DeepSEOAnalysis checks this

DeepSEOAnalysis detects rendering characteristics from the initial HTTP response: presence of complete content in the initial HTML (consistent with SSG/SSR) versus a sparse shell (consistent with CSR), structured data in the initial HTML versus JavaScript-only injection, and CrUX performance metrics that reflect actual delivery speed. These signals help confirm whether the rendering mode is producing SEO-safe initial HTML.

GLOSSARY

technical

SSR vs SSG (SEO)

The choice between server-side rendering (generating HTML per request at the server) and static site generation (pre-building HTML at deploy time) — both produce SEO-safe server-rendered HTML, but with different trade-offs in content freshness, performance, and infrastructure cost.

Read definition →

technical

Incremental Static Regeneration (ISR) SEO

A Next.js rendering strategy that serves statically pre-generated pages (fast, SEO-safe) while automatically regenerating stale pages in the background at defined intervals — enabling large content sites to combine SSG performance with acceptable content freshness without full rebuilds.

Read definition →

technical

Static Site SEO

The SEO strategy for sites built with static site generators (Gatsby, Astro, Hugo, Eleventy, Next.js SSG mode) — where HTML is pre-built at deploy time and served directly from a CDN without server-side computation, producing excellent Core Web Vitals and reliable Googlebot crawl experiences.

Read definition →

technical

Decoupled SEO

The full set of SEO considerations specific to decoupled (headless) web architectures — where content management and content presentation are separate systems — including rendering strategy, structured data implementation in the frontend layer, canonical management, and AI crawler access.

Read definition →

technical

API-First SEO

The SEO strategy for sites built on API-first (headless) architectures — where content is managed via CMS API and rendered by a separate frontend — requiring explicit implementation of meta tags, canonical tags, and structured data in the frontend layer rather than via CMS plugins.

Read definition →

See how your site scores on Rendering Mode (SEO).

The free DeepSEOAnalysis audit checks rendering mode (seo) and 100+ other signals. Full report, no signup.

Run a free audit →