Headless CMS

The "head" is the front end, the part that turns content into pages. A traditional CMS such as a standard WordPress install includes both the editing back end and the page-building front end. A headless CMS keeps only the back end: editors still log in and write, but developers build the front end separately, often with a framework such as Next.js, and pull the content in through an API.

Headless is an architecture, not a brand or a quality level. Some products are headless only; others, including WordPress, can be run headless by using their API and ignoring their themes. The choice brings flexibility and performance options, and also more moving parts.

How it works

Editors work in an admin interface organised around content types, structured models with fields such as title, summary, image, price or opening hours. Instead of a page with free-form layout, each item is stored as structured data. The CMS then exposes that content through an API, typically REST or GraphQL, which any authorised program can request.

The front end is a separate codebase. It either fetches content when a visitor arrives, or, more often for marketing sites, fetches everything at build time and generates finished pages, a static site. When an editor publishes, a webhook tells the hosting platform to rebuild, and the change goes live a short time later.

Because the content is structured and not tied to one layout, the same entries can feed a website, a mobile app, a digital sign or a partner feed. The cost is that features a traditional CMS gives for free, such as previews of unpublished pages, menus, forms and search engine settings, must be designed and built into the front end.

Example

A multi-location clinic group stores each clinic's address, hours, services and team members as structured entries in a headless CMS. The website, a patient app and the screens in each waiting room all read the same entries. When a clinic changes its Saturday hours, the receptionist edits one field and every channel shows the change, the website as soon as it has rebuilt.

What the group gave up is visible in the editing experience. Editors cannot drag blocks around a page freely; they fill in fields, and the layout is decided by developers. A preview button had to be built specially so staff could see a draft before publishing, and adding a new kind of page means a developer adds a content type and a template.

Why it matters for your business

A headless CMS earns its cost when content is reused across several channels, when performance and security matter enough to justify a static or custom front end, or when a development team wants full control of the code. For a small business with one website and a modest budget, it usually means paying developers to rebuild features a traditional CMS already includes, and it creates a dependency on whoever built the front end. The honest test is whether you have a second channel or a performance need a well-built traditional site cannot meet.

Common mistakes

• Choosing headless because it sounds modern when the business has one website and no developer on hand.
• Forgetting to plan previews, so editors publish blind and check the live site afterwards.
• Modelling content as big rich-text blobs, which throws away the structured-data benefit.
• Not budgeting for two systems, the CMS subscription and the front-end hosting, plus the developer who maintains the connection.

Questions people ask

What is the difference between a headless CMS and a traditional CMS?

A traditional CMS stores content and also builds the pages from themes. A headless CMS only stores and edits content and hands it to a separately built front end through an API. Traditional is simpler and cheaper to run; headless is more flexible across channels and front-end technology.

Is a headless CMS better for SEO?

Not by itself. Search engines care about the pages they receive. A headless setup can produce very fast, clean pages, but titles, meta descriptions, structured data, sitemaps and redirects must all be built deliberately. A well-configured traditional CMS can perform just as well.

Can WordPress be used as a headless CMS?

Yes. WordPress has a built-in REST API, and plugins can add GraphQL. Editors keep the familiar dashboard while a separate front end fetches content. You lose themes and many plugins that depend on WordPress rendering pages, so features like forms and SEO settings need rebuilding.