01 — What "headless" actually means (and what it does NOT)
"Headless" is a SEO-optimised word that confuses decisions. Here is the operational definition, no buzzwords.
Headless = the CMS only manages content, doesn't render it. The frontend is a separate application that fetches content via API (REST or GraphQL) and renders it wherever you want: web, mobile app, smart TV, newsletter, OG image generator.
WordPress monolithic is the opposite: WP manages content AND rendering. Every pageview runs PHP+MySQL+plugins that decide how the page looks. It's the all-in-one box model that's been around since 2003.
In between there's WordPress headless: you use WP only as a content backend (Gutenberg admin, custom post types, media library), and build the frontend in Next.js/Astro that calls the WP REST API. It's a compromise that keeps the WP editor experience without the performance tax of PHP rendering.
Common mistake: thinking "headless" automatically means "fast". False. A poorly-built headless (over-fetch, cache miss, edge cold) is slower than a decent WordPress. The difference is control and scale, not speed by default.
02 — 3 archetypes compared (what does what)
Three real stack families, each with its trade-offs. Knowing where your case fits is half the decision.
- 01
WordPress monolithic
Cos'è. WP installed on PHP/MySQL hosting, theme + plugins, Gutenberg admin, frontend server-side rendered (PHP) on every pageview. WooCommerce for e-commerce.
Trade-off. Fast setup, huge ecosystem, familiar editor. Performance depends on theme + plugin quality (often poor). Security needs constant updates. Scales badly past 100k PV/month without aggressive CDN.
- 02
WordPress headless
Cos'è. WP backend (admin + REST/GraphQL API) + Next.js/Astro/Nuxt frontend that fetches content and renders static/incremental. WP doesn't render pages — only content.
Trade-off. Top frontend performance (static gen), familiar WP editor, but doubled maintenance (WP backend + frontend codebase). WP plugins that depend on frontend rendering (e.g. SEO plugins) must be reimplemented in Next/Astro.
- 03
Pure headless (specialised CMS + frontend)
Cos'è. API-first CMS (Sanity, Contentful, Strapi, Storyblok, Payload) + Next/Astro/Remix frontend. No WordPress instance. Frontend hosting Vercel/Netlify, managed CMS hosting.
Trade-off. Enterprise performance + scale. Frontend-only maintenance, no weekly WP patches. But editor learning curve (admin different from WP), CMS subscription cost 25-300€/month, vendor lock-in.
03 — 6 decision dimensions (what to actually weigh)
- 01
Performance (real CWV)
WP monolithic: median LCP 3-5s on mobile (PHP rendering + plugin assets). WP headless: LCP 0.8-1.5s (static gen + edge). Pure headless: LCP 0.5-1.2s (static gen + CDN edge + image optimisation). Non-trivial difference for Google SEO and conversion: every 100ms more LCP = -1% e-commerce conversions (median data).
- 02
Total cost (3-year TCO)
WP monolithic: hosting 10-30€/month + paid plugins 100-300€/year + dev maintenance 500-2000€/year ≈ 1500-4000€ over 3 years for a brochure site. WP headless: 50-150€/month + initial dev 5-15k€ + maintenance ≈ 10-25k€. Pure headless: 50-300€/month CMS + initial dev 8-25k€ + maintenance ≈ 15-40k€. Break-even when traffic justifies the perf gain.
- 03
Operational maintenance
WP monolithic: weekly core+plugin+theme updates, security patches, db dumps, upgrade downtime. WP headless: same WP backend updates + frontend deploys (CI/CD). Pure headless: only frontend deploys + CMS subscription, no plugin updates, no db. Headless reduces long-term maintenance by 60-70% on average.
- 04
Editor experience (who writes)
WP monolithic: Gutenberg + classic, editors already trained. WP headless: same WP admin, zero learning curve. Pure headless: different admin (Sanity Studio, Contentful, Storyblok) — more focused and content-modeling-friendly, but WP-trained editors need 1-2 weeks onboarding. For teams with many non-tech editors, WP-based wins.
- 05
Team requirements (who maintains)
WP monolithic: any WP dev (~2000€/year freelance retainer). WP headless: needs React/Next dev + WP admin enabled (rare combo, costs more). Pure headless: needs React/Next dev + specific CMS know-how (Sanity, Contentful) — less rare but more expensive than median WP dev. Headless doubles senior team cost.
- 06
SEO + integrations
WP monolithic: SEO via plugins (Yoast/RankMath), auto schema, auto sitemap, 50k+ ready integrations. WP headless: frontend SEO must be rebuilt (next-sitemap, custom schema, meta), WP plugins that modify frontend don't work. Pure headless: custom frontend SEO, but total control (fine-grained schema, edge headers, custom OG). More powerful but more work.
04 — When WordPress monolithic is still the right choice
It's not cool, but often it's the rational call. Here are the cases.
1. Brochure site with <30 pages: blog/portfolio/showcase without huge traffic or multi-channel ambitions. 10€/month hosting, decent theme, done. Headless is pure overkill.
2. Professional firms (lawyer, architect, accountant): content driven, non-tech editor (assistant updating news), contained budget. WP does exactly what is needed.
3. SMB with marketing team of 1-2: whoever writes content is a generalist, doesn't want to learn a new CMS. WP reduces friction.
4. Small-mid e-commerce (10-200k€/year): WooCommerce has a mature ecosystem (payment gateways, shipping, accounting). Shopify is an alternative, but WooCommerce stays valid.
5. Hard budget cap <3k€: headless requires 5-15k€ initial dev investment. Below this threshold, well-built WordPress mono > poorly-built headless.
In all these cases, headless perf gain doesn't justify the TCO. WP done right (custom or lightweight premium theme, <5 essential plugins, decent hosting, free Cloudflare CDN) can hit green CWV and competitive SEO.
05 — When to switch headless (and what you need)
When headless TCO pays for itself in added value, and the prerequisites.
1. Performance critical for business: mid-large e-commerce where every 100ms of LCP = measurable conversion loss. SaaS where slow demo page = bounce. Editorial high-traffic where ad revenue scales with engagement.
2. Multi-channel content: same content must appear on web + mobile app + newsletter + smart TV + signage. WP isn't designed for multi-channel; headless is.
3. Strong dev team (in-house or retainer): needs senior React/Next/Astro who can do static gen + edge functions + CMS integration. Without this, headless becomes Frankenstein.
4. Enterprise compliance: separating backend (CMS, data) from frontend (rendering) makes GDPR audits, security review, isolation easier. Enterprise companies often require it.
5. Editorial > 200 articles + traffic > 200k PV/month: WP monolithic starts to suffer. WP headless or pure headless with static gen + edge cache holds volume better.
Minimum prerequisites: 8-25k€ initial budget, senior dev reachable for maintenance, content modeling done well before picking the CMS, team with at least 1 person who knows Git + CI/CD deploy. If any of these is missing, WordPress mono or WP headless remain safer choices.
06 — Decision matrix by use case
Eight typical profiles, eight orientations. Starting point, not dogma.
Personal blog/portfolio
WP mono or static SSG (Astro)
Low volume, simple scope, low budget. WP mono is fine; Astro static + Markdown is a modern alternative without overhead.
Professional firm
WP mono
Content driven, non-tech editor, contained budget. WP ecosystem for local SEO + booking plugins covers everything.
SMB brochure site
WP mono or WP headless (if perf priority)
Default WP mono. Switch to WP headless if Core Web Vitals are explicit SEO goals and budget supports dev investment.
Small-mid e-commerce (10-500k€/year)
WordPress + WooCommerce
Mature WC ecosystem, gateways+shipping+accounting. Shopify is an alternative, but WC stays valid below this volume.
Mid-large e-commerce (500k-5M€/year)
Headless: Shopify Hydrogen / Medusa + Next
Critical performance and CRO, multi-channel, custom checkout. WC scales badly past 1M€/year; headless is justified.
Editorial / publisher (>200 articles)
WP headless
Editors trained on WP, but Next/Astro frontend for perf + scale. Multi-channel via API. Best cost/feature combo.
SaaS marketing site
Pure headless (Sanity/Contentful + Next)
Tech budget available, strong dev team, perf critical for demo conversion, precise content modeling (features, pricing, docs).
Multi-channel content (web + app + newsletter)
Pure headless
WP isn't designed for multi-channel. API-first CMS with decoupled frontends = the only sane way to scale content distribution.