What is a headless CMS? It is a content management system that stores and edits your content but doesn’t decide how it looks or build the pages. A separate front end, built with a framework such as Astro or Next.js, fetches the content and turns it into the website. “Headless” means the CMS has no “head”, the part visitors see. A traditional CMS such as WordPress does both jobs in one system.
For most small business sites, a traditional CMS or a static site is simpler and cheaper. A headless CMS earns its extra cost when the same content feeds several places, when editors need a CMS but the front end needs to be fully custom and fast, or when a team outgrows its current platform.
How the two set-ups work
Traditional CMS. You log in to WordPress, edit a page and press Update. WordPress stores the content, applies the theme and serves the page to visitors. One system, one bill, one thing to update.
Headless CMS. You log in to the CMS, edit content in a form and press Publish. The CMS stores the content and makes it available through an API. The website, built separately, fetches the content and builds the pages, often ahead of time as static files. The same content can also feed an app, a kiosk or another site.
What changes for the people who edit
| Traditional CMS | Headless CMS | |
|---|---|---|
| Editing | Edit the page as it will look | Edit structured fields: title, summary, body, image |
| Preview | Built in | Needs setting up; varies by CMS |
| Layout changes | Often possible for editors | Usually need a developer |
| New page types | Through the theme or a page builder | A developer adds them |
| Publishing | Instant | Instant, or after a rebuild of a few seconds to minutes |
Editors often find headless editing tidier, since content is in clear fields, but they lose some freedom to change layouts themselves. Decide whether that is a benefit or a cost for your team.
Benefits
- Speed. The front end can be built as static pages with little JavaScript, which is fast by default.
- Security. The CMS isn’t on the public website, so there is less to attack.
- One source of content for many places: website, app, newsletters, screens.
- Design freedom. The front end isn’t limited by a theme system.
Costs and drawbacks
- Two systems. A CMS and a front end, each with its own setup and updates, and sometimes two bills.
- Developer dependence. New page types and layout changes need a developer.
- Preview and plugins. Things WordPress gives you out of the box, like previews, forms, SEO plugins and comments, have to be set up or built.
- Higher build cost, because more of the site is custom.
Who should use a headless CMS
A headless CMS makes sense when:
- Content goes to more than one place
- Speed and design matter enough to justify a custom front end, and editors still need a CMS
- A development team will look after the site long term
A traditional CMS makes sense when:
- One website is the only destination for content
- Editors want to change layouts without a developer
- The budget is small, or there is no developer on hand
A static site with no CMS makes sense when content changes rarely and a developer makes those changes. That is how our main site works.
WordPress can be headless too
WordPress can act as a headless CMS: editors use the WordPress screens they know, and a separate front end, such as an Astro site, builds the public pages from WordPress content. It is a common middle path for teams that like WordPress editing but want a faster or more custom front end. We compare the two platforms with our own measurements in Astro vs WordPress.
Questions people ask
Is a headless CMS better for SEO? Not by itself. It makes a fast site easier to build, and speed helps visitors. Titles, structured data and sitemaps still have to be set up in the front end.
Is a headless CMS more expensive? Usually, to build and to run, because there are two systems and more custom work.
Can I switch to headless later? Yes. Content can be moved or, with WordPress, kept where it is while a new front end is built.
If you are weighing a headless set-up, our Astro website development page explains how we build fast front ends, and WordPress development covers the traditional route.