Key takeaways
- A headless CMS stores and manages content, but delivers it through an API instead of rendering web pages itself.
- A separate front end (Next.js, Nuxt, Astro, a mobile app) fetches and displays the content.
- Great for multi-channel content and custom apps; overkill for most small business websites.
“Headless” is one of the most hyped terms in web development. It can deliver blazing-fast, flexible sites — or double your costs for no real benefit. Here’s what it means and when it’s worth it.
Traditional vs headless#
| Traditional (WordPress as usual) | Headless | |
|---|---|---|
| Content management | CMS | CMS |
| Page rendering | CMS theme | Separate front-end app |
| Delivery | HTML pages | API (REST/GraphQL) → front end |
| Channels | Mainly the website | Website, apps, kiosks, other sites |
| Teams needed | WordPress developer | CMS + front-end developers |
Popular headless CMS options#
- WordPress (headless): REST API or WPGraphQL with a Next.js/Astro front end — familiar editing for content teams.
- Sanity, Contentful, Storyblok, Hygraph: hosted, API-first CMSs.
- Strapi, Payload, Directus: open-source, self-hosted options.
When headless makes sense#
- The same content feeds a website, mobile apps and other channels.
- You’re building a web app or SaaS that also needs marketing content.
- Your front-end team works in React/Vue and wants full control.
- Very high traffic with static generation at the edge.
- Strict security requirements (the CMS can sit behind a firewall).
Need a hand with this?
Get a quick, honest review of your website’s SEO.
When it doesn’t#
- Small business or blog sites where the team edits pages visually.
- Limited budget for development and maintenance of two systems.
- Reliance on WordPress plugins that output front-end features (forms, SEO, e-commerce) — many don’t work headless without extra work.
- Editors who need live previews and page building (possible headless, but requires setup).
SEO in headless setups#
- Use server-side rendering or static generation — see JavaScript SEO.
- Rebuild what WordPress plugins gave you: titles, meta, canonicals, sitemaps, schema, redirects.
- Handle 404s and redirects in the front end.
- Set up preview modes so editors see unpublished changes.
A pragmatic middle ground#
Many projects use a traditional WordPress site for marketing and blog content, and a separate React/Next.js app for the logged-in product. Each tool does what it’s best at. See SaaS tech stack and REST APIs explained.
Headless CMS FAQ#
Is headless faster?#
It can be, especially with static generation and a CDN. A well-optimised traditional WordPress site can also be very fast.
Is headless more secure?#
The CMS can be hidden from the public internet, reducing attack surface — but there are now two systems to secure.
Can I go headless later?#
Yes. WordPress content can be exposed via its API whenever you’re ready.