1. What headless WordPress actually means
The word “headless” refers to removing the “head” — the visual front-end that users see — from the content management system (WordPress) that runs behind the scenes.
Traditional WordPress
WordPress manages content and renders the HTML pages users see. Your theme templates live inside WordPress. When a visitor loads a page, WordPress queries its database, runs PHP, and sends a complete HTML page back. One system does everything.
Headless WordPress
WordPress manages content only. A separate application — typically Next.js — handles everything users see. Next.js calls WordPress's API to fetch content, then renders it using React components. WordPress has no theme visible to users. Two separate systems, each doing one job.
For editors, the experience is identical — they log into WordPress and manage content exactly as they would on a traditional site. The difference is invisible to them. For developers, the front-end is a completely separate Next.js codebase with full design freedom and React's component ecosystem.
2. Traditional vs headless — a concrete comparison
| Factor | Traditional WordPress | Headless WordPress |
|---|---|---|
| Build cost (UK) | £3,000 – £15,000 | £15,000 – £45,000 |
| Build timeline | 3–8 weeks | 10–20 weeks |
| Performance potential | Excellent with optimisation | Best-in-class (edge delivery) |
| Design freedom | Limited by theme constraints | Unlimited — pure React front-end |
| Multi-channel content | Website only | Website, mobile app, signage from one API |
| Hosting complexity | One server | Two environments (WordPress + Next.js) |
| Ongoing maintenance | One codebase | Two codebases — higher ongoing cost |
| Best for | Most UK business websites | Large content platforms, multi-channel, complex SPAs |
3. How headless WordPress works technically
You do not need to understand every technical detail, but this overview helps you ask the right questions when briefing a developer.
WordPress exposes content via API
WordPress has a built-in REST API that any application can query. You install either the WPGraphQL plugin (for GraphQL queries) or use the default WP REST API. Content — pages, posts, custom post types, menus, taxonomies — becomes available as structured JSON data at a predictable endpoint.
Next.js fetches and renders content
A Next.js application makes API calls to WordPress during the build process (Static Site Generation) or at request time (Server-Side Rendering). The pages are built using React components. The HTML output has no WordPress fingerprint — it is pure custom front-end code.
Hosting on Vercel + managed WordPress
The Next.js front-end deploys to Vercel's global edge network — serving pages from data centres close to each visitor for millisecond response times. WordPress sits on a managed WordPress host (WP Engine, Kinsta) as an API backend, not publicly accessible. This security separation keeps the database off the public internet.
On-demand revalidation for content changes
When an editor publishes a new blog post in WordPress, a webhook triggers Next.js to regenerate only the affected pages — the new post page and the blog listing. Everything else stays cached. This combination of static serving + on-demand updates is called Incremental Static Regeneration (ISR) and is one of the key performance advantages of the headless pattern.
4. When headless is genuinely worth the cost
You need to publish content to multiple channels
If your WordPress content also needs to appear in a mobile app, digital signage, or a customer portal — without duplicating editorial work — headless is the right architecture. One WordPress CMS, multiple front-end consumers of the API. Traditional WordPress cannot serve this pattern cleanly.
Your design requires full custom front-end freedom
Certain experiences are very difficult to achieve within WordPress theme constraints — complex animations, highly interactive interfaces, single-page application behaviour. If your design brief requires things that would require hacking around WordPress's template system, a Next.js front-end gives your developer a clean canvas.
You are building a large content platform with global audiences
A media site serving 500,000+ monthly visitors benefits materially from Vercel's edge delivery — pages served from data centres in the same region as each visitor. Traditional WordPress on a single server, even with CDN, cannot match the latency profile of true edge-deployed Next.js.
Your team includes React developers who will own the front-end
Headless only makes sense when there is ongoing developer capacity to maintain the Next.js codebase. If you are commissioning a one-off build and have no developer on retainer, the second codebase becomes a liability rather than an asset.
5. When headless adds complexity without value
Most UK business websites do not need headless architecture. Here are the situations where a well-built traditional WordPress site is unambiguously the right choice.
Budget under £12,000
You cannot build headless properly at this budget. A £10,000 headless build will be rushed and incur technical debt immediately. Spend that budget on a high-quality traditional WordPress site instead.
5–30 page brochure or professional services site
A law firm, accountant, or dental practice website does not need edge delivery or multi-channel content distribution. A custom traditional WordPress site achieves excellent SEO and performance at a quarter of the cost.
No developer on retainer after launch
Two codebases require two maintenance paths. If you have no developer maintaining the Next.js front-end, dependency updates and security issues accumulate. Traditional WordPress can be maintained more easily by a wider pool of developers.
WooCommerce is your primary requirement
Headless WooCommerce is significantly more complex and expensive than traditional WooCommerce. Unless you have multi-channel commerce requirements, standard WooCommerce on a well-optimised traditional WordPress install is the right call.
6. UK pricing for headless WordPress in 2026
| Component | Cost range (UK) |
|---|---|
| WordPress setup, content modelling, WPGraphQL | £4,000 – £10,000 |
| Next.js front-end development | £8,000 – £25,000 |
| Hosting setup (Vercel Pro + managed WP) | £500 – £1,500/yr ongoing |
| Ongoing maintenance (2 codebases) | £400 – £1,000/mo |
| Total initial build | £15,000 – £45,000 |
For comparison — traditional WordPress
A custom traditional WordPress site from WebAnts starts from £3,000. A complex site with WooCommerce or custom functionality starts from £8,000. The performance and SEO outcomes are excellent — the investment differential only becomes worthwhile when your requirements genuinely need what headless provides. See our WordPress development service for traditional WordPress pricing.
7. The technical stack — WPGraphQL, Next.js, Vercel
WPGraphQL
A free WordPress plugin that adds a GraphQL API to your WordPress install. Rather than making multiple REST API calls to fetch pages, menus, posts, and custom fields separately, WPGraphQL lets a developer write a single query that returns exactly the data needed. This reduces API calls, improves performance, and makes the front-end codebase cleaner. It is maintained by WP Engine and widely used in production.
Next.js
Next.js is a React framework built by Vercel. It is the most widely used framework for headless WordPress front-ends because it supports both Static Site Generation (pre-built pages served from a CDN) and Server-Side Rendering (dynamic pages built on request). Next.js's App Router, Incremental Static Regeneration, and built-in image optimisation make it the natural choice for high-performance WordPress front-ends.
Vercel
Vercel is the deployment platform built by the Next.js team. Deploying a Next.js headless WordPress site to Vercel takes minutes and provides automatic preview deployments, edge caching, Core Web Vitals monitoring, and global CDN delivery. Production Vercel deployments start at approximately £20/mo for a typical site and scale based on usage.