1. The missing piece: the backend
Astro is a frontend framework. It does not provide a database, an admin area or user management. WordPress is a complete system.
To make an Astro site manageable for a client, you need to pair it with a headless CMS such as Sanity, Strapi or WordPress headless.
- Two systems to maintain instead of one.
- More complex API management.
- CI/CD build and deploy flows that are easier to break.
2. The illusion of extra speed
A static Astro site may benchmark slightly faster than a well-optimized WordPress site, but the extra editorial complexity is rarely free.
For a developer's personal blog, the trade-off can make sense. For a company site that publishes regularly, usually not.
3. Autonomy and costs
Custom Astro sites cost more to build and require specialized developers for maintenance.
WordPress democratizes site management: pages, menus and tracking can be updated without calling the agency for every change.
If you lock the client into a system they do not understand, you create dependency instead of partnership.
Verdict
If the project is a static landing page updated once a year, Astro is a strong option.
If the client wants a living site with a robust backend, straightforward SEO and full autonomy, WordPress remains the more strategic choice.