Headless WordPress: When It Earns Its Cost, And When It Does Not
Headless WordPress is a real architecture with real advantages, and it is currently being recommended to a lot of people who will not get their money back. Here is how we decide, on actual projects, whether it is worth it.
What You Are Actually Buying
You are buying a front end that is not WordPress. That is the whole trade. Everything good and everything expensive follows from it.
The good: your front end can be deployed, cached and scaled on its own terms. Your interface work stops being constrained by what the theme layer wants. One content store can feed a website, a mobile app and a partner integration without any of them pretending to be a page. If you are already building the app, you may be buying something you needed anyway.
What It Charges You
Everything WordPress gave you for free is now a ticket. Preview stops working until somebody builds it. So do menus, forms, redirects, sitemaps, and the editor's ability to see what a page will look like. Plugins that render on the front end simply do not, which quietly removes most of the ecosystem.
The cost that gets missed is the editor's. In a normal WordPress site the person writing the content can see the result and fix a line themselves. Headless, they see a form, and a widow in a heading becomes a deployment. That is not a technical problem and it will not show up in a performance budget, but it is the thing that makes people quietly stop updating a site.
How We Decide
Two questions, in this order.
Is there a second consumer of the content? A mobile app, a kiosk, a partner feed, another site. If yes, the API is not overhead, it is the point, and a headless front end is close to free on top of a thing you were building regardless.
Who edits this, and how often? A site a marketing team touches weekly needs preview and needs the editor to be able to see what they are doing. A site that changes four times a year does not, and the argument gets much easier.
If the answer to the first is no and the answer to the second is often, headless is being chosen for how it sounds rather than for what it does.
The Middle Option Nobody Sells
Most sites that want headless actually want fast. Those are different problems with different price tags. A well-built theme with conditional asset loading, a properly configured object cache and clean queries will get you a fast site for a fraction of the cost, and the editor keeps their preview button.
We build both. We are more careful about recommending the first one, because we are the people who have to build the preview system afterwards.