WordPress Headless: When It Is Worth the Complexity and When It Is Not

Headless WordPress has the marketing everyone wants: modern frontend, familiar backend. The reality is that you now maintain two systems. After a year of running both, I can tell when the split earns the cost.

When Headless Is Worth It

Your frontend needs cannot be met by WordPress themes. Not you do not like themes. Cannot. App-like interactivity, real-time features, heavy JavaScript. If a skilled WP theme dev could build it in the classical stack, headless is overkill.

Your content team is happy in WordPress admin. This is not trivial. If the content team prefers Sanity or Contentful, go headless CMS instead of headless WordPress.

Your performance budget rules out classical WP output. Hand-tuned Next.js can beat WP. Headless gives you that lever.

When Headless Is Not Worth It

Content-heavy marketing site with light interactivity. Classical WordPress ships this better and cheaper. Going headless here is cosplay.

Small team without a frontend specialist. Headless means the frontend is your responsibility forever. Not a plugin problem any more.

Budget sensitive. Headless means two hosting bills, two deployment pipelines, two cache layers. The TCO is double.

The Gotchas I Hit

Preview broke. The WP preview feature assumes a classical frontend. Headless preview requires custom work. The client missed preview on week one.

Menus and widgets. Plugins assume classical frontend. My headless frontend re-implemented half of them.

SEO plugins did not apply. Yoasts output lives in WP. The headless frontend needs its own SEO stack or a careful mapping.

Caching got complicated. WP cache, CDN cache, frontend cache, ISR cache. Four layers to invalidate on a publish.

The Pattern That Worked

Use WP REST API or WPGraphQL for content. Use Next.js with ISR for the frontend. Invalidate Next.js cache on WP post save via a webhook. Rebuild SEO metadata on the frontend per route.

add_action('save_post', function($id) {
  wp_remote_post(FRONTEND_REVALIDATE_URL, [...]);
});

Reading

WPGraphQL docs are the standard reference. Read them before committing.

Headless is a tool. Not a trophy.