What Is a Headless CMS, and When Does a Marketing Site Need One?
A headless CMS is a content system that stores content and sends the content to any front end through an API. In “What Is a Headless CMS, and When Does a Marketing Site Need One?”, Pavlo Zhydkykh compares headless and traditional setups and says when a startup site gains from one.
Pavlo ZhydkykhUpdated · 7 min read
Short answer
What is a headless CMS, and does your startup site need one? Founders ask me this when a rebuild is on the table, usually after a vendor demo full of words like API-first and composable. I build marketing sites on Framer, where the CMS is part of the builder, and on Astro + Sanity, where the CMS is headless. This guide explains the difference in plain terms and says when the headless route pays off and when the simpler setup wins.
Key takeaways
- A headless CMS is a back end only system that makes content available through an API, without a built-in front end.[1]
- The Astro docs recommend a headless CMS for Astro sites, because Astro handles the presentation of the content.[3]
- Sanity’s Free plan costs $0 and includes up to 20 user seats; the Growth plan is $15 per seat a month (checked 6 Nov 2026).[4]
- None of the major AI crawlers render JavaScript, so a headless site needs a front end that sends finished HTML.[5]
- Pavlo Zhydkykh builds headless sites on Astro + Sanity: a landing page from $1,200, a multi-page site from $3,000.
What is a headless CMS?
A headless CMS is a content management system that stores and organises content but has no built-in front end; a headless CMS delivers the content through an API to a website, app or other channel. A traditional CMS such as WordPress stores the content and renders the pages in one system.
Wikipedia: Headless content management system
“Go headless when content brings the leads and grows every month. For a small site your team designs, a builder is enough.”
Last checked · 7 min read
What is a headless CMS?
A headless CMS is a content management system with no website attached. Wikipedia describes it as a back end only system that acts as a content repository and makes content available through an API, without a built-in front end. The "head" is the part visitors see: the pages, the layout, the design. A headless CMS keeps the body (the content) and leaves the head to a separate front end.
A traditional CMS such as WordPress does both jobs in one application. The same system stores your posts, holds the theme and renders the page when someone visits. That is why the industry calls it coupled or monolithic.
The category keeps growing. Wikipedia cites Grand View Research, which valued the headless CMS software market at US$1.8 billion in 2025 and projects US$6.2 billion by 2033. You do not need a market report to decide, though. You need to know who edits the site and what the site has to do.
How a headless CMS works on a marketing site
On an Astro + Sanity site, which is the headless stack I build, the work splits in three parts:
- Editors write in the CMS. Sanity gives the team a form for each content type: a blog post, a case study, a pricing plan, a job opening. Required fields stop half-finished entries from going live.
- The front end asks for the content. Astro fetches the entries through the CMS API when the site builds and turns them into finished HTML pages.
- Visitors get static pages. The pages are served from a CDN such as Cloudflare Pages, so a visit never waits for a database.
The Astro docs put the split simply: because Astro takes care of presentation, you choose a headless CMS, which helps you write content but does not generate the site that displays it. Sanity's own headless CMS guide frames the same idea from the other side: authors focus on content, developers focus on code.
Headless CMS vs traditional CMS
Here is how the two models compare for a startup marketing site. The headless column describes the setup I deliver; other headless products differ in the details.
| Traditional CMS (WordPress, built-in builder CMS) | Headless CMS (Sanity with Astro) | |
|---|---|---|
| What it is | Content, theme and page rendering in one system | Content only, delivered to any front end through an API |
| Editing | Edit the page you see, often with a visual editor | Edit structured fields, with a live preview of the page |
| Where pages come from | Rendered by the CMS, often on each visit | Built by the front end into static HTML |
| Reuse | Content is tied to one website | The same entries can feed the site, the docs, the app |
| Setup effort | Low: install a theme or start in the builder | Higher: a developer models the content and builds the front end |
| Best for | Small sites and teams that design pages themselves | Content-heavy sites, several channels, speed and AI search |
The line between the two is blurring. Wikipedia notes that website builders such as Wix and Webflow have added APIs or headless content features next to their own page rendering, often called hybrid or decoupled CMS platforms.
When a marketing site needs a headless CMS
In my experience, a startup site gains from a headless CMS when two or more of these are true:
- The site is mostly content: a blog, docs, use case, integration and comparison pages that grow every month.
- The same content appears in more than one place, such as the website, the product's help center and an in-app changelog.
- Marketing publishes often and should never need a developer to add a post, a case study or a new hire.
- Speed is part of the pitch, as it is for developer tools, AI products and fintech, where a slow site reads as a slow product.
- You want the content in an account you own, separate from the design, so a future redesign does not mean re-entering every page.
That last point is the one founders underrate. When content lives apart from the layout, a redesign touches templates only. I covered the same idea for teams leaving a builder in my Astro vs Webflow comparison.
When a headless CMS is the wrong call
Headless is not an upgrade for every site. Wikipedia lists the main downside plainly: more effort to set up and configure, and some web development knowledge on both the front and the back end. For a startup that means:
- A five page site that rarely changes does not need a content model. A builder with its own CMS is faster to launch and cheaper to run.
- A team that redesigns pages every week wants a visual canvas. In a headless setup editors change text, images and whole articles, but a new kind of section needs a developer. Framer keeps that freedom; my Framer CMS guide shows how far its built-in CMS goes.
- Nobody owns the code. A headless site has two parts to keep running, the CMS and the front end. If no one on the team or on retainer can own the repository, choose a builder.
What headless means for SEO and AI search
A headless CMS does not rank a site by itself. What matters is the HTML the front end sends. A crawl study by Vercel and MERJ found that none of the major AI crawlers render JavaScript, so a page whose text appears only after a script runs is close to invisible to ChatGPT and Perplexity.
That is the risk with headless sites built as JavaScript apps that fetch content in the browser. A static front end avoids it: Astro builds every page into HTML ahead of time, so every word is in the response. Structured content also helps here. Because a case study in Sanity has a client, a problem and a result as separate fields, the same fields can feed the page, the schema markup and the llms.txt file without anyone copying text by hand.
How to choose a headless CMS
The Astro docs list more than 40 CMS guides, from Contentful and Storyblok to Strapi, Payload and Sanity, and point to a directory of over 100 headless systems. For a startup marketing site I check four things:
- The editor. Can your marketer use it without training? Ask for a trial and publish a test post yourself.
- Preview. Editors need to see the page before it goes live, not only a form.
- The free tier. Sanity's Free plan costs $0 and includes up to 20 user seats, two public datasets and Visual Editing; the Growth plan is $15 per seat a month (checked 6 Nov 2026).
- The exit. Your content should export cleanly, so the CMS never becomes the next lock-in.
Sanity is the one I set up, because its content model is code I can version and its free plan covers most startup teams. If your site already runs on WordPress, the content can move into Sanity during a WordPress to Astro migration.
What a headless setup costs
The running cost can start near zero: Sanity's Free plan and a static host such as Cloudflare Pages cover a typical startup site. The real cost is the build, because someone has to model the content and write the templates once.
My prices are fixed before work starts. A headless CMS site on Astro + Sanity starts at $1,200 for a landing page (1 to 2 weeks) and $3,000 for a multi-page site (2 to 4 weeks). Moving an existing site with its content and URLs is $2,200 (2 to 4 weeks). SEO and GEO basics are included, and changes after launch are $30 an hour. The full list is on the pricing page.
My recommendation
Start with who edits the site. If marketers design pages themselves and the site is small, stay with a builder and its built-in CMS. If the site is mostly content, grows every month and has to be fast and readable to AI search, go headless with a static front end. For AI, fintech and B2B SaaS marketing sites that is usually Astro + Sanity, the stack this site runs on.
If you need this built
A landing page from Pavlo starts at $1,200 (1 to 2 weeks), a multi-page site at $3,000 (2 to 4 weeks). The price is fixed before work starts.
See all pricesFrequently asked questions
What is a headless CMS in simple terms?
A headless CMS stores your content and hands it to a website or app through an API, without building the pages itself. A separate front end, such as an Astro site, turns that content into the pages visitors see.
What is the difference between a headless CMS and a traditional CMS?
A traditional CMS such as WordPress stores content, holds the theme and renders pages in one system. A headless CMS keeps only the content and delivers it to any front end, so the design and the content can change separately.
Is WordPress a headless CMS?
Not by default. WordPress is a traditional CMS with themes that render the pages. A developer can use WordPress as a headless back end through its API, but most teams that go that far choose a CMS built for structured content, such as Sanity.
Is a headless CMS better for SEO?
Not by itself. Rankings depend on the HTML, speed and content the front end serves. A headless CMS paired with a static front end like Astro sends finished HTML, which search engines and AI crawlers read in full.
Can marketers edit a headless CMS without a developer?
Yes, for content. In Sanity editors change text, images, posts and page sections in forms with a live preview. A brand new type of section still needs a developer, so plan the section types before the build.
How much does a headless CMS cost for a startup?
Sanity's Free plan costs $0 with up to 20 user seats, and its Growth plan is $15 per seat a month. The build is the larger cost: an Astro + Sanity landing page starts at $1,200 and a multi-page site at $3,000.
Free tool Does ChatGPT recommend you? Free report in 48 hours · 5 AI engines
Checklist
5 signs a startup site needs a headless CMS
One sign alone rarely justifies the extra setup. Two or more usually do, and that is when Pavlo Zhydkykh recommends Astro + Sanity.
1. The site is mostly content
A blog, docs, use case and comparison pages that grow every month need a content model, not hand-built pages.
2. Content appears in several places
The same entries feed the website, a help center or an in-app changelog through one API.
3. Marketing publishes often
Editors add posts, case studies and job openings in forms, with no developer in the loop.
4. Speed is part of the pitch
Developer tools, AI products and fintech sites get static HTML from a CDN instead of pages rendered on each visit.
5. A redesign is coming
Content kept apart from the layout survives a redesign; Pavlo replaces templates, not entries.
Fit check
Is a headless CMS
right for you?
A good fit if
- The site is content-heavy and adds pages every month.
- Speed and AI search visibility bring the leads.
- You want content in an account you own, separate from the design.
- Someone on the team or on retainer, such as Pavlo Zhydkykh, can own the front end code.
Not the right fit if
- A five page site that rarely changes: a builder with a built-in CMS launches faster.
- Marketers redesign page layouts every week: Framer keeps that freedom.
- Nobody can own a code repository, not even through a freelancer.
- Launch is next week: modelling content and building templates takes 1 to 4 weeks.
Compared
Headless CMS vs traditional CMS
Both can power a fast site that ranks. The difference is where pages come from and who can change what; Pavlo Zhydkykh builds the right column on Astro + Sanity.
| Criterion | Traditional CMS | Headless CMS |
|---|---|---|
| Definition | Content, theme and rendering in one system | Content only, delivered through an API |
| Editing | Edit the page you see, often visually | Edit structured fields with a live preview |
| Pages | Rendered by the CMS, often on each visit | Built by the front end into static HTML |
| Reuse | Content tied to one website | Same entries feed the site, docs and app |
| Setup effort | Low: a theme or a builder | Higher: a content model plus a front end |
| Best for | Small sites, teams that design pages | Content-heavy sites, speed, AI search |
In their words
Headless CMS, in the words
of the docs and clients
Word for word, with the source linked: research, official documentation and the people Pavlo Zhydkykh has worked for.
“The main downside is that it may require more effort to set up and configure and a certain level of web development knowledge on both the front and back end.”
“This means that the CMS helps you write your content, but doesn’t generate a site that displays it.”
“Content authors get to focus on content. Developers get to focus on code.”
“One of the best contractors I have worked with. Really thoughtful about communication. Went above and beyond in delivering the results that our team needs. Would 100% hire again for our projects.”
“He's amazing in what he contributes, both design-wise and also from the ideas.”
“It was an absolute pleasure working with Pavlo. He's very professional and responds immediately to all questions and/or feedback. The quality of work he delivered was AMAZING.”
About the author
Pavlo Zhydkykh
Pavlo Zhydkykh is a web designer and developer in Eastern Europe who has built websites for AI, fintech and B2B startups since 2016, designing and building each project himself on Framer or Astro + Sanity. Clients include MStudio Asia, Silicon Data, Inturai, Accolade Pro, NimbleStax and Sancts.
- Top Rated on Upwork
- 100% Job Success
- 10 years since 2016
- 50+ sites shipped
- 90+ PageSpeed at launch
About Pavlo LinkedInUpworkContra Privacy policy
Page reviewed by Pavlo Zhydkykh · Updated
In this topic
Platforms compared
10 articles
- 01 Figma MCP with Claude Code: What 15,280 Calls Taught Me 6 min
- 02 Best Claude Code Skills for Web Design: I Counted 259 Calls 8 min
- 03 Website Migration SEO Checklist: Keep Rankings When You Change Platforms 6 min
- 04 What Is a Headless CMS, and When Does a Marketing Site Need One? You are here
- 05 Astro vs Webflow in 2026: Which Fits a Startup Website? Next
- 06 Framer vs Webflow 2026: Which Platform Wins? 8 min
- 07 Framer vs WordPress 2026: Which Should You Choose? 5 min
- 08 Framer vs Figma Sites 2026: What's the Difference? 6 min
- 09 Should Your SaaS Site Be Custom-Coded or No-Code? 6 min
- 10 Webflow to Framer SEO: Redirects That Keep Rankings 6 min