# Why Are Marketers Buying Headless CMSs?

> Headless used to describe an architecture. Today it describes a sales pitch. The platforms met in the middle because marketers refused to manage content in a database with a login.

Analyst Editorial by DXP Principal Analyst Group · Published 2026-10-24 · Not updated
Source: https://www.dxpscorecard.com/editorials/why-are-marketers-buying-headless-cms

## The short answer

Marketers are buying headless CMSs because the products stopped being headless. The term once meant structured content behind an API with no way to build a page. Storyblok, Contentful, Sanity and Contentstack have since attached visual editors and live preview, while SitecoreAI, Optimizely and WordPress opened their content through GraphQL and REST APIs. The two camps met in the middle, and the marketers decided where the middle was.

## Key takeaways

- Headless originally meant one thing: content stored as structured data, delivered through an API, with no visual way to build a page. It was fast to launch, cheap to run and developers loved it. Marketers were handed a form.
- Every headless CMS that sells to marketing teams has since reattached the head. Storyblok's Visual Editor, Contentful's live preview and inspector mode, Sanity's preview on the real website, Contentstack's Visual Editor, Hygraph's Click to Edit and Strapi's Live Preview all put the page back in front of the editor.
- The suites and the traditional platforms moved the other way. SitecoreAI delivers through the Experience Edge GraphQL API, Optimizely through Optimizely Graph, Adobe Experience Manager through GraphQL and an OpenAPI delivery API, and WordPress through its core REST API and WPGraphQL. Each of them kept its visual builder.
- The marketers won. Nobody who owns a website wanted to manage it in something that looked like a step above a database. Page building and preview were non-negotiable, so every vendor built them, and now everything looks the same.
- Buy the editing experience and the API you can see in a trial, not the label. Headless no longer tells you whether a marketer can build a page, and DXP no longer tells you whether developers get a clean API. Both are table stakes, and the word will eventually be retired. We will keep using it until buyers stop searching for it.

## Our analysts' take

Start with the question nobody in the vendor meeting wants to ask out loud: what is a headless CMS? The original answer was simple. The head is the website, the part a visitor sees. The body is the content repository, the part an editor works in. A traditional CMS such as WordPress glued the two together: one system stored the content, rendered the pages and gave the editor a preview of the result. A headless CMS cut the head off. It stored structured content, served it through an API and left the website itself to the developers, who built it in whatever framework they liked and hosted it wherever they liked. The CMS became a database with a nice form on top. That was the whole pitch, and around 2016 to 2019 it was a good one. Contentful, Sanity, Strapi and Hygraph went to market as lightweight, inexpensive, developer-first products that could be live in days, and the MACH Alliance (microservices, API-first, cloud-native, headless) formed in 2020 to turn the idea into a procurement checkbox.

The catch was the person who had to use it every day. A marketer managing a campaign in an early headless CMS filled in fields called hero_title and cta_variant, pressed publish and then opened the website in another tab to see whether anything had broken. There was no page to drag a component onto, no preview that matched the finished site, and every new layout was a developer ticket. Developers were delighted. Marketing teams, who in most organizations own the website and its budget, were not, and they said so in every renewal conversation. The vendors listened, because the vendors needed the marketing budget. Storyblok built its entire product around a visual editor on a live preview of the real site and grew on that alone. Contentful added live preview and an inspector mode that clicks from any element on the page to the field behind it. Sanity added preview on the real website with click-to-edit overlays. Contentstack built a Visual Editor and now sells itself as a digital experience platform rather than a headless CMS. Even Strapi, the open-source developer favourite, added Live Preview with double-click editing on its paid plans. The head grew back.

Meanwhile the platforms that always had a head grew an API. Sitecore moved its content delivery onto the Experience Edge GraphQL API, rebuilt its page builder to edit a headless front end, and the product that was XM Cloud is now SitecoreAI. Optimizely made Optimizely Graph the GraphQL delivery layer for its SaaS CMS and put Visual Builder, a drag-and-drop editor, on top of your own Next.js or Astro site. Adobe Experience Manager delivers Content Fragments over GraphQL and an OpenAPI delivery API, and its Universal Editor puts click-to-edit overlays on a React front end. WordPress has shipped a REST API in core since version 4.7 in December 2016, and the WPGraphQL plugin feeds Next.js sites from a stock install. So the headless vendors added page builders, the suites added APIs, and they met in the middle. In our view the term has lost its meaning. We expect the industry to sunset it and sort platforms some other way: enterprise DXP versus CMS, with API delivery assumed the way responsive design is assumed, or under a new name such as Content Orchestration Hub or AXP, the Agentic Experience Platform, now that AI agents are becoming the main consumer of the API. We will probably retire the Headless CMS section of this site when that happens. Will The DXP Scorecard be the first to move on from the word? Probably not; others are surely doing it already, and we are comfortable following. For now the term stays, because buyers still search for it, vendors still sell with it, and the first thing a non-technical buyer asks is still what it means. The honest answer in October 2026 is: not what it says. This is where the Principal Analyst Group stands.

## What to look for

1. **A page builder on your real site.** Ask whether a marketer can click a component on the rendered page, insert an approved section and move it, or whether they fill in fields next to a preview window. Every vendor on this page now says yes to visual editing. The difference between a canvas and a form beside a preview is the difference between a campaign page in an hour and a ticket.
2. **An API your developers would choose.** Separate delivery and management APIs, GraphQL or REST with filtering and pagination, and official SDKs for the framework your team already uses. This was once the headless differentiator. SitecoreAI, Optimizely, Adobe Experience Manager and WordPress all offer it now, so check the quality rather than the presence.
3. **Who builds and runs the front end.** Headless still means the website is a separate application that your team or your agency builds and hosts on Vercel, Netlify, Cloudflare or your own cloud. SitecoreAI, Optimizely SaaS CMS and Storyblok all leave the front end to you. Budget for the developer who maintains the component library after launch, because the page builder only offers what that library contains.
4. **What is in the box after the CMS.** Personalization, A/B testing, site search, forms and analytics. Storyblok, Contentful, Sanity and Hygraph ship almost none of them and expect you to connect other products. SitecoreAI bundles personalization and testing into the base license, while Optimizely sells them as separate products. The label headless or DXP predicts nothing here; the price list does.
5. **A door for the AI agents.** The next head is not a website, it is an agent. Ask for the official MCP (Model Context Protocol) server, which lets Claude, ChatGPT or Copilot read and write the content under your permissions, and ask which parts of the platform it reaches. Contentful, Sanity, Strapi, Storyblok, SitecoreAI and Optimizely all ship one. This is the capability that will define whatever we end up calling these platforms next.

## How headless lost its meaning in three moves

The word did mean something precise for about five years. Here is how it drifted, in the order it happened.

- **Move one: the API with no page.** Contentful, Sanity, Hygraph and Strapi arrived as content repositories with delivery APIs and an entry form. The website was the customer's problem, built in React, Vue or whatever came next and deployed to a static host. The products were cheap, quick to adopt and simple to reason about, and an engineering team could have one live in an afternoon. Preview, if it existed, was a URL a developer wired up. This is the only moment the word headless was literally true.
- **Move two: the head grows back.** Storyblok proved that a visual editor on a live preview of the real front end could sell a headless CMS to marketing teams, and the rest followed. Contentful added live preview, inspector mode and shareable preview links. Sanity added preview on the real website with click-to-edit. Contentstack added Live Preview and a Visual Editor and started calling itself a digital experience platform, which is why it already sits in our Enterprise DXP column rather than the headless one. Hygraph added Live Preview and Click to Edit, though still without a drag-and-drop canvas. Strapi added Live Preview with double-click editing on its Growth and Enterprise plans. The content model stayed structured; the marketer got a page again.
- **Move three: the suites open an API.** Sitecore put content delivery on the Experience Edge GraphQL API and rebuilt its page builder around a headless front end, so SitecoreAI is, by the old definition, a headless CMS with a very large suite attached. Optimizely made Optimizely Graph its delivery layer and ships Visual Builder for a Next.js or Astro site; its SaaS CMS sits in our Headless CMS column for exactly that reason. Adobe Experience Manager delivers Content Fragments over GraphQL and an OpenAPI delivery API and edits any front end through Universal Editor. WordPress has had a REST API in core since 2016 and WPGraphQL has turned it into a back end for thousands of Next.js sites. Once the suites and the traditional platforms do what headless did, and the headless platforms do what the suites did, the word no longer sorts anything.

## What replaces the word, and when we will stop using it

A label survives as long as it helps a buyer narrow a shortlist. Headless no longer does that, so something will replace it. Here is what we think the candidates are, and why we are not switching yet.

- **Enterprise DXP or CMS, with the architecture as a footnote.** The most likely outcome is that the market sorts platforms by what is in the box rather than how it is delivered. A CMS holds the core content features. An enterprise DXP adds personalization, experimentation, analytics, customer data and asset management on the same content. API delivery becomes an assumed property of both, the way nobody advertises a responsive website any more. If we remove the Headless CMS section of this site, this is the shape it collapses into.
- **Content Orchestration Hub.** The term emerging for the content repository whose job is to feed many destinations at once: websites, apps, commerce, email, digital signage and now AI agents. It describes what the former headless vendors actually do for large customers, and it has the advantage of saying what the thing is for rather than what it lacks.
- **AXP, the Agentic Experience Platform.** The newest candidate, and the one tied to a real change in how content is managed. When Claude, ChatGPT or a vendor's own agents create, translate, audit and publish content through an MCP server, the primary consumer of the API is no longer a website build but an agent, and the primary editing interface is a conversation. A platform designed around that is doing something different from a headless CMS, and it may deserve a different name.
- **Why we are keeping headless for now.** Buyers type it into search engines, vendors print it on pricing pages, and analysts still group platforms by it. Dropping the word before the market does would make our Headless CMS section harder to find without making it more accurate. The only argument for moving sooner is that non-technical buyers still need the term explained, and when we explain it they rightly point out that the product in front of them is not headless at all. We will follow the industry on this one, and we are fine with that.

## Questions to ask before you buy anything called headless

- **Show me a marketer building a landing page.** In the trial, on a copy of your own front end, with no developer in the room. Insert a component, reorder two sections, change an image and publish. If any step needs a ticket, the head is not as attached as the demo suggested.
- **Where does my website actually run?** On most headless platforms, and on SitecoreAI and Optimizely SaaS CMS, the answer is a separate application your team deploys to Vercel, Netlify, Cloudflare or your own cloud. Ask who builds it, who maintains the component library and what happens to the page builder when that developer leaves.
- **Which API, and what does it cost at volume?** Ask for the delivery API your developers will use, GraphQL or REST, and how the plan meters it: API calls, bandwidth, entries, locales or seats. The quietest cost overruns in headless projects come from preview traffic and a mobile app nobody budgeted for.
- **What else is in the license?** List personalization, A/B testing, search, forms and analytics and ask which are included, which are separate products from the same vendor and which are someone else's. Storyblok, Sanity and Contentful ship almost none of them. SitecoreAI bundles several. Optimizely licenses them separately. The total is what you are comparing, not the CMS line.
- **Is there an MCP server, and what does it reach?** If you expect AI agents to publish, translate or audit content in the next two years, the official MCP server matters more than any button in the editor. Ask whether writes land as drafts, whether tokens can be scoped, and whether the server reaches the whole suite or only the content. This is the question that will outlive the word headless.

## Platforms in this piece

- [Storyblok](https://www.dxpscorecard.com/platform/storyblok) (Markdown: https://www.dxpscorecard.com/platform/storyblok.md)
- [Contentful](https://www.dxpscorecard.com/platform/contentful) (Markdown: https://www.dxpscorecard.com/platform/contentful.md)
- [Sanity](https://www.dxpscorecard.com/platform/sanity) (Markdown: https://www.dxpscorecard.com/platform/sanity.md)
- [Contentstack](https://www.dxpscorecard.com/platform/contentstack) (Markdown: https://www.dxpscorecard.com/platform/contentstack.md)
- [Hygraph](https://www.dxpscorecard.com/platform/hygraph) (Markdown: https://www.dxpscorecard.com/platform/hygraph.md)
- [Strapi](https://www.dxpscorecard.com/platform/strapi) (Markdown: https://www.dxpscorecard.com/platform/strapi.md)
- [SitecoreAI](https://www.dxpscorecard.com/platform/sitecore-ai) (Markdown: https://www.dxpscorecard.com/platform/sitecore-ai.md)
- [Optimizely SaaS CMS](https://www.dxpscorecard.com/platform/optimizely-saas) (Markdown: https://www.dxpscorecard.com/platform/optimizely-saas.md)
- [Adobe Experience Manager](https://www.dxpscorecard.com/platform/aem) (Markdown: https://www.dxpscorecard.com/platform/aem.md)
- [WordPress](https://www.dxpscorecard.com/platform/wordpress) (Markdown: https://www.dxpscorecard.com/platform/wordpress.md)

## Frequently asked questions

### What is a headless CMS in plain English?

A headless CMS stores your content as structured data and hands it to any website or app through an API, instead of rendering the pages itself. The website, the head, is a separate application your developers build and host. In its original form it had no visual page builder, which is why the term was coined. Most headless CMSs now include visual editing and live preview, so the name describes the architecture rather than the editing experience.

### Is a headless CMS good for marketers?

It can be, if the vendor has attached a visual editor and your developers have built a library of components for it. Storyblok, Contentful, Contentstack and Sanity all offer editing on a live preview of the real site. Without that component library the marketer is back to filling in fields and raising tickets, so judge the editing experience in a trial rather than trusting the architecture.

### What is the difference between a headless CMS and a traditional CMS?

A traditional CMS such as WordPress stores content, renders the pages and previews them in one system. A headless CMS stores content and serves it through an API, leaving the website to a separate front end. The practical gap has closed: WordPress ships a REST API in core and WPGraphQL feeds headless sites, while headless platforms have added page builders. Today the real differences are who hosts the front end and what else the license includes.

### Is WordPress a headless CMS?

It can be used as one. WordPress has included a REST API in core since version 4.7 in December 2016, and the WPGraphQL plugin exposes posts, custom post types and Advanced Custom Fields data to a Next.js or similar front end. It remains a web-first system with HTML stored in its rich text, so it is a less tidy content repository than a purpose-built headless CMS, but the label no longer excludes it.

### Is the term headless CMS going away?

We think so, though not immediately. Headless platforms have added visual editors and suites such as SitecoreAI, Optimizely and Adobe Experience Manager have added GraphQL delivery, so the word no longer separates products. Expect the market to sort platforms as enterprise DXP versus CMS, or to adopt a new name such as Content Orchestration Hub or Agentic Experience Platform as AI agents become the main consumer of the content API. Until buyers stop searching for it, we will keep using it.

### What is an Agentic Experience Platform (AXP)?

An emerging term for a content and experience platform designed to be operated by AI agents rather than by people in an editing screen. Agents create, translate, audit and publish content through the platform's MCP (Model Context Protocol) server under human-set permissions, and the website or app is one of several destinations the content reaches. Most vendors are moving this way through their MCP servers and agent tools; the name is still settling.

## About this editorial

A position the DXP Principal Analyst Group took on 2026-10-24. It is not updated; a changed view is published as a new editorial. The linked scorecards carry the current ratings for every platform named here. Scorecards and platform inclusion are unsponsored: no vendor pays to be named in an editorial or to change a rating.