Headless WordPress

WordPress for your editors. A fast frontend for everyone else.

Your team keeps the WordPress admin; visitors get pages built with Astro or Next.js and served from the edge. It starts with an honest fit check, and if a fast classic WordPress site would do the job for less, that's what we'll tell you.

No passwords needed to quote

Write as much as you like: what's happening, what you want, links, errors. The more we know, the more exact your fixed price.

Or start from what you want
An honest fit check firstYour editors keep WordPressOne fixed price and a date
4.9 from 450+ clients Astro or Next.jsWPGraphQL or the REST APILive site runs throughout
The fit check

Headless isn't for every site. Here's how to tell.

Answer six questions and the needle moves. It's the same reasoning the free fit check uses on your real site.

  1. Speed is how you win customers, and your site is slow today
  2. The same content also feeds an app, another site or a screen
  3. Your pages rely on plugins that draw on the page: page builders, form builders, store add-ons
  4. Your editors lay out pages visually, block by block
  5. Most pages look the same for every visitor: no logins, carts or dashboards
  6. Someone looks after a JavaScript codebase for you, or you want us to

Answer all six to see where your site lands.

How it runs

What happens when your team presses Publish.

WordPress keeps the content; the frontend serves it from the edge. Pick a moment to follow it through.

WordPressYour editors, as today
Content APIWPGraphQL or the REST API
FrontendAstro or Next.js, at the edge
VisitorsPhones and desktops
  1. 0.0 sAn editor presses Update in WordPress.
  2. 0.2 sWordPress tells the frontend which page changed.
  3. 1.4 sThe frontend rebuilds that page and the lists it appears on, nothing else.
  4. 1.9 sThe edge drops its old copy.
  5. About 2 sVisitors get the new page.

No full-site rebuild and no waiting for a deploy: only what changed is rebuilt. Example timings.

Also carried over: SEO titles, descriptions and schema from Yoast or Rank Math, redirects and the sitemap, menus, images in modern formats, and every URL.

The site you're reading runs on the same kind of frontend: Astro, served from Cloudflare's edge.

How it works

From fit check to launch in two to ten weeks.

A blog or a brochure site is two to four weeks; a large site with many content types, six to ten. Your live site keeps running throughout.

  1. Free, 2 days

    The fit check

    We look at your site, its plugins and your team, then say whether headless fits. If it doesn't, you hear that first.

  2. Week 1

    Content and API

    Post types, fields and menus exposed through WPGraphQL or the REST API; previews and publish hooks wired in.

  3. Weeks 2 to 8

    The frontend

    Built on Astro or Next.js beside your live site, every URL kept, green Core Web Vitals checked before launch.

  4. One evening

    Switched in one evening

    The domain moves to the new frontend; WordPress keeps running behind it, now private.

The price

How much headless WordPress costs.

One fixed price and a date, sent after the free fit check. If headless doesn't fit, the check costs nothing and tells you what would.

From$4,999 Most headless builds: $4,999 to $14,999

What moves the price

  • The frontend framework and where it is hosted
  • How much of the site has to be live, not static

Every headless build includes

  • An honest fit check first
  • Previews that open the real design
  • Publish in seconds, no full rebuild
  • Forms, search and SEO data carried over
  • Both codebases in your name
An honest noIf headless won't pay off for your site, the fit check says so, and says what would.
No surprise second billThe frontend's hosting is named in the quote, with its monthly cost.

A headless store, several sites on one WordPress, or content for an app are quoted after the fit check. Hosting and a care plan are separate.

Client reviews

Checked by other agencies, trusted by picky clients.

4.9
Average from 450+ clients · Read the reviews
★★★★★
“…they work very cooperatively with us behind the scenes and do superb work, on-time, and on-budget.”
David T.freshviewpartners.com
★★★★★
“I am an actual client of Roundborders and am VERY picky when it comes to who I work with…”
Emma T.emmatang.com
★★★★★
“…he never hesitates to fix issues quickly and ensure the brief is 100% fulfilled.”
Andrew F.standout-cv.com

Questions about going headless.

Anything else? Ask in the box at the top. We usually reply within a few hours.

Contact us
What happens to my existing WordPress hosting?

WordPress stays, on its current host or a smaller one, but it no longer serves visitors: the frontend runs on an edge platform such as Cloudflare, Vercel or Netlify. That's two systems to pay for, so the quote names the frontend's hosting and its monthly cost before you decide.

Will my content editors still use WordPress?

Yes. Editors keep the same WordPress admin, posts, pages and fields. Two things change: Preview opens the new frontend (we build previews on every project), and page-builder layouts become blocks and templates the frontend knows how to show. Your team tries it on staging before launch.

Will I lose my SEO rankings after the migration?

Not if it is done carefully. Every URL is kept or redirected, and the titles, descriptions, canonicals and structured data from Yoast or Rank Math come through the API into the new frontend, with the sitemap and redirects built in.

Can my WooCommerce store go headless?

It can, but it's rarely the right first step. The catalogue reads well through the API, but the cart, checkout, payments and many extensions are built for WooCommerce's own pages, so a headless store means rebuilding them. Most stores do better keeping checkout classic and making the rest fast, or going hybrid; the fit check says which.

What happens to my existing plugins?

Plugins that manage data (ACF, Yoast or Rank Math, WooCommerce's catalogue) keep working and are read through the API. Plugins that draw on the page (page builders, sliders, form builders, many store add-ons) don't show on a headless frontend, so what they did is built into it, or that part of the site stays classic.

How much faster will the site actually be?

Usually much faster, because pages are prebuilt or cached at the edge and ship little JavaScript, and green Core Web Vitals is checked before launch. The fit check measures your site as it is first, so you see the starting point and a realistic target before paying for anything.

Is ongoing maintenance more complex after going headless?

A little. WordPress still needs its updates, and the frontend is a second codebase with its own updates and hosting. Both are documented and in repositories in your name, and a care plan can look after both.

How long does the migration take?

Scope determines the timeline. A brochure site or blog typically takes 2–4 weeks. A large WooCommerce store or heavily customised site with many custom post types can take 6–10 weeks. We'll give you a precise timeline as part of your free estimate.

How much does a headless WordPress site cost?

Most headless builds run $4,999 to $14,999: a blog or marketing site on Astro sits near the start, larger sites with many content types or app features toward the top. A headless store, several sites on one WordPress, or content for an app are quoted after the free fit check. The frontend's hosting is a second monthly cost, named in the quote.

Fast for visitors, familiar for editors.

Tell us about your site. A free fit check, then one fixed price and a date if headless fits, or an honest no if it doesn't.

After launch

Two codebases, one care plan: WordPress updates tested on a staging copy first, the frontend's dependencies kept current, daily backups and monitoring. From $149 a month.

See the care plans
Not quite? Pick another service

Fix something

Build something

Move to WordPress

Look after my site

Full details

Everything you wrote goes with it. The estimate is free and fixed before any work starts.