Headless WordPress
WordPress as a back-end via WPGraphQL or REST. Editorial team keeps wp-admin; public site is modern.
VISIT HEADLESS WORDPRESSKey takeaway: Headless WordPress keeps the WordPress editor and ecosystem while serving content through an API (WPGraphQL or REST) to a modern front end like Next.js or Astro. Pick it when the team is committed to WordPress authoring but wants the performance and developer experience of a decoupled front end.
Quick facts
- CategoryLegacy / Headless mode
- LanguagePHP
- PricingOpen source
- LicenseGPL-2.0
- Created2003
- GitHub stars19.5k
- Statusactive
What it is
WordPress used headlessly is the most-deployed pattern in this entire directory by raw site count. The editorial team keeps wp-admin (which they already know); a Next.js or Astro front-end consumes the data via WPGraphQL or the REST API. Excellent for migrations off legacy WordPress where the team will not retrain.
Best for
- WordPress sites migrating to a modern front-end without changing the editorial workflow
- Editorial teams with WordPress muscle memory and no appetite for a new admin UI
- Projects with significant WordPress content history (12,000-site agency reality)
When not to pick it
Skip headless WordPress for greenfield projects where the team has no prior WP investment, Payload, Sanity, or Astro Content Collections are cleaner. Also skip if your team will fight the WP-style content model.
My take
Headless WordPress is the right answer when the editorial team is the bottleneck and they already live in wp-admin. New projects with no WP legacy almost never pick it. The 12,000-site experience says: pick by team, not by framework.
Keep the editor, change the front end
Headless WordPress decouples the back end (wp-admin, plugins, the familiar editor, ACF for structured fields) from the front end, which you build separately and feed with WPGraphQL or the REST API, often via Faust.js for Next.js. Editors keep the workflow they already know and the vast plugin ecosystem stays available, while visitors get a fast, custom front end.
The cost of decoupling
You take on real complexity: two systems to host and deploy, preview and authentication that no longer work out of the box, and plugins that assume they own the front end and may not translate. It pays off for content-heavy or performance-sensitive sites where the WordPress editor is non-negotiable; for a simple brochure site, classic WordPress is usually less work.
Frequently asked questions
What is headless WordPress?
It is WordPress used only as a back end: you author in wp-admin as usual, but the public site is a separate front end (often Next.js or Astro) that pulls content through WPGraphQL or the REST API.
Is headless WordPress good for SEO?
It can be excellent, because you control the rendering and performance of the front end. But SEO is not automatic: redirects, metadata transport, and server-side rendering have to be implemented deliberately during the decoupling.
What does headless WordPress cost to build?
A decoupled rebuild of a typical 30-100 page site usually runs in the tens of thousands of USD, because you are building and hosting a second system and re-implementing preview, auth, and SEO transport. The editor stays the same; the front end is new work.
Links
Compare Headless WordPress side-by-side
Similar tools you should also consider
If Headless WordPress is your pick, the next conversation is short
The 30-min call is where your CMS choice becomes a real architecture, an editorial workflow your team can adopt, and a price range you can take to your stakeholders. Describe your content estate, your team\'s muscle memory, your timeline. I tell you whether Headless WordPress is genuinely your fit.