What is a traditional website?

In a traditional WordPress architecture, the CMS handles data storage, business logic and HTML rendering all at once. Concretely:

  • Content (posts, pages, media) is stored in a MySQL database
  • The PHP theme generates the HTML and CSS and controls the layout
  • The visitor receives the rendering produced directly by the WordPress server
  • Modifying the design means working on the theme, which is coupled to the content display logic

This tight coupling between content and presentation means that any visual change requires working in the same environment as content management.

The "headless" concept: backend / frontend separation

Headless architecture is built on a decoupling principle: the CMS (backend) only handles content storage and structuring, while one or more independent frontends take care of presentation.

Content stays in WordPress and its database. Multiple frontends can consume that content via an API. Each frontend has its own technology stack and its own design. Modifying one frontend has no impact on the others or on the backend.

Why is it called "headless"?

The term "head" refers to the presentation layer of a CMS, that is, the theme that produces the HTML pages a user sees. "Headless" means this presentation layer has been removed from the CMS. The WordPress backend no longer outputs HTML for visitors: it exposes its data through an API, and a separate frontend application takes care of rendering.

Decoupling principle

The backend (WordPress) delivers content as structured data (JSON). One or more frontends consume that data through the API and render it with their own interface. This decoupling allows each layer to evolve independently.

The headless architecture in detail

WordPress's evolution toward headless

WordPress has been around since 2003 and powers about 40% of websites worldwide. Adoption of the headless architecture is driven by growing needs for performance, design flexibility and multi-channel distribution.

40%

of the global web

WordPress market share (W3Techs)

×3

faster

Average performance gain in headless architecture with SSG

100%

technology choice

No constraint on the frontend framework used

What does it actually mean for you?

If you manage content

The WordPress admin interface remains the same. Writing, publishing and organizing content do not change. Only the display layer is replaced by a modern frontend.

If you visit the site

Load times drop below one second thanks to pre-rendering and CDN distribution. The interface is smoother and the design is no longer constrained by a WordPress theme.

If you build the site

You work with a modern frontend stack (React, Next.js, TypeScript). The code is decoupled, testable and versioned independently from the WordPress backend.

Steps to go headless

Keep WordPress as the CMS

Content and the admin interface stay in place. The database is preserved — no content migration is required.

Enable the API

WordPress natively exposes a REST API. The WPGraphQL plugin can be added to provide a GraphQL endpoint, which allows more targeted, performant queries.

Build the frontend

A frontend application is built with a framework like Next.js. It consumes data from the WordPress API and handles page rendering.

Connect the two layers

The frontend sends requests to the WordPress API to fetch content, then renders pages with a custom design, using SSG (Static Site Generation) or SSR (Server-Side Rendering).