Headless CMS: questions and answers

A headless CMS is a content management system that stores content and delivers it through an API, without generating the website's presentation itself. Headless CMS comes up more and more often – in agency meetings, developer proposals and tool comparisons. We've gathered the questions people ask most about it and answered them briefly and directly: how it works, what it costs, SEO, content preview and hosting.

Key takeaways

• A headless CMS separates content from presentation: editors work in a panel and the front end fetches content via an API.
• A headless architecture requires building and maintaining a separate front end, which raises costs and involves developers.
• A site on a headless CMS can rank very well in Google if the front end renders HTML on the server or statically.
• Going headless pays off for multiple channels, an unusual front end or a developer team that wants to work in its own framework.
• A hybrid CMS renders ready-made pages and exposes content via an API, so you don't have to commit to one model.

What is a headless CMS?

A headless CMS is a content system without a "head": it has an editing panel and a content store, but no presentation layer. Content is delivered as data, usually JSON, and a separate application – a website, a mobile app or an in-store screen – takes care of displaying it. For a detailed comparison with the traditional approach, see the other articles on the LessCMS blog.

How does a headless CMS work in practice?

Content goes through a few stages: editing, API, front end and delivery. Each can be handled by a different tool.

1. Content modelling – you define content types and fields, e.g. a "project" with a title, description, gallery and date.
2. Editing – an editor fills in the fields in the panel and publishes the entry.
3. API – published content becomes available at an API endpoint, usually protected by a key.
4. Front end – the developer's application fetches the data and builds HTML pages on the server, at build time or in the browser.
5. Delivery – finished pages are served from hosting or a CDN, often with a cache that refreshes after publishing.

What are the benefits of a headless CMS?

The biggest benefit is freedom: developers build the front end in any technology, and the same content can feed several channels. On top of that:

• One content source for many channels – website, app, kiosk or newsletter all use the same data.
• Full control over front-end performance – you don't ship template code you never use.
• A smaller attack surface – the editorial panel doesn't have to be publicly reachable at the site's address.
• Independent changes – a redesign doesn't require migrating content.

What are the drawbacks and hidden costs of a headless CMS?

The main drawback is that you must build and maintain a separate front end – a second software project. So a company pays not only for the CMS but also for developer time, front-end hosting and ongoing updates.

• Editors often can't see what the page looks like while editing, because the panel shows only fields.
• Features a traditional CMS provides out of the box – sitemap, redirects, forms, meta tags – have to be implemented in the front end.
• Every new page section requires a developer, not just an editor.
• The team depends on people who know a specific framework.

Is a headless CMS good for SEO?

Yes, as long as the front end produces ready-made HTML on the server (SSR) or at build time (SSG). Problems arise when content is loaded only in the browser via JavaScript – crawlers may then see it late or incompletely. In a headless setup the front end is responsible for titles, meta descriptions, structured data, the sitemap, canonical URLs and redirects, so write these requirements down before the project starts.

How much does a headless CMS cost?

The system itself can be cheap or even free on a basic tier, but the total cost is driven mainly by building and maintaining the front end. The budget includes:

For a simple business website, the total is usually higher than with a CMS that renders the site itself.

Who needs a headless CMS – and who doesn't?

A headless CMS suits companies that publish the same content across several channels or have developers building the front end in their own technology. Typical examples include a mobile app that reuses website content, a complex site with unusual interactions, or an agency with its own component library. A small business with a simple site edited by the marketing team usually doesn't need one – a CMS with a visual editor works better there.

How does content preview work in a headless CMS?

In a headless setup, preview usually has to be built separately, because the CMS doesn't know how the front end will display the content. Most often the front end has a preview mode that fetches drafts and shows them at a non-public URL. If the API serves only published content, pre-publish preview has to come from the CMS itself or from a separate staging environment.

Where should you host the front end of a headless CMS?

You can host the front end on an edge platform or an app hosting service, on your own server, or as static files on a CDN. The choice depends on the rendering method: static pages just need a CDN, while SSR needs an environment that runs code. Make sure the front-end cache refreshes automatically after you publish in the CMS. The LessCMS API page shows what an integration can fetch.

How does LessCMS work as a headless CMS?

LessCMS is a hybrid CMS: you can use it as a headless CMS with your own front end, or let it render a full website on your domain. The key facts:

• A read-only public API returns published pages, collections, menus, blocks, redirects, the sitemap and robots.txt. Access is protected by an x-api-key header, and keys are scoped to a project and can be revoked.
• Swagger documentation is available at /api-docs, and the collections endpoint looks like https://api.lesscms.io/v1/{workspace}/{project}/collections/{code}.
• Full-site mode gives you server-side rendering, edge delivery via Cloudflare and automatic cache purging on publish – with no front end to build.
• The visual editor and live preview work in the panel, so editors see the result of their work, while collections with custom fields feed both the site and the API.

Frequently asked questions

Is a headless CMS the same as API-first?

Almost – both terms describe a system that delivers content primarily through an API. "API-first" emphasises how the system is designed, while "headless" emphasises the missing presentation layer. In practice the terms are often used interchangeably.

Can WordPress be used as a headless CMS?

Yes, WordPress exposes a REST API and can feed a separate front end. You still maintain the full installation with its plugins and updates, and some theme-dependent features stop working. That's why many teams choose a system designed around an API.

Can non-technical editors work with a headless CMS?

Yes, if the content model is well designed and fields have clear names and descriptions. Judging the visual result is harder, because the panel shows forms instead of the page. A preview or a hybrid CMS with a visual editor helps.

Is a headless CMS more secure than a traditional one?

It usually has a smaller attack surface, because the public site contains no admin panel or CMS code. Security still depends on the front end, the hosting and how API keys are protected. A read-only API further reduces risk.

What is a hybrid CMS?

A hybrid CMS can both render a finished website and deliver content through an API. It lets you start with a site that needs no coding and add your own front end or app later. It's a good choice when you don't want to lock into one model from day one.

Not sure whether headless or a full site fits your project better? Compare plans on the pricing page and create an account without a card – both modes work in the same panel.