Yuri Osipov · Founder, SEO & analytics

Headless WordPress: keep the admin, replace the rendering

Headless WordPress is the pragmatic middle. It does not ask a newsroom to learn a new editor, does not ask the finance team to cancel a working subscription, and does not ask the client to migrate ten years of content. It asks one thing: stop letting WordPress render the page.

In short

What headless WordPress actually is

A normal WordPress site does two jobs: store content and render it. Headless splits them. WordPress keeps the first job and exposes content over HTTP; the front‑end does the second.

Two ways to read the content:

Structure comes from custom fields. Advanced Custom Fields (or its open‑source successor Secure Custom Fields) turns a page into typed data instead of a blob of block markup — and that is the single most important decision in a headless WordPress project. Without it, you are parsing HTML.

Who it fits

It fits badly when the WordPress installation is already a liability — abandoned plugins, an unsupported PHP version, a theme nobody understands. In that case headless makes the front‑end fast while leaving the actual problem in place.

How it connects to Astro

Fetch at build time, prerender, deploy static:

// src/lib/wp.ts
const WP = import.meta.env.WP_URL

export async function getPosts() {
  const res = await fetch(`${WP}/wp-json/wp/v2/posts?per_page=100&_embed`)
  if (!res.ok) throw new Error(`WP: ${res.status}`)
  const posts = await res.json()
  return posts.map((p: any) => ({
    slug: p.slug,
    title: p.title.rendered,
    date: p.date,
    html: p.content.rendered,
  }))
}

With WPGraphQL the same data arrives in one shaped query, which is nicer for pages built from flexible sections. Either way, the pattern is identical: fetch, map to your content model, render with your own components.

Publishing triggers a rebuild through a webhook — a small plugin or a function on the WordPress side calls your host’s deploy hook. For sections that change hourly, add on‑demand rendering for those routes and leave the rest prerendered.

Two setup details bite everyone exactly once. Authentication: the build only reads published content, so a read‑only application password is enough — write access stays inside the admin. Permalinks: the REST API lives under /wp-json, and permalink rules that swallow that path make the API answer 404s that look like authentication failures. Both are one‑line fixes — after you have spent an hour finding them.

Strengths

Weaknesses

When to choose it

Choose headless WordPress when the cost of changing the editorial tool is higher than the cost of running two systems — which is true for most established publishers and for many clients with a decade of content. It is also the honest recommendation when a team is not ready for a schema‑as‑code CMS but the current site cannot stay as it is.

If the team is technical and wants the CMS in the repository, Payload is the cleaner long‑term home. If editors want visual previews, Storyblok delivers that out of the box.

Summary

Headless WordPress is a bridge, and bridges are useful when there is a river. You keep the admin, the roles and the archive, and you gain a fast static front‑end that you own — at the price of maintaining WordPress properly and moving SEO, images and previews into the front‑end.

See how it compares in the headless CMS comparison for Astro, or start from the headless CMS hub. We move sites from classic WordPress to an Astro front‑end without stopping publishing — that is web development work, and the reasoning behind it is in why we stopped starting new projects on WordPress.

Screenshots in this series are placeholders — we will replace them with our own, taken on real projects.

Yuri Osipov

Yuri Osipov

Founder, SEO & analytics

Runs Take the Space. Specialises in technical SEO, measurable analytics setups and AI search visibility.

All posts by the author →
What does headless WordPress actually mean?
WordPress keeps storing and editing content, but stops rendering the public site. The front‑end — in our case Astro — fetches posts, pages and custom fields through the REST API or WPGraphQL and generates static HTML.
Do editors notice the difference?
Not on the admin side: the dashboard, roles, media library, revisions and plugins stay exactly as they were. The difference is that the theme no longer matters, so the site is rebuilt and deployed by your front‑end pipeline instead of being rendered on request.
Is headless WordPress more secure than a normal WordPress site?
It reduces exposure, it does not remove it. The public front‑end has no PHP and a tiny attack surface, but the WordPress installation still exists and still needs updates, hardened plugins and a patched PHP runtime — the vulnerabilities that hit PHP itself in 2026 proved that point.
Do SEO plugins still work?
Partly. Plugins that write meta tags through the theme no longer reach the page, because there is no theme. You either expose the fields through the API and render the tags in Astro, or manage metadata in the front‑end; either way, the SEO layer moves into your code.
How do content changes appear on a static site?
Publishing fires a webhook that starts a build. For news sites you add on‑demand rendering or incremental rebuilds for the sections that change constantly, and keep the rest static.

Want a high‑performance website?

Let’s discuss how we can help your business grow.