Headless WordPress: is it relevant to most SMEs yet?

Short answer: Headless WordPress separates content API from front-end frameworks—powerful for product teams, usually overkill for typical NZ brochure and WooCommerce sites.

You inherit two deployment surfaces, auth complexity, and higher ongoing dev cost. Be sure you need omnichannel publishing or a bespoke app—not just buzzword appeal.

When headless can make sense

• Same content feeds web, app, and partners via APIs.
• Front-end team insists on a JavaScript framework with strict performance budgets.

When to stay traditional

Single marketing site with forms and modest ecommerce—monolithic WordPress remains maintainable.

Total cost of ownership

Budget hosting, CDN, API monitoring, and developers comfortable with both stacks.

Frequently asked questions