"Headless" just means the editor and the website are two separate things. You log into one to write, the site reads from it to display. That is it. Strip out the jargon and a headless CMS is a spreadsheet with a nice interface that your website plugs into.
The question is not "should we go headless", the question is "will headless help our site bring in more clients and rank better, or will it just add cost and friction". For most small businesses the answer is one of those two, rarely both.
What headless actually buys you
Three real benefits, in order of how often they matter:
- Speed. A site that reads from a headless CMS at build time and serves static HTML is between two and five times faster than a typical WordPress page on shared hosting. Faster pages rank better on Google and convert better on mobile. This is the single biggest client-acquisition argument for headless.
- Structure. Content in a headless CMS is structured into fields (title, date, author, body, image), not a blob of HTML. That structure lets you render the same content in three different layouts, feed it into your mobile app, or syndicate it, without rewriting anything.
- Editor peace of mind. A clean field-by-field interface means your marketing team cannot accidentally break the site's CSS by pasting from Word. They write; the design holds.
If none of these three map to a real problem you have, you do not need headless.
What it costs you
Headless CMS sites are built by developers first, not WordPress-shop generalists. Your starting team is a front-end engineer who knows React or Astro, plus a CMS admin who configures the schema. That is £6,000 to £15,000 for a marketing site, versus £2,500 to £6,000 for an equivalent WordPress build.
Preview environments need explicit setup. Plugins that "just work" in WordPress (forms, comments, analytics) become separate integrations. If your team is used to logging in and clicking "edit page", be honest about whether they will embrace the slightly more technical workflow.
The three we recommend most
Sanity
Best for content-heavy sites. The editor is excellent, the schema is TypeScript, the free tier is generous. Real-time collaboration, like Google Docs but for structured content. Used by Netflix, Figma and a lot of sharp small brands. Per-user pricing above the free tier can surprise growing teams.
Contentful
Best for marketing teams that need multi-language and approval workflows out of the box. The API is rock-solid, the editor is a little more corporate than Sanity. Pricing scales steeply once you go past the free tier, check the numbers before committing.
Keystatic
Best for solo founders, freelancers and small teams who want content as Git-tracked files rather than a hosted service. Edit through a local admin UI or via GitHub OAuth. Zero hosting cost beyond your regular site hosting. Excellent fit for Astro and Next.js marketing sites. This is the CMS we reach for most in 2026 for small business clients. The site you are reading uses it.
When WordPress is still the right answer
We recommend WordPress to clients when:
- Your team publishes content weekly and wants a familiar editor.
- You rely on specific plugins (WooCommerce, LearnDash, a membership plugin) that have no clean headless equivalent.
- Your budget is under £3,500 for the whole build.
- Your traffic is primarily organic search and the SEO plugin ecosystem (Yoast, Rank Math) is part of how your team works.
Done right, a modern WordPress site on good hosting (not shared), with a minimal theme, can hit 90 on Lighthouse. That is better than a sloppy headless build. Stack matters less than care.
How to pick, in four questions
- How often do you publish? Weekly or more, strong case for headless. Monthly or less, WordPress is likely fine.
- Do you have a dev on retainer? Yes, headless opens more options. No, pick WordPress or Keystatic.
- What is your annual traffic growth target? 3x or more, headless pays off because performance compounds. Flat, stick with what works.
- Does the site currently rank well on Google? If yes, be careful about a platform change that risks the rankings. Plan URL mapping and server-side redirects before you migrate.
The SEO angle
Headless sites do not automatically rank better. They can be faster, which helps. They are often cleaner in markup, which helps. But you still need the basics: clean URLs, a sitemap, structured data for your service pages, real internal linking, fast-to-first-contentful-paint mobile performance. Headless gives you the tools. It does not do the work.
Migrate carelessly and you lose the SEO equity you built up for years. Migrate with a redirects map, schema parity and a content audit, and the new site usually ranks better within 90 days because the speed wins carry through.
The short version
Go headless when you publish often, care about speed and conversions, and have the budget for a proper build. Stay on WordPress when your team is happy, your plugins are load-bearing, and the current site is not costing you clients. Either way, spend as much effort on the content and the conversion design as you do on the platform. That is where the leads actually come from.