"Headless CMS" is agency jargon for a simple idea. The name is confusing. The idea, once explained, is obvious.
Here's what it actually is, why it's become the default recommendation for modern marketing sites, and how to decide whether it's the right call for your business, without the consultant-speak.
The traditional CMS model (WordPress)
WordPress is a coupled CMS. Your content and the code that displays it are in the same system. The wp-admin dashboard edits content; the WordPress theme templates display it; they're welded together.
Benefits: one system to manage. Cheap to set up. Your team edits in the same admin that runs the site.
Costs: the frontend is locked to WordPress's PHP-based rendering. Slower than modern static-first stacks. Plugin ecosystem forces you into WordPress's conventions. Hard to reuse content elsewhere (mobile app, newsletter, marketplace listing) without exporting.
For 15 years this was fine. In 2026, the performance cost of coupled CMSes shows up in Core Web Vitals scores, and Google ranks faster sites higher for identical content.
The headless model
A headless CMS decouples content storage from content display.
- Content lives in a structured API, "hero headline: [text]," "featured case: [relation to case 37]," "call-to-action button: [object with label + href]"
- The frontend is whatever you want. Astro, Next.js, a mobile app, a marketplace integration, it pulls the structured content via API and renders it however it needs to
Analogy: WordPress is like a vending machine, the drink is stuck inside the machine. Headless is like a fridge at home, the drink is stored once, you can serve it in a glass, a bottle, a flask, whoever asks for it.
The three headless CMSes worth knowing (2026)
Most headless CMSes are built for enterprise. These three work well for UK small businesses:
Keystatic (our default)
- Git-backed, content is stored as Markdown and YAML files in the site's repository
- Free, no SaaS subscription, no content limits, no seat fees
- Editor UX, lives inside your own site at
/keystatic. Clean, fast, modern - Best for: small teams editing weekly or less. Technical small businesses that like content under version control
Sanity
- Cloud-hosted, content sits in Sanity's database, accessed via API
- Generous free tier, 10,000 API requests/day, 3 users, 5GB assets, more than most small businesses use
- Content modelling, the strongest of the three, build highly structured schemas, rich editorial experiences
- Best for: content-heavy small businesses with 3+ editors. Teams that need real-time collaboration
Contentful
- Enterprise-grade, polished admin, strong governance features, excellent API
- Pricey above the free tier, jumps to ~$300/month at the first paid level
- Best for: multi-brand / multi-region businesses. Teams that need proper role-based permissions and audit logs
What headless gives you as a small business
- Faster sites. Static HTML renders from a CDN in under a second. No PHP runtime, no database query on every pageview.
- Better SEO. Fast sites rank higher. Core Web Vitals are consistently green.
- No plugin bloat. Your content schema is written once, in TypeScript or similar. No 40-plugin swarm needed to duplicate WordPress's built-ins.
- Multi-channel ready. Content can feed a mobile app, a newsletter template, a partner directory, a JSON-LD schema payload. Publish once, render many.
- Vendor-independence. Your content is either in git (Keystatic) or in a cloud service you can export from. No lock-in.
What the team experience is actually like
Non-technical editors who open Keystatic's admin typically say "oh, this is WordPress." The learning curve is minimal. Fields are clearly labelled, validation is immediate, Markdown preview works inline.
The difference shows up when content changes go through review. On Keystatic, saving creates a git commit, a senior editor can review the PR, suggest changes, approve. On WordPress, edits go live immediately (unless you install a revision plugin that most teams bypass).
For a 2–3 person team running a marketing site, this workflow is tighter than anything WordPress offers out of the box.
When headless makes sense for your business
- You care about speed and SEO. Marketing site, lead-gen funnel, content that ranks.
- You edit monthly, not daily. Headless rewards thoughtful content; WordPress rewards high-frequency publishing with the admin familiarity.
- You want structured content. A case study has typed fields (client, year, metrics, gallery) not a single free-text blob.
- You value vendor-independence. Git-backed or exportable-anytime.
- Your developer team is comfortable with modern JS frameworks. Astro, Next.js, SvelteKit, Remix.
When headless doesn't make sense
- High-volume publishing. 5+ posts per week by 5+ authors. WordPress's editorial workflow wins.
- WooCommerce dependency. If commerce is the business, staying on WooCommerce is simpler than rebuilding on headless commerce platforms.
- Plugin dependency. A specific plugin your business runs on that has no equivalent elsewhere.
- Team that won't learn anything new. If your team actively resists new tools, forcing a migration costs more than staying.
Our default stack
For small-business marketing sites in 2026, our default is Astro + Keystatic. This site, the one you're reading now, runs on exactly that. 100+ Lighthouse on mobile. No plugin list. Content in Markdoc files. Deployed from a git push.
Why this specific combination:
- Astro's islands architecture ships only the JavaScript that's actually needed
- Keystatic's git-backed content means every edit is a commit (audit trail + easy rollback)
- Cloudflare Pages / Netlify hosting is free at this scale
- Total monthly cost to run the stack: £0 (excluding domain)
For e-commerce, we pair either WooCommerce on clean WordPress or Shopify (depending on catalog size and checkout complexity), not headless. E-commerce is where WordPress still wins on total-effort-to-launch.
Migration path from WordPress
Moving from WordPress to a headless stack is usually a 4–6 week project, not an overnight flip.
What's involved:
- Content export, posts, pages, media, custom fields
- Schema redesign. WordPress's loosely-typed content becomes strictly-typed in headless
- URL preservation, 301 redirects for every old URL to the new equivalent
- Theme rebuild, the old WordPress theme becomes an Astro layout
- QA, SEO audit, performance audit, content-completeness check
What's gained: speed, SEO ceiling, maintainability, lower ongoing cost.
What's lost: WordPress-specific plugins with no headless equivalent (usually a handful, most have alternatives). Specific editorial workflows that depended on wp-admin quirks.
For most small businesses, the gains outweigh the losses, but it's genuinely a project, not a weekend flip.
Is headless right for your business?
Three questions:
- Does site speed affect your business? If SEO / paid-ads ROI / conversions depend on Core Web Vitals → yes, headless is worth it.
- How often does content change? Weekly editing, structured content types → yes. Yearly updates to a brochure site → no, stay static or simple WordPress.
- Are you paying WordPress maintenance tax now? If you're spending £200+/month on WordPress hosting + plugins + maintenance for a marketing site, headless will pay back within a year.
Want to see if headless fits your business?
Book a free 30-minute call, we'll look at your current stack, your content cadence, and recommend honestly (including "stay on WordPress" if that's the right call).
Or message on WhatsApp.