1. There is no backend
Astro is a frontend framework. It ships without a database, an admin area or user management. WordPress is a complete system.
To deliver a client-editable Astro site you need to pair it with an external headless CMS: Sanity, Contentful, Storyblok, Strapi. Each has limited free tiers and costs that grow with content volume and users.
- Two systems to maintain instead of one.
- Two separate service contracts.
- A more complex, more fragile build and deploy pipeline.
2. Every feature needs to be built from scratch
WordPress ships with a mature ecosystem of ready-to-use tools: technical SEO, redirect management, contact forms, site search, cookie consent, caching, user roles, translations, e-commerce.
In Astro none of this is included. Every feature requires a custom integration or a paid external service.
| Feature | WordPress | Astro |
|---|---|---|
| Technical SEO (sitemap, meta, schema) | Mature plugin (Yoast, RankMath) | Built by hand or via npm package |
| Redirect and 404 management | Dedicated plugin | Config file or hosting service |
| Contact forms | Plugin (Contact Form 7, Gravity Forms) | External service (Formspree, Netlify Forms) |
| Site search | Native plugin or Algolia | Custom integration |
| Cookie consent and privacy | Dedicated plugin | Custom component or SaaS |
| Caching and performance | Plugin (WP Rocket, LiteSpeed) | Depends on hosting and CDN |
| Multilingual | WPML, Polylang | Custom i18n or headless CMS |
| User accounts and protected content | Native system | External auth service (Auth0, Clerk) |
| E-commerce | WooCommerce | Shopify, Snipcart or custom build |
3. Initial savings paid back over time
An Astro site may cost less to build in its first version. But total cost is measured in years, not weeks.
Astro changes its API with every major release: from Astro 1 to Astro 5 there have been four migrations, each requiring active work on existing codebases. A single deprecated npm package can stall the build and freeze the site.
WordPress has a far more conservative update policy. Themes and plugins built with care hold across versions without rewrites.
4. Client autonomy is close to zero
Without a headless CMS the client edits code files directly. With a headless CMS they get a separate interface, disconnected from the real site preview, with more fragmented publishing flows.
WordPress gives clients an admin area they can learn in a few hours: pages, menus, images, forms, users — all without opening a text editor.
When the client depends on a developer for every content update, operational costs grow and the relationship becomes harder to sustain.
5. Developer dependency and long-term maintenance
A custom Astro site depends on specific architectural choices: the headless CMS selected, integrations built for that project, a pipeline configured in a particular way. Anyone who takes over later has to rebuild the entire context from scratch.
WordPress has the largest freelance and agency developer pool in the world. Finding someone to maintain or extend a project is straightforward, even years after the initial build.
6. When Astro genuinely makes sense
Astro is the right choice in specific contexts: static landing pages updated once or twice a year, developer-maintained personal portfolios, promotional microsites with no editorial backend.
It also makes sense when a team already has an internal backend and only needs a fast rendering layer, or when performance is a critical technical requirement and the budget covers the added complexity.
For everything else — company sites, e-commerce, active blogs, sites with registered users, portals — WordPress remains the more solid choice, more cost-effective over time and more manageable without depending on a developer for every small change.
Verdict
Astro is not a bad choice in absolute terms. It is a bad choice for most agency projects, where clients need autonomy, maintenance needs to stay affordable and the budget does not cover building every single feature from scratch.
WordPress democratizes site management. Astro centralizes it in the developer.
Frequently asked questions
Can WordPress be optimized enough to match Astro's performance?
A well-optimized WordPress site — solid theme, configured caching, CDN — reaches Lighthouse scores between 90 and 100 on static pages. The gap with Astro exists but is rarely noticeable to end users. The real question is: what is that gap worth against the cost of maintaining a more complex architecture?
What about using WordPress headless as the CMS with Astro as the frontend?
It is a combination used by teams with dedicated resources and specific requirements. In this setup, many of WordPress's advantages disappear — integrated admin, immediate preview, plugins that operate on the frontend — while Astro's complexity is added. It is rarely the optimal choice for agencies serving standard clients.
Can clients learn to use a headless CMS?
They can. But it is worth asking why. A headless CMS requires more training, has less intuitive interfaces and publishing flows are more fragmented. WordPress was designed precisely to be used by people who are not developers.
Next step
Considering WordPress for your next project?
I can help assess the technical choice against your real requirements and build a WordPress solution that holds up over time.
Talk about the project