Headless WordPress

Headless WordPress is an architecture in which WordPress is used only as a content management backend, while the public-facing site is rendered by a separate front-end (often React, Next.js, Astro, or SvelteKit) that consumes WordPress content through its REST or GraphQL API.

When headless makes sense

• You want a modern JavaScript front-end (interactive UI, app-like behavior) without leaving the WordPress editorial workflow.
• WordPress feeds multiple destinations — a public site, a mobile app, a third-party platform.
• Performance budgets demand static or edge rendering that’s hard to achieve with a classic theme.
• You’re consolidating multiple sites onto one editorial backend.

Trade-offs

• Most plugin functionality that injects HTML into the front-end stops working — preview, forms, ecommerce, page builders all need re-thinking.
• Two systems to host, monitor, and secure (the WordPress backend and the front-end).
• Editorial preview becomes a deliberate feature you have to build, not a built-in.
• SEO and structured data move to the front-end’s responsibility.

When a classic block-first WordPress build is the better answer

For most marketing and editorial sites the modern block editor is fast enough and avoids the architectural cost of headless. Hello World recommends headless only when there’s a concrete reason — performance, multi-channel publishing, or a non-WordPress front-end requirement — that outweighs the operational complexity.