Headless WordPress + Astro is a popular escape hatch: keep WP as the editorial database, ship a fast Astro frontend. It works - until plugin gravity and WP APIs become the bottleneck you moved the frontend to avoid.
Why teams try this
- Editors already know WordPress- Astro ships less JavaScript for content sites- You can keep permalinks and gradually migrate## How the architecture looks
- WordPress exposes REST or GraphQL (WPGraphQL)- Astro fetches posts at build time (or on-demand)- Templates map WP fields into Astro components- Media still often lives on the WP uploads host## Pain you should expect
- Preview and draft workflows get awkward- Plugin-dependent fields do not always serialize cleanly- You still maintain WordPress security updates- Structured content is weaker than purpose-built headless CMSs## When to switch CMS entirely If you are already rebuilding the frontend, evaluate a true headless CMS (BCMS included). You keep Astro's performance and gain cleaner models, better media UX, and fewer WP-shaped constraints - especially for multi-framework teams. ## Related reading
- Headless WordPress examples- Astro website examples- Best CMS for AstroWant setup notes, tradeoffs, and migration guidance? Read the complete guide: Headless WordPress and Astro.
