What Is a Headless CMS Website? A Plain-English Guide for Marketing Teams
What you're agreeing to when an agency proposal says "headless CMS", in the language of the person who edits the site every week.
Somewhere in an agency proposal, between the timeline and the price, sits a line like "headless CMS (Sanity)" — and everyone nods and nobody asks. This guide is for the person who has to edit that website every week and would like to know what they're agreeing to.
No jargon, no architecture diagrams that need their own glossary. Just what changes, what your Tuesday looks like, what the common platforms cost, and when you should say no to the whole idea.
Quick answer: A headless CMS is a content system that stores your text, images, and data separately from the website that displays them. Editors write and publish in a friendly editing app; the website pulls that content in and presents it. Because the two are separate, the site can be built for speed, and a future redesign changes the presentation without touching the content.
The one idea: your content and your website become two things
| Approach | How it's put together |
|---|---|
| Traditional CMS (WordPress) | Content + design + plugins + the server your visitors hit. One system, one machine, every risk shared. |
| Headless (Sanity + Astro) | A content studio where editors work → a fast static site that visitors get. |
A traditional CMS is one system doing two jobs: it stores your content and it builds the pages visitors see, on the same server, usually in the same breath. That coupling is why WordPress is easy to start and awkward to keep fast: every theme, plugin, and editor choice lives in the machine that serves your visitors.
A headless setup splits the jobs. The CMS keeps only the content; "headless" means it has no public-facing front end of its own. Your actual website is built separately (in our case with Astro, pre-rendered to fast static pages) and pulls content from the CMS when it builds. Editors never touch the website's code; developers never touch the content.
Two practical consequences fall out of that split. The site gets fast, because what visitors receive is pre-built HTML rather than something assembled on demand, the gap explained in why WordPress sites struggle to stay fast. And redesigns get cheaper, because your content library survives untouched while the presentation is rebuilt around it. Content entered once outlives several designs.
What editing actually looks like day to day
The fear is always that "headless" means "developers only." In practice the editing experience is the part that improves most. Here is the honest Tuesday-afternoon comparison:
| Task | Sanity Studio | WordPress admin |
|---|---|---|
| Edit a blog post | Structured fields, live preview of the real page | Gutenberg or a page builder; preview approximates the theme |
| Update a stat appearing on 12 pages | Change it once; every page updates | Find and edit all 12 pages |
| Break the layout with an edit | Not possible — presentation is locked in code | Routinely possible with page builders |
| Work simultaneously with a colleague | Real-time collaboration, like Google Docs | Post locking: one editor at a time |
| Publish | Click publish; the site rebuilds in minutes | Click publish; pray the cache clears |
| Install a plugin that slows the site | No plugins exist to install | The classic failure mode |
The trade: you cannot drag a new page layout together yourself. New page types are developer work. For teams that mostly write, update, and publish inside established designs (which is most marketing teams), that constraint is the feature: the site always looks like the design.
The common choices, compared honestly
| Platform | Editing experience | Pricing shape | Best for |
|---|---|---|---|
| Sanity | Structured fields, live preview, real-time collaboration; studio customized to your content | Generous free tier (~20 seats); ~$15/seat paid | Marketing sites with a dev partner; our default |
| Contentful | Polished, corporate, approachable | Small free tier, then ~$300/mo | Enterprises with multi-site content hubs |
| Storyblok | Visual block editor marketers consistently love | Free 1 seat; Growth from ~€99/mo | Teams wanting Webflow-like visual editing, headless benefits |
| Payload | Clean, developer-flavored | Open source, self-hosted free | Dev-heavy teams, no SaaS bill |
| Headless WordPress | The wp-admin you know | Free + hosting + maintenance | Teams locked into WP workflows — but you keep the PHP burden |
Pricing moves often in this market; treat the figures as the shape of each model and check vendor pages for current numbers.
When a traditional CMS is still the better fit
Headless is not a universal upgrade. Stay traditional when the site is small and budget-led (a Squarespace site needs no architecture discussion), when your site's value depends on a plugin ecosystem (deep WooCommerce, LMS, memberships), when there is no developer or agency relationship at all (a headless site without a dev partner is a car without a mechanic), or when the editorial team's WordPress muscle memory genuinely outweighs the performance gains.
What you're buying when an agency proposes a headless build
- Content modeling: your content types designed as structured fields. Ask to see the field layout for your most-edited page type.
- A customized editing studio: not a generic dashboard. Ask for a demo with your real content in it.
- The front-end build: the actual website, pre-rendered for speed. Ask what Lighthouse scores they'll commit to.
- Preview and publishing flow: how an editor sees changes before they're live, and how long publish-to-live takes.
- Training and documentation: an hour in a well-built studio is usually enough; ask for it to be included.
- The CMS bill: who pays it, and what tier you'll actually need (often: the free tier).
That package is standard in our custom website design and development work, with Sanity as the default studio, and what a custom website costs in 2026 covers where it lands in the budget.
Frequently Asked Questions
What is a headless CMS in simple terms?
A content system with no website attached. It stores your text, images, and data; a separately built website pulls that content in and displays it. Editors get a clean editing app, developers get full control of the site, and the two can't break each other.
Is headless WordPress a real option?
Yes: WordPress can run as a content-only back end feeding a modern front end. Teams choose it to keep familiar editorial workflows. You gain front-end speed but keep WordPress's PHP hosting, updates, and security maintenance, so it captures part of the benefit, not all of it.
Can non-technical editors use a headless CMS?
That's who it's for. Day-to-day writing, editing, image swaps, and publishing happen in a visual studio with live preview and no code. The developer-only work is creating new page types and changing designs, which is true on any professionally built site.
Sanity vs Contentful: which is better for a marketing site?
For most small and mid-sized marketing teams, Sanity: its free tier covers a typical team (around 20 seats), the studio is customized to your content, and live preview and collaborative editing are built in. Contentful's strengths (governance, multi-site content reuse) matter most at enterprise scale, where its pricing (from roughly $300/month) makes sense.
Does a headless CMS make my website faster?
Indirectly, yes. Separating content from presentation lets the website be pre-rendered to static pages served from a CDN, which is what makes sub-second loads routine. The CMS itself never slows a visitor down because visitors never touch it.
Spend 30 minutes with our owner.
Book a Strategy CallPrefer to see a number first? Try the pricing calculator.