🎉 Black Friday Sale starts soon! 23 Save the date

0Days

0Hours

0Minutes

0Seconds

Home / Services / Development for WordPress / Headless builds

Headless builds on WordPress

Headless builds on WordPress, with the front end that fits.

Your team keeps the WordPress editor. Visitors get a fast front end built with Astro, Next.js or Nuxt, chosen for your site. We have delivered all three for clients, and we will tell you honestly when a classic build is the better buy.

How it fits together
  1. Your editorsThe WordPress editor they know
  2. WordPressContent, media, SEO data
  3. APIREST or GraphQL
  4. Front endAstro, Next.js or Nuxt
  5. Edge networkPages served close to visitors

What headless means

WordPress keeps the content. A separate front end shows it.

In a headless (or decoupled) build, WordPress stays the place your team writes and manages everything. The pages visitors see are rendered by a separate front end that fetches the content through the WordPress REST API, built in since WordPress 4.7, or the WPGraphQL plugin.

  1. EditorsWrite, edit and publish in the block editor
  2. WordPressContent, custom fields, media library, SEO plugin, users and roles
  3. REST API or WPGraphQLContent leaves WordPress as data (JSON)
  4. Front endAstro, Next.js or Nuxt; pages built ahead of time or on demand
  5. Edge networkNetlify, Vercel or Cloudflare serve pages close to visitors
  6. VisitorsFast pages, with no WordPress admin on the public domain

There is a middle way too: a hybrid, where a block theme renders most of the site and the API feeds an app or one demanding section. We build all three and help you choose.

Why teams choose it

What headless actually changes.

Each point is a mechanism, not a promise. We measure the result on your build.

01

Light pages by design

Pages are built as HTML ahead of time or on the server, with JavaScript only where it is needed. How light depends on the front end we choose with you.

02

Admin off the public site

The WordPress login and admin live on a separate address. The public site is the front end only.

03

One source, many channels

The same content feeds your website, an app, a partner feed or a kiosk, managed once in WordPress.

04

Front-end freedom

Your design system as real components, without fighting a theme or page builder.

The Elicus team at work in Jaipur

Choosing the front end

The front end that fits your site, not our habits.

WordPress stays the same underneath. The front end is chosen for your content, your traffic and your team. We have delivered headless builds with all three of these.

Our default

Astro

Content-led sites: marketing sites, publishers, documentation. Pages are plain HTML by default, with JavaScript only in the parts that need it.

  • Static HTML first, interactive islands
  • Built ahead of time or on demand, page by page
  • Open source, hosted anywhere

Front ends built with Astro

For app-like sites

Next.js

Sites that behave like apps: logins, dashboards, personalisation, or a team that already works in React.

  • React components and server rendering
  • Pages refreshed on demand when content changes
  • Ready-made WordPress previews with Faust.js

For Vue teams

Nuxt

The same kind of front end for teams that work in Vue, with server rendering and static pages where they fit.

  • Vue components and server rendering
  • Static or on-demand pages
  • A good fit when your team already knows Vue

Considering another framework, such as SvelteKit? Tell us what you have in mind and we will give you an honest view.

Is headless right for you?

When headless is not the right call.

Headless costs more to build and run: two systems to host, previews to build, front-end work for every new layout. We make Divi products, and we will still tell you plainly when a Divi or block theme site is the better buy.

When headless fits and when a block theme is better
Headless is a good fit whenStay with a block theme when
Content reaches more than your website (an app, partners, other channels)A brochure or small business site with one channel and occasional updates
You have, or want, a front-end design system and developers to own itMarketing needs to build new layouts without a developer each time
Traffic is high and pages are content-heavyThe site depends on a page builder, including Divi, or many front-end plugins
Budget covers two systems over timeYou need interactivity, not decoupling: the Interactivity API and a good block theme cover a lot

The hard parts, handled

Where headless builds usually go wrong.

Previews, publishing, SEO, forms and search are where most headless projects get stuck. We plan each one before the build starts.

Previews

Drafts are private, so headless previews are built, not automatic. We point the WordPress Preview button at a private route on the front end that fetches the draft with authentication and renders it on demand.

  1. Editor clicks PreviewIn WordPress, as usual
  2. Preview linkPoints to a private preview route on the front end
  3. Signed fetchThe draft is fetched with authentication
  4. Rendered on demandNever cached, never public

Publishing

When you publish, WordPress sends a webhook. The front end either rebuilds through a build hook (Netlify, Vercel) or refreshes just the changed pages.

  1. Editor clicks PublishIn WordPress
  2. WebhookWordPress tells the front end what changed
  3. Rebuild or refreshA build hook, or only the changed pages are refreshed
  4. Live on the edgeThe new page is served everywhere

SEO

Yoast exposes each page’s head tags through the REST API, and Rank Math has a headless setting with its own endpoint. Sitemaps and redirects must live on the public domain, so we generate them as part of the front-end build, with canonical URLs and structured data checked before launch.

Forms

Front-end form plugins do not render on a headless site, so forms submit to WordPress through an API. Gravity Forms, for example, has a REST endpoint that runs validation, notifications and spam checks and keeps every entry in your dashboard.

Search and comments

WordPress has a search endpoint we can build on, or we connect a hosted search. Anonymous comments through the API are off by default in WordPress, so comments need a small authenticated bridge or a comment service.

Stores

WooCommerce’s Store API gives cart, checkout and product data to any front end. Extensions that change the store’s theme layer need rework. See development for WooCommerce.

Plugin compatibility

What happens to your plugins.

Plugins that work in the WordPress admin keep working. Plugins that print things on the front end are rebuilt. We audit every plugin before we quote. We build plugins ourselves, so we know this layer from the inside.

Plugin compatibility in a headless build
PluginIn a headless buildHow
Custom fields (ACF)Works as-isFields are exposed to the API and mapped to components
Yoast SEO, Rank MathWorks with integrationHead tags read through their REST endpoints
Gravity FormsWorks with integrationSubmissions posted to its REST API; entries stay in WordPress
WooCommerceWorks with integrationStore API for cart, checkout and products
RedirectionWorks with integrationRedirects exported into the front-end build
Page builders (Divi, Elementor)RebuiltLayouts are rebuilt as front-end components
Sliders, pop-ups, shortcode outputRebuiltRebuilt as components, or replaced
Cookie banners, analytics, chatRebuiltAdded to the front end directly

How a build runs

Five steps, decided up front.

You approve the architecture before we build anything.

01

Discovery

Content model, plugin audit and a clear decision: headless, hybrid or block theme.

02

Architecture

Post types, fields, API, hosting and how publishing will work.

03

Front end

Your design built as a component library, on staging.

04

Editorial setup

Previews, publishing, and training for your editors.

05

Launch and care

Redirect map, SEO checks and go-live, then care for both halves.

Hosting the two halves

Two systems, both yours.

The WordPress half

WordPress runs on a PHP host, on its own address. We can look after it on a care plan.

See care plans

The front-end half

The front end runs on Netlify, Vercel or Cloudflare. We can set the accounts up in your name, so you own both halves.

Measured, not promised.

We test your current site before we start and the new build before launch, and show you both. Moving from Drupal, Joomla or Wix? We can migrate and go headless in one project.

For agencies

Your development team for WordPress, under your name.

Agencies around the world send us their builds on WordPress. We do the work, you keep the client, and our name appears nowhere.

White-label

Your brand on everything. No Elicus credit, ever.

NDA-friendly

Happy to sign yours before we see a brief.

Scale on demand

We grow the team to fit the project.

Your terms

Something specific in mind? We'll talk it through.

Questions

Headless, answered.

What is a headless setup with WordPress?

WordPress stays the place your team writes and manages content. A separate front end fetches it through the REST API, built in since WordPress 4.7, or WPGraphQL, and renders the pages visitors see.

Headless or decoupled: is there a difference?

Most people use the words interchangeably. We also build hybrids, where a block theme renders most pages and the API feeds an app or one section.

Will my editors still use the normal WordPress editor?

Yes. The block editor, custom fields, media library, roles and SEO plugin stay. We map your blocks to front-end components and set up previews.

Can we preview drafts before publishing?

Yes, but it is built, not automatic. The Preview button is pointed at a private route on the front end that fetches the draft with authentication and renders it on demand.

How fast do changes go live after I click Publish?

WordPress sends a webhook that triggers a rebuild or refreshes just the changed pages. We measure and tell you the real time for your build.

What happens to SEO?

Yoast and Rank Math both expose head tags for headless front ends. Sitemaps and redirects are generated on the public domain as part of the build, and we check canonical URLs and structured data before launch.

Will our plugins still work?

Admin-side plugins do: custom fields, SEO data, WooCommerce data. Plugins that output front-end markup, such as page builders including Divi, sliders and pop-ups, are rebuilt as components. We audit every plugin before quoting.

How do forms work?

Submissions are posted to WordPress through an API, so entries stay in your dashboard. Gravity Forms, for example, runs validation, notifications and spam checks on submissions sent to its REST endpoint.

Which front end will you use?

The one that fits: Astro for content-led sites, Next.js for app-like sites or React teams, Nuxt for Vue teams. We have delivered all three and recommend one in the discovery step, with the reasons.

Where is it hosted, and who owns it?

WordPress on a PHP host, which we can manage, and the front end on Netlify, Vercel or Cloudflare. We can set the accounts up in your name.

Is headless more expensive?

Usually, yes: two systems to host and maintain, previews and integrations to build, and front-end work for each new content type. That is why we tell you when a block theme is the better buy.

Can you make our WooCommerce store headless?

Yes. WooCommerce's Store API covers cart, checkout and products for any front end. Extensions that change the store's theme layer need rework, which we scope first.

Architecture call

Headless, hybrid or block theme?

Tell us about your site, your content and your team. We come back with a clear recommendation, even when it is not headless.

We start with a short call to check whether headless is right for you. If it is not, we say so.

What do you need?