A traditional CMS such as WordPress, Drupal or Joomla stores your content and also builds the pages visitors see. A headless CMS such as Sanity, Contentful, Strapi or Storyblok only stores and serves content through an API; a separate front end, usually built with a framework like Next.js, displays it. Choose a traditional CMS when you run one website, need editors to work independently with page templates, and lack in-house developers. Choose headless when the same content must feed several channels (website, app, kiosks, partner sites), when the front end needs custom, high-performance UX, and when developers will own that front end long term.
We are asked about headless on almost every mid-size website project now. Our honest view is that it is the right answer for some projects and an expensive detour for many others. This guide is meant to help you tell which one yours is.
What is a headless CMS, in plain terms?
Think of a traditional CMS as a restaurant with its own dining room: the kitchen (content storage) and the dining room (the website) are one building. A headless CMS is a kitchen that delivers to any dining room you like. The kitchen does not care whether the food ends up on a website, a mobile app or a screen in a showroom.
Technically, "headless" means the content repository is decoupled from the presentation layer. Content is structured into fields (title, summary, body, image, author, related items) and delivered through an API. Developers then decide how each channel displays it.
How do headless and traditional CMSs compare?
| Factor | Traditional CMS | Headless CMS |
|---|---|---|
| What you get | Content storage, editing, themes and page rendering in one system | Content storage, editing and an API; the front end is built separately |
| Editor experience | Page-based, with visual layouts and templates | Field- and block-based; visual editing depends on the product and setup |
| Launch speed | Faster for standard sites using themes | Slower; front end built from scratch |
| Front-end freedom | Limited by the theme system | Complete; any framework or channel |
| Multi-channel delivery | Possible, but awkward | Designed for it |
| Performance | Good with careful build and caching | Very high potential with static and edge rendering |
| Hosting | One server or managed host | CMS (often SaaS) plus front-end hosting |
| Maintenance | One system to update | Two systems, plus the integration between them |
| Skills needed | CMS developer, often available locally | Front-end framework developers plus CMS configuration skills |
| Typical examples | WordPress, Drupal, Joomla | Sanity, Contentful, Strapi, Storyblok, headless WordPress |
When is a traditional CMS the better choice?
A traditional CMS is usually better when:
- You run one website and have no plans for an app or other channels.
- Editors need to build and rearrange pages themselves with ready-made templates.
- There are no in-house developers, and you want to avoid depending on one for routine changes.
- You need to launch relatively quickly.
- You rely on plugins for features such as forms, events, multilingual content or e-commerce.
Even Contentstack, a headless CMS vendor, says a coupled CMS can be the better choice when content changes rarely, visual presentation is a low priority, content creators cannot code and need templates, or there are no in-house developers (Contentstack). When the vendor selling headless tells you when not to use it, it is worth listening.
When is headless the better choice?
Headless usually earns its place when:
- Content is reused across channels. Product information that feeds the website, mobile app, in-store screens and partner portals.
- The front end is a product in itself. Interactive tools, configurators, personalised dashboards or a marketing site that shares components with your React app.
- Performance at scale matters commercially. Large sites with heavy traffic where static or edge rendering pays off.
- Several sites share one content source. Regional sites or brands pulling from a central library.
- Developers will own the front end. In-house or through a long-term partner.
What are the hidden costs and risks of going headless?
These are the issues we see buyers discover after they have committed:
- Preview is not automatic. In a traditional CMS, editors click "preview" and see the page. In headless, a preview environment must be built so drafts render on the real front end.
- Page building can be harder for editors. Unless the content model includes flexible blocks or the product supports visual editing, editors may only be able to fill fields in fixed templates.
- Plugins do not carry over. On headless WordPress, plugins that output front-end HTML (forms, sliders, page builders) do not appear on the new front end. Each must be rebuilt.
- SEO controls must be built. Titles, meta descriptions, canonical tags, structured data, redirects and XML sitemaps are not automatic. They need fields in the CMS and logic in the front end. Google's JavaScript SEO basics explain why server-rendered or pre-rendered pages are the safer choice for search.
- Two bills and two update cycles. A SaaS CMS subscription (often priced by seats, locales and API usage) plus front-end hosting, and dependency updates on both sides.
- Vendor dependence moves, it does not disappear. You avoid theme lock-in but depend on a CMS vendor's API and pricing.
How does the content model change your project?
With headless, the content model is the foundation. Before design starts, someone must define each content type, its fields, and how types relate. For example:
| Content type | Example fields | Relationships |
|---|---|---|
| Service | Title, summary, body blocks, FAQs, hero image, SEO fields | Related case studies, industries |
| Case study | Client industry, challenge, approach, outcome, gallery | Services used |
| Location | Address, hours, map coordinates, local phone | Services offered there |
| Author | Name, role, bio, photo | Articles written |
A good content model makes the site easier to grow. A rushed one locks editors into awkward workarounds. Budget real time for this step, and involve the people who will actually edit the site. A design system that matches the content blocks keeps the front end consistent.
Is there a middle ground?
Yes. Several options sit between fully traditional and fully headless:
- Hybrid CMS. Some platforms offer both page rendering and an API, so you can start traditional and expose content to an app later.
- Headless WordPress. Editors keep the WordPress admin; a Next.js front end renders the site. Useful when the team already knows WordPress.
- Visual headless products. Some headless CMSs include visual editing and page building, closing much of the editor gap.
- Start traditional, decouple later. Build a clean content model in a traditional CMS now, and add an API front end when a second channel appears.
If your headless front end will use React, read is React good for SEO? Next.js vs a single-page app before you choose a rendering approach.
What should a headless CMS proposal include?
Because headless projects have more moving parts, proposals vary more than for traditional builds. Check that a proposal covers each of these explicitly:
- Content model workshop with your editors, producing a documented list of content types and fields.
- CMS choice and plan, with the reason it fits your team size, locales and API needs.
- Front-end framework and rendering strategy, including which pages are pre-rendered and how content changes go live.
- Preview environment so editors can see drafts on the real design.
- SEO fields and logic: titles, descriptions, canonical tags, structured data, redirects and XML sitemap.
- Forms, search and other features that a theme or plugin would normally handle.
- Hosting for both parts, with monitoring and who is responsible for each.
- Editor training and documentation, because the editing experience differs from a page builder.
- Ongoing support, covering CMS updates, dependency upgrades and new components.
If several of these are missing, the proposal is either assuming you will handle them or planning to bill for them later. Ask which.
A decision checklist
Score each statement "yes" or "no":
- We publish the same content to more than one channel, or will within a year.
- Our website needs custom interactive features a theme cannot reasonably provide.
- We have, or will contract, developers to own the front end long term.
- Performance at large scale has a measurable business value for us.
- Our editors are comfortable working with structured fields rather than visual page building, or the chosen CMS offers visual editing.
Four or five "yes" answers: headless is likely worth it. Two or three: consider a hybrid or headless WordPress. Zero or one: a well-built traditional CMS will serve you better and cost less to run.
Bottom line
Headless CMS architecture separates content from presentation, which pays off for multi-channel content, custom front ends and large-scale performance, if you have developers to own it. For a single business website run by a marketing team, a traditional CMS with a clean custom theme is usually faster to launch and simpler to maintain.
If you are deciding between the two, our website development and React.js development teams can help you design the content model and estimate both routes. Book a free consultation to talk it through.






