New I move websites from WordPress to Astro 1:1, without losing Google rankings. See how it works →Coming from ? See how I worked on their website →
Glossary

Headless CMS: what it is and when it makes sense

A headless CMS is a content panel kept separate from the website itself. You edit text, images and posts there, and the site fetches and displays them in its own way. Here's how it works, how it differs from WordPress and when it's worth choosing.

Headless CMS in one sentence

A headless CMS is a content management system that stores your content but doesn't render the website itself.

The name comes from cutting off the “head”, the layer visitors see. In a traditional CMS such as WordPress, the panel, the database and the site's design are one whole. A headless CMS keeps only the “body”: the panel and the content store. The site's design is built separately, e.g. in Astro.

Content reaches the site through an API, a standard connection. The same content can feed a website, a mobile app or a newsletter.

How it works day to day

  • You log in to the panel, e.g. Sanity Studio, and change the text of a service or add a post.
  • You click “Publish”. The panel lets the site know the content has changed.
  • The site rebuilds in the background, usually in under a minute, and shows the new version.
  • Visitors get ready-made, fast HTML. The panel isn't exposed on the public site.

For an editor the difference is smaller than it sounds: you still fill in fields and click “Publish”. The difference is underneath: in speed, security and how many things can break.

How it differs from WordPress

WordPress does everything at once: it stores content, generates the page on every visit, and runs plugins and themes. That's convenient, but every plugin is code to update, and the login page sits at the site's own address.

A headless CMS only handles content. There are no one-click plugins adding features and risk. New features are added by a developer in the site's code, and you get a panel with exactly the fields you need.

  • Speed: the site is ready-made files, not database queries on every visit.
  • Security: no login page or database at the site's address.
  • Tidy content: instead of one big editor you get fields that match your content, e.g. price, lead time, scope.
  • Less maintenance: no weekly plugin updates.

Downsides worth knowing

  • A new feature, such as a calculator or bookings, is added by a developer. You can't install it yourself like a plugin.
  • Previewing changes before publishing has to be set up. In a well-prepared project it works, but it isn't out of the box.
  • The build costs more than a simple site without a panel, because the panel has to be designed around your content.
  • For shops with many products and platforms with user accounts, WordPress with WooCommerce or an LMS is usually the better fit.

Sanity, Payload or EmDash

Sanity runs in the cloud and handles many editors, change history and rich content well. The free plan covers most company websites.

Payload is installed on your own server, so the data stays with you. It needs a server with Node.js and a database, i.e. stronger hosting than an ordinary website.

EmDash is a lightweight panel from Cloudflare, built on Astro. It suits smaller sites and needs no server to maintain.

FAQ

Frequently asked questions

Is a headless CMS harder to use than WordPress?

Usually it's easier. The panel only has the fields your content needs, without themes, plugins and settings that can break the layout. After a short handover, editors work in it on their own.

How much does a website with a headless CMS cost?

A company website on Astro with a content panel costs €2,490–3,790 net and takes 4–8 weeks. Details on the website with a CMS page. The panel itself, in Sanity or EmDash, is usually free at a typical company website's traffic.

Can I add a headless CMS to my existing website?

Yes. If you're moving your site from WordPress to Astro, the panel can be added during the migration or later. See the WordPress to Astro migration.

Can WordPress work as a headless CMS?

It can: WordPress exposes content through an API, and the site is built separately. That makes sense when the team knows and likes the WordPress dashboard. But the WordPress and plugin updates remain, so for new sites I more often choose Sanity, Payload or EmDash.

Want to see a headless CMS in action?

On a short call I'll show you the demos and tell you straight whether a panel makes sense for your site, or whether a site without one is enough.

Let's talk about your website