# Headless CMS, explained without the jargon | Plyo

> What headless actually means, when separating your content from your website is worth the extra setup, and when a traditional CMS is the better buy.

Source: https://plyo.studio/blog/headless-cms-explained

1.  [Home](/)
2.  [Blog](/blog)
3.  Headless CMS, explained without the jargon

# Headless CMS, explained without the jargon

What headless actually means, when separating your content from your website is worth the extra setup, and when a traditional CMS is the better buy.

Plyo Studio 22 January 2026 6 min read

On this page

[The difference in one example](#the-difference-in-one-example)[When headless is worth it](#when-headless-is-worth-it)[When it is not](#when-it-is-not)[What it looks like in practice](#what-it-looks-like-in-practice)[Picking one](#picking-one) [Common questions](#common-questions)

Related service

[Astro websites](/services/astro)

A headless CMS stores your content and nothing else. It has no opinion about how the content looks or where it appears. Your website asks for the content and decides how to display it. The “head” that is missing is the front end.

## The difference in one example

In a traditional CMS, a blog post and the page it appears on are the same thing. The CMS owns the template, the styling and the URL.

In a headless CMS, the post is just structured data: a title, a body, an author, a date, a cover image. Your website requests it and renders it. So does your app, your email newsletter and the screen in reception, all from one source.

## When headless is worth it

-   **The same content appears in more than one place.** A website and a mobile app. A website and a customer portal.
-   **Your content has real structure.** Products with variants, properties with coordinates, events with venues. Things a page editor models badly.
-   **You want the front end free.** Rebuild or redesign the site without migrating content, because the content was never inside the site.
-   **Several teams write.** Proper roles, review workflows and scheduling.

## When it is not

-   A five page brochure site. The setup cost buys you nothing.
-   A team that wants to see the page while they edit it. Headless editors show fields, not pages. Some people find that abstract and quietly stop using it.
-   No developer available. Headless assumes someone builds the front end. That is the whole point of it.

For most marketing sites, a visual CMS like [Webflow](/services/webflow) is the better buy, because the people editing can see what they are changing.

## What it looks like in practice

We often pair a headless CMS with [Astro](/services/astro). The content lives in something like Sanity or Storyblok. At build time Astro pulls it and writes out plain HTML pages. The visitor gets a static page that loads instantly, and the client gets a proper editing interface.

The trade is that content changes need a rebuild, which takes a minute or two and happens automatically when someone hits publish. For a site that updates a few times a week, nobody notices. For a live price feed, that model is wrong and you want rendering on demand instead.

## Picking one

The main options behave quite differently.

System

Suits

Watch for

Sanity

Complex, deeply structured content

The editor needs configuring, it is not off the shelf

Storyblok

Marketing teams who want a visual preview

Pricing climbs with users and spaces

Contentful

Larger organisations, strong governance

The most expensive of the three

Markdown in the repo

Developer written docs and posts

No interface for non technical staff

The right question is not which is most capable. It is which one your team will still be using in a year.

If you are weighing this up, tell us where your content needs to appear and we will say honestly whether headless is worth it.

## Keep reading.

[All posts](/blog)

-   [
    
    Engineering Image formats and sizes for a fast website 7 min read](/blog/image-formats-for-a-fast-website)
-   [
    
    Engineering Contact forms: stopping spam without losing enquiries 6 min read](/blog/contact-forms-stopping-spam)
-   [
    
    Engineering Multi-language and multi-region websites 7 min read](/blog/multi-language-and-multi-region-websites)

Updated 22 January 2026

FAQ

## Common questions

[Ask a question](/contact)

### Is headless better for SEO?

Not inherently. What matters is that the pages are rendered as real HTML with proper meta data. A headless setup built on a framework that pre-renders is excellent. One that renders everything in the browser can be a problem.

### Can I move from WordPress to headless?

Yes, and the content usually exports cleanly. The bigger job is modelling it properly on the way in rather than copying the old structure across unchanged.

### Does headless cost more?

Up front, usually. There is a front end to build that a traditional CMS would have given you. It pays back when the content outlives the website, or feeds more than one place.

About Plyo Studio

## Custom Astro websites. Built on Cloudflare.

Plyo Studio is an independent web studio that designs and builds fast, search-ready websites, web apps and interactive maps. Sites are custom-built in Astro and hosted on Cloudflare, so they load quickly and are easy for search engines and AI answer engines to read.

Founded by Chloe Nixon, a full stack developer and UI/UX designer from Australia, and Micky, a software engineer from New Zealand. Clients work directly with the founders from the first call to launch. Typical work: custom websites, migrations off Webflow, WordPress, Wix and Squarespace, web apps, and interactive maps and GIS. Projects are quoted at a fixed price before work starts.

[Start a project](/contact) [hello@plyo.studio](mailto:hello@plyo.studio) [About us](/about)

## Related pages

-   [Blog Read practical notes on designing, building and moving websites.](/blog)
-   [Astro websites Custom sites pre-built into lean HTML, for speed and search.](/services/astro)

Start a conversation

## Ready for a website that works harder?

[Start a project](/contact) [Free website audit](/audit)
