Home / Services / Headless builds / Astro
Front ends built with Astro, for WordPress
WordPress content. Pages that ship almost no JavaScript.
Astro turns your WordPress content into plain HTML pages and adds JavaScript only to the parts that need it. It is our default front end for content-led sites, and we have delivered it for clients.
Proof you can check
Our own products, numbers and community record, linked wherever you can check them.
(opens in a new tab)
(opens in a new tab)
(opens in a new tab)- 300,000+sites run Divi Extended (opens in a new tab)
- Platinumsponsor, WordCamp Rajasthan 2026 (opens in a new tab)
- 6 + 1free plugins and a theme on WordPress.org (opens in a new tab)
- 4.7 / 5on Trustpilot, 116 reviews of Divi Extended (opens in a new tab)
Why Astro
Why Astro is our default for content sites.
Astro 7 is the current major version. These are the parts that matter for a site fed by WordPress.
01
Islands
Astro renders components to HTML and CSS and strips client-side JavaScript automatically. Only the parts you mark as interactive, such as search or a form, load JavaScript.
02
Built ahead, or on demand
Pages are built ahead of time by default. Routes that must always be fresh can be rendered on demand, one route at a time.
03
Content collections
Content from WordPress can be loaded at build time, or fetched live per request for pages that change often.
04
Open source, hosted anywhere
Astro is MIT-licensed. Its company joined Cloudflare in January 2026, with a public commitment that Astro stays open source and deployable to any host.

Astro with WordPress
How we connect the two.
The decisions we make on every Astro front end for WordPress.
Fetching content
Astro reads your content from the WordPress REST API, which is open for public content by default. For larger content models we can add WPGraphQL, which Astro’s own WordPress guide lists as an option.
Previews
Astro’s WordPress guide does not cover previews, so we build them: the WordPress Preview button opens a private route that fetches the draft with authentication and renders it on demand.
Publishing
When you publish, WordPress triggers a rebuild through your host’s build hook, or refreshes just the changed routes when pages are rendered on demand.
Hosting
Astro has official adapters for Node, Netlify, Vercel and Cloudflare. Static pages can be served from any host or CDN.
Interactive parts
Islands can be written as Astro components or with React or Vue, so an existing component library can come along.
Beyond WordPress
Astro can also pull content from Markdown files and other sources, so documentation or a product catalogue can live next to your WordPress content in one site.
When Astro is not the pick.
If your site behaves like an app, with logins, dashboards and personalised pages, or your team already works in React or Vue, Next.js or Nuxt can fit better. We have delivered both.
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 | In a headless build | How |
|---|---|---|
| Custom fields (ACF) | Works as-is | Fields are exposed to the API and mapped to components |
| Yoast SEO, Rank Math | Works with integration | Head tags read through their REST endpoints |
| Gravity Forms | Works with integration | Submissions posted to its REST API; entries stay in WordPress |
| WooCommerce | Works with integration | Store API for cart, checkout and products |
| Redirection | Works with integration | Redirects exported into the front-end build |
| Page builders (Divi, Elementor) | Rebuilt | Layouts are rebuilt as front-end components |
| Sliders, pop-ups, shortcode output | Rebuilt | Rebuilt as components, or replaced |
| Cookie banners, analytics, chat | Rebuilt | Added 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.
Questions
Astro, answered.
Why Astro for a WordPress site?
Astro sends plain HTML with no JavaScript by default and adds it only to interactive islands, which suits content-led sites. WordPress stays where your team edits.
Is Astro safe to build on long term?
Astro is MIT-licensed open source. Its company joined Cloudflare in January 2026, with a public commitment that Astro stays open source, with a public roadmap, and deployable to any host. Astro 7 is the current major version.
Can editors preview drafts?
Yes. We build a private preview route that the WordPress Preview button opens. It fetches the draft with authentication and renders it on demand, never cached and never public.
Where can an Astro site be hosted?
Astro has official adapters for Node, Netlify, Vercel and Cloudflare, and fully static pages can be served from any host or CDN.
Can we use React or Vue components?
Yes. Astro islands can use React or Vue components, so an existing component library can be reused.
What if Astro is not right for us?
Then we recommend Next.js or Nuxt, which we have also delivered, or a classic block theme build. The choice is made in discovery, with the reasons written down.
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.
