Frequently Asked Questions

Two Fundamentally Different Approaches

WordPress and headless CMS represent two fundamentally different architectural philosophies for building web-based content experiences. Understanding this difference — and communicating it clearly to clients — is one of the most important capabilities an agency can develop. Getting this recommendation right determines whether a client ends up with a platform that serves their needs for years or one that frustrates their team and limits their growth.

WordPress, launched in 2003, is the world’s most widely deployed CMS, powering approximately 43% of all websites. It is a coupled CMS, meaning it manages both content and presentation within a single system. WordPress stores content in a MySQL database and uses PHP templates (themes) to render that content as HTML pages. The WordPress ecosystem includes tens of thousands of plugins that extend its core functionality, enabling everything from contact forms and e-commerce to membership systems and complex editorial workflows — all managed through a familiar admin interface.

A headless CMS, by contrast, separates content storage and management from presentation. The CMS provides a content repository and a management interface, but it does not render HTML. Content is delivered to a separate front-end application via an API — typically REST or GraphQL. The front end is built with a modern JavaScript framework such as Next.js, Nuxt.js, Astro, or SvelteKit, and it renders the content using its own templates and components. The CMS and the front end are independently deployable, scalable, and updatable.

Architecture Comparison

The practical architectural differences between WordPress and headless CMS have significant downstream implications for development complexity, performance, flexibility, and total cost of ownership.

In a WordPress build, the entire system — database, CMS logic, template rendering, and content delivery — runs on a single server stack. An incoming page request triggers PHP execution that queries the database, retrieves content, applies the theme template, and returns HTML to the browser. With good caching, this process is fast. Without caching, it can be slow, particularly under high traffic.

In a headless architecture, the content layer and the delivery layer are separate systems that may run on entirely different infrastructure. The CMS (Contentful, Sanity, Prismic, or headless WordPress) is typically hosted on a managed SaaS platform. The front-end application is deployed to a CDN-edge infrastructure via Vercel, Netlify, or Cloudflare Pages, where it is either pre-rendered at build time (Static Site Generation) or rendered on-demand at the edge (Edge SSR). This structural separation enables very high performance and scalability.

When WordPress Is the Right Choice

For the majority of agency client projects — particularly SME websites, marketing sites, portfolio sites, news and blog sites, and WooCommerce stores — WordPress is the right choice. The reasons are practical, not ideological.

• Budget Fit: WordPress builds are generally less expensive than equivalent headless builds. The development ecosystem is large, which keeps rates competitive. The theme and plugin ecosystem reduces custom development requirements for common functionality.
• Editorial Experience: WordPress’s editor (Gutenberg) is mature, widely understood, and genuinely usable for non-technical content editors. Most clients who have managed a website before have encountered WordPress. The learning curve is low.
• Plugin Ecosystem: For clients who need e-commerce, membership, bookings, events, multilingual support, SEO tools, or marketing automation integrations, WordPress’s plugin ecosystem provides reliable, well-supported solutions that would take significantly longer and cost significantly more to custom-build on a headless stack.
• Developer Availability: WordPress developers are abundant in the UK, which means competitive day rates and a large pool of white label partners and freelancers. For agencies outsourcing delivery, WordPress is the easiest platform to source quality development support for.
• Support and Longevity: WordPress has a huge global user base, active open-source development, and a commercial ecosystem of hosting, plugin, and support providers. It is not going away. Recommending WordPress to a client comes with a reasonable expectation of long-term platform stability.

The appropriate WordPress project profile is: SME marketing sites, brochure websites, content-heavy blogs and news sites, WooCommerce stores with moderate complexity, portfolio and agency sites, and charity or non-profit websites. These represent the vast majority of agency CMS work, and for all of them, WordPress is a sound technical and commercial choice.

When Headless CMS Is the Right Choice

Headless CMS becomes the appropriate recommendation when the client’s requirements push beyond what WordPress’s coupled architecture handles well.

• Multi-Channel Content Delivery: When content needs to be delivered simultaneously to a website, a mobile app, digital displays, and other touchpoints from a single repository, a headless CMS is architecturally essential. WordPress can serve as a headless back end via its REST API or WPGraphQL, but purpose-built headless platforms like Contentful or Sanity are better suited to structured multi-channel content delivery.
• Extremely High Performance Requirements: When page speed and Core Web Vitals scores are mission-critical — in competitive e-commerce, financial services, or media contexts — a headless front end delivered via CDN edge infrastructure outperforms any WordPress configuration.
• Complex Interactive Experiences: Applications that require sophisticated client-side interactivity, complex state management, or custom user flows that don’t map to standard page-level rendering benefit from the freedom that a JavaScript front-end framework provides.
• Enterprise Scale and Traffic: Sites that need to handle hundreds of thousands of daily visitors, with global CDN delivery, zero-downtime deployments, and independent scaling of content and delivery layers, are better served by headless architecture.
• Structured Content at Volume: Large content operations — major publishers, e-commerce catalogues with thousands of products, global documentation sites — benefit from headless CMSs’ superior content modelling and editorial workflow capabilities.

Cost and Delivery Implications

The cost and delivery implications of WordPress versus headless CMS are significant, and agencies need to factor them clearly into client proposals.

A standard WordPress marketing site — 10 to 20 pages, custom design, Gutenberg blocks, contact forms, basic SEO configuration, and a simple WooCommerce integration — typically has a development cost in the range of £5,000 to £15,000 depending on complexity and the agency’s rate card. Build time is typically 6 to 12 weeks. This is the core of most agency project pipelines.

An equivalent headless CMS build — the same site delivered as a Next.js front end against Contentful or Sanity — would typically cost 40 to 80% more, with a longer build timeline. The premium reflects the additional front-end development work required (building components from scratch rather than using WordPress themes and plugins), the more complex infrastructure setup, and the greater need for specialist JavaScript development skills.

The premium is justified when the client genuinely needs the capabilities headless delivers. It is not justified — and will result in an overspent, frustrated client — when the brief could have been met perfectly well with WordPress.

Ongoing maintenance and support costs also differ. WordPress maintenance retainers cover core updates, plugin updates, security monitoring, and performance management. These are well-understood, standardised, and easy to price. Headless maintenance involves front-end framework updates, API version management, build pipeline maintenance, and CMS platform changes — a broader and less predictable scope that should be reflected in higher retainer pricing.

The Case for Platform-Agnostic Agency Positioning

The commercial conclusion is that agencies should not position themselves as ‘WordPress agencies’ or ‘headless CMS agencies’ but as CMS strategy partners who recommend the right platform for each client’s needs. This positioning is only credible if the agency can genuinely deliver on multiple platforms — which is why the white label partnership model, with its multi-platform development capability, is such a powerful enabler of platform-agnostic positioning.

An agency that can look a client in the eye and say ‘you need WordPress because X, Y, and Z, and here’s exactly how we’ll build it’ — or, conversely, ‘your requirements call for a headless approach and here’s why’ — is a more trusted and more commercially successful agency than one that defaults to a single platform regardless of the project brief.