Headless WordPress vs Traditional WordPress: Which Should You Choose?

In a traditional (or "monolithic") setup, WordPress does everything: it stores the content, runs the PHP theme that turns that content into HTML, and serves the pages to visitors. Plugins can add features to both the admin and the public site.

This is how most WordPress sites work, and it's the reason WordPress is so approachable. Editors see a preview that matches the live site, and thousands of plugins work out of the box.

In a headless setup, WordPress is only the content backend. Editors still use the familiar WordPress admin, but the public website is a separate application — usually built with React or Next.js — that fetches content through the WordPress REST API (or GraphQL via WPGraphQL).

The "head" (the frontend) is decoupled from the "body" (the CMS). The same content can also feed a mobile app, a dashboard or several websites at once.

• Build effort: traditional is faster and cheaper to build; headless needs a separate frontend app, API design and a deployment pipeline.
• Performance: both can be fast. A well-built theme with caching scores well on Core Web Vitals; a statically generated Next.js frontend can be extremely fast but only if it's built carefully.
• Plugins: traditional sites get plugin features on the frontend automatically. In headless, anything that outputs HTML (forms, sliders, many SEO features) has to be rebuilt in the frontend.
• Editing experience: traditional has true live preview. Headless needs extra work for previews and the editor may not see exactly what visitors see.
• Security: headless can reduce the public attack surface because the WordPress admin can sit on a separate, locked-down domain.
• Hosting: traditional needs one PHP host. Headless needs a PHP host for WordPress plus a Node/edge host for the frontend.
• Multi-channel content: headless wins clearly when one content source must feed several apps or sites.

• Marketing sites, company websites, blogs and portfolios where editors need to publish quickly.
• WooCommerce stores that rely on many plugins for payments, shipping and tax.
• Projects with a limited budget or no in-house JavaScript developers to maintain a separate frontend.
• Teams that want the full plugin ecosystem without rebuilding features.

• You already have (or are building) a React or Next.js application and want WordPress to manage its content.
• The same content must power a website, a mobile app and internal dashboards.
• You need highly interactive, app-like interfaces that a PHP theme would struggle with.
• Security or compliance requirements call for keeping the CMS off the public website.

You don't have to choose all or nothing. A common pattern is a traditional WordPress theme for the main website, with custom REST API endpoints feeding a React widget, a customer dashboard or a mobile app. You keep the plugin ecosystem and easy editing, and use React only where it adds real value.

Search engines need to receive real HTML. If you go headless, use server-side rendering or static generation (Next.js does both) rather than a client-only single-page app. You'll also need to output titles, meta descriptions, canonical tags, structured data and an XML sitemap from the frontend yourself, because WordPress SEO plugins no longer render the page.

Start from the business need, not the technology. If your main goal is a fast, easy-to-edit website, a well-built traditional WordPress theme is usually the right call. If you need one content source for several applications, or an app-like frontend, headless WordPress with Next.js is worth the extra investment.

If you're unsure, I'm happy to look at your requirements and recommend the simplest architecture that will do the job.