"We're going headless" became fashionable around 2020 and hasn't really slowed. It's the right answer for some Australian businesses and a $20k mistake for others. Here's the honest framing.
What headless WordPress actually is
Traditional WordPress: PHP renders the page on every request, hits the database, returns HTML. Slow but simple. The theme controls everything.
Headless WordPress: WordPress is just the editing backend. Editors still log into wp-admin to write posts. But the public site is built in something else, usually Next.js or Astro, that fetches content from WordPress's REST or GraphQL API and renders it.
Result: editors get the WordPress they know. Visitors get a static-fast site that doesn't touch a database on page load.
Why Australian businesses are switching
- Speed. A traditional WordPress site lands at 50–70 on Lighthouse without serious tuning. A Next.js front-end on the same content lands at 95+ effortlessly. Real money in conversion and SEO.
- Design freedom. Themes constrain you; React/Astro doesn't. Custom motion, custom layouts, custom interactions all become possible.
- Better hosting economics. The frontend hosts on Vercel or Netlify ($20–$200/month). The WordPress backend hosts on a small Kinsta instance ($35/month). Same content, half the hosting cost of a serious managed-WordPress plan.
- Resilience. If WordPress goes down for an hour, your site keeps serving cached pages. The decoupling is a uptime feature.
The costs nobody tells you about
- Build cost is 2–3x. A custom Next.js + WordPress stack runs $16k–$30k. A great traditional WordPress site runs $7k–$12k.
- Plugin compatibility breaks. Many WordPress plugins assume they own the frontend (Yoast, contact forms, comment plugins). In headless, you re-implement their frontend bits in the React layer.
- Preview is harder. Editors are used to clicking "Preview" and seeing the post. In headless, you have to build a preview mode that works against your decoupled frontend. Most stacks support it; few support it elegantly.
- Two stacks to maintain. WordPress core, plugins, security patches. Plus Next.js, npm dependencies, hosting. Twice the surface area.
Going headless is buying speed and design freedom with engineering cost. If you're not at the size where the speed and freedom move real money, you're paying for nothing.
When headless wins
- Content-heavy publisher with serious SEO ambitions. Speed and Core Web Vitals genuinely move rankings.
- Brand-led site that needs custom motion or layout. Themes won't get you there.
- Multilingual or multi-region site. Frontend frameworks handle this far better than WordPress alone.
- Existing React app. If you already have a React app, sharing components with the marketing site is a real win.
When headless loses
- Small site, small team. Stay on traditional WordPress. The speed gains aren't worth the engineering.
- WooCommerce primary. Headless WooCommerce is doable but painful. Use Shopify if commerce is your main product.
- Heavy plugin reliance. If you're built on a stack of frontend-coupled plugins (membership, forum, complex forms), the rebuild cost is huge.
- No engineering team. Two stacks need two competencies. If you don't have them, traditional managed WordPress is correct.
The frontend choice
Three real options:
- Next.js (React). The most flexible, biggest ecosystem, best for app-like sites. Best when you have React knowledge already.
- Astro. Newer, ships less JavaScript, fastest possible result. Best for content-heavy sites with light interactivity.
- Eleventy. Static site generator, often even faster, simplest mental model. Best when content rarely changes.
The decision in three sentences
Speed and design freedom are real benefits. They cost money in engineering. Make the switch when those benefits move enough revenue or rankings to pay for the switch, not before.
The bottom line
Headless WordPress is a real upgrade for content publishers and brand-led businesses with the budget to support it. For most small-business sites, traditional WordPress (or Webflow) is still the right call.
If you want three Australian developers to weigh in on whether headless is right for your specific case, FindDevs gets you those quotes. Free, three real opinions, in 24 hours.