# Headless CMS

Category: [Technical SEO](https://seo-geo-glossary.com/en/glossary/category/technical-seo/) › [CMS, operations & special files](https://seo-geo-glossary.com/en/glossary/category/technical-seo/cms-operations-special-files/)

A **headless CMS** is a content management system that stores and manages content and delivers it through an API, without producing web pages itself. A separate frontend, built by a development team, decides how the content looks and under which URLs it is available. The related term decoupled CMS is delimited inconsistently across sources and is not defined here.

## What does a headless CMS mean for SEO?

A traditional CMS generates content, HTML, URLs, title tags and sitemaps in one piece of software. With a headless setup, the frontend takes over those jobs. Search engines see only what the frontend sends to the browser, never the API. In practice, the CMS brand does not decide rankings, the HTML and HTTP responses that reach the crawler do (assessment).

If the frontend renders in the browser, Google's JavaScript processing applies. According to Google, Googlebot queues pages with a 200 status code for rendering. Links are found only if they are `<a>` elements with an `href` attribute. Google allows JavaScript to set a canonical URL but advises against changing the one given in the original HTML. For single-page apps, error pages need a real 404 status or a `noindex` to avoid soft 404s.

The content model also matters. Fields for title, meta description, canonical and robots directives must exist in the CMS, and the frontend has to print them into the page.

## Example

An API response for a product page:

```json
{
  "slug": "trail-shoe",
  "seoTitle": "Alpine Trail Running Shoe",
  "metaDescription": "Light trail shoe with an aggressive tread.",
  "canonical": "https://www.example.com/shoes/trail-shoe"
}
```

The frontend must turn `seoTitle`, `metaDescription` and `canonical` into a title element, a meta tag and a link element in the `<head>`.

## Common mistakes

- **No SEO fields in the content model.** Editors cannot set titles or canonicals.
- **Missing pages return 200.** The frontend shows an error message, but the server responds with 200.
- **Navigation without `href`.** Click handlers instead of links keep Google from finding further pages.
- **Redirects, sitemap and robots.txt forgotten.** A headless CMS does not deliver them by default.

## FAQ

**Is a headless CMS bad for SEO?**
It moves responsibility for HTML, URLs and meta data to the frontend. If the frontend implements them completely, search engines get the same basics as with a traditional system.

**What is the difference between a headless CMS and a CMS?**
A traditional CMS manages and displays content. A headless CMS manages content and hands it to other systems over an API.

## Related terms

- [CMS (content management system)](https://seo-geo-glossary.com/en/glossary/cms/index.md)
- [Headless browser](https://seo-geo-glossary.com/en/glossary/headless-browser/index.md)
- [CMS migration](https://seo-geo-glossary.com/en/glossary/cms-migration/index.md)
- [JavaScript SEO](https://seo-geo-glossary.com/en/glossary/javascript-seo/index.md)

## Sources

- [Understand JavaScript SEO basics – Google Search Central](https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics)
- [What is a headless CMS? – AWS](https://aws.amazon.com/what-is/headless-cms/)
- [Headless CMS 101 – Sanity (secondary)](https://www.sanity.io/headless-cms)

---

Last updated: October 7, 2026
URL: https://seo-geo-glossary.com/en/glossary/headless-cms/