TECHNICAL · SEO GLOSSARY

Headless CMS (SEO)

A CMS that stores and delivers content via API with no built-in rendering layer. SEO quality depends entirely on the frontend framework consuming the API — if the frontend uses client-side rendering (CSR), Googlebot may not crawl content until the second-wave JavaScript render, which can be delayed days to weeks.

Definition

A headless CMS (e.g., Contentful, Strapi, Sanity, Prismic) separates the content management back-end from the presentation layer. Content is stored in the CMS and delivered via REST or GraphQL APIs; a separate frontend framework (Next.js, Gatsby, Nuxt, Astro) fetches the content and renders it as HTML for the browser. The SEO implications: the CMS itself produces no SEO output — no HTML, no title tags, no meta descriptions, no sitemaps, no structured data. All SEO output comes from the frontend. The critical SEO variable is the frontend rendering mode. **SSG (Static Site Generation)** — e.g., Gatsby, Next.js with `generateStaticParams()` — pre-renders all pages to static HTML at build time; Googlebot sees complete HTML instantly. **SSR (Server-Side Rendering)** — e.g., Next.js App Router with `async` Server Components — renders HTML per-request on the server; Googlebot sees complete HTML on first-wave crawl. **CSR (Client-Side Rendering)** — e.g., plain React SPA fetching from the headless CMS API client-side — returns an empty HTML shell; Googlebot must wait for the second-wave JavaScript render, which may be delayed days to weeks for lower-priority URLs. Headless CMSs also require frontend-owned sitemaps, robots.txt, structured data injection, and AI visibility signals — none are provided by the CMS.

Why it matters for SEO

Many teams adopt headless CMSs for content flexibility without accounting for the rendering mode decision. A Next.js frontend with Contentful can be either SSG/SSR (excellent for SEO) or CSR (poor for SEO) depending on how the frontend is configured. The audit detects rendering mode by comparing the server-returned HTML (before JavaScript execution) against the fully rendered DOM. Content absent from the raw HTTP response but present after JavaScript is flagged as a CSR rendering gap. Fixing this — migrating to SSR/SSG — is often the highest-impact technical SEO change for headless CMS sites.

How DeepSEOAnalysis checks this

The audit compares the raw server HTTP response against the post-JavaScript rendered DOM. Content in headings, body text, or JSON-LD that appears after JavaScript execution but not in the server response is flagged as a rendering gap. CMS type is detected and CMS-specific remediation guidance is provided (e.g., Next.js App Router Server Components pattern for Contentful, gatsby-source-contentful for Gatsby).

Useful tools and resources

Full technical SEO audit

GLOSSARY

technical

JavaScript SEO

The practice of ensuring that JavaScript-rendered content is accessible and indexable by search engine crawlers, which process JS differently from browsers.

Read definition →

technical

Server-Side Rendering (SSR)

Generating the full HTML of a page on the server per request, so browsers and crawlers receive complete content on the first HTTP response — the opposite of client-side rendering (CSR) where a JavaScript bundle builds the DOM after load.

Read definition →

technical