Most "headless vs traditional" posts are written by headless vendors, so the scoreboard comes out 10–0. Here's the version with the losses included.
Where traditional actually wins
Turnkey SEO. Yoast and Rank Math bolt onto the rendering layer. Meta tags, sitemaps, schema, redirects — a settings panel, no code. A headless CMS ships none of that. You model metaTitle and metaDescription on the content type yourself, then render them into <head> from your app.
The editing loop. Change a heading, see it render, publish. No developer in the middle. Headless breaks that by design — content lives in a database, not on a rendered page, so "preview" means asking a frontend to fetch a draft and render it separately.
Setup cost. Someone builds a frontend. Someone picks SSR vs SSG vs ISR. Someone maintains a deploy pipeline. For a five-page site with one editor, that's more machinery than the job needs.
WordPress runs 41.9% of all websites (W3Techs). That number isn't an accident.
Where headless wins
Control, and channels. URL structure, schema markup, and redirect logic live in your code instead of a plugin's defaults. One entry feeds a website, a mobile app, and an email — each pulling only the fields it needs. Adding a second channel to WordPress usually means duplicating content or bolting on a REST layer the platform wasn't built to expose.
And "run WordPress headless" mostly inherits the worst of both: full hosting cost, minus the plugin ecosystem that justified WordPress in the first place.
The framing nobody uses
It stopped being a two-way choice. The MACH Alliance folded headless into a four-part standard — Microservices, API-first, Cloud-native, Headless.
So the real question isn't headless or not. It's how much of MACH do you actually need. One React site talking to one content API needs the API-first piece and the headless piece. Not microservices. Not a cloud-native commerce engine.
Full post covers the SEO tradeoff in detail, the React fit, and the cost math:
Headless CMS vs Traditional CMS: React, SEO, and When Each Wins →
We build Draftbase for exactly that slice — MDX over REST and GraphQL, links and media resolved inline, drafts readable through the same API. Hobby free, Startup $49/mo.
