WordPress or Astro: choose by how your team works day to day
Compare editing, features, maintenance and redesign cost. A CMS can make Astro editable, and no technology guarantees search rankings.

- Published
- Updated
- Reading time
- 8 min
- Author
- SBSébastien BalieuFounder of Numinam
WordPress and Astro cover different ground. WordPress includes a content management system; Astro builds the front end of the site and can be connected to a CMS. So the choice has to be about the complete setup your team will use.
A marketing team can publish regularly with either, as long as editing was planned for. Before you choose, ask for a demonstration with a real page, a real image and a real translation.
WordPress and Astro at a glance
WordPress is an open source CMS, released under the GPLv2 or later licence. It runs on a PHP server with a database: the recommended setup calls for PHP 8.3 or higher, MySQL 8.0 or MariaDB 10.11, and HTTPS. The server assembles pages from the database, and a caching layer can serve ready-made copies of them.
Astro is a web framework designed for content sites: blogs, marketing sites, online shops. By default, it generates pages when the site is built, as static files. With a server adapter, Astro renders some pages on each visit, a client area for example.
| Criterion | WordPress | Astro |
|---|---|---|
| What it is | CMS with admin and front end | Front-end framework, connected to a CMS or to files |
| How it runs | PHP and a database on every visit, unless cached | Pages prepared in advance; a server only for on-demand pages |
| Editing | Built-in admin | The chosen CMS’s interface, or Markdown files |
| Multilingual | Plugin required | Built-in multilingual routing, content managed in the CMS |
| Shop | A plugin such as WooCommerce | Connected payment service or external shop |
| Licence | GPLv2 or later | MIT |
What changes for your team?
| Need | WordPress | Astro with a CMS |
|---|---|---|
| Publish content | Built-in admin | The chosen CMS’s interface |
| Preview a change | Workflow to check, depending on the theme | Preview and publishing to plan for |
| Add a feature | Plugin or custom development | Connected service or custom development |
| Maintain the site | Core, theme, plugins and hosting | Code, dependencies, CMS and services |
| Change provider | Export, access and configuration to hand over | Code, content, access and deployment procedure |
WordPress has roles and capabilities to organise who contributes: administrator, editor, author, contributor, subscriber. The result also depends on the fields and the theme: a very free-form visual editor can make approvals harder.
Astro can limit the JavaScript sent to the browser and produce light content pages. You still have to plan the editing screens, the permissions and the delay between publishing and the page going live.
Which CMS should you pair with Astro?
Astro’s documentation offers guides for around twenty CMSs, including Contentful, Decap CMS, Directus, Keystatic, Payload, Sanity, Storyblok, Strapi and TinaCMS. These tools are called “headless”: you use them to write and organise content, and Astro takes care of displaying it.
They fall into two families. Some CMSs store content in the site’s code repository, such as Decap CMS or Keystatic. Others store it in a hosted service that the site queries, such as Sanity, Storyblok or Contentful. The second family adds a third-party service, with its own account and pricing; the first ties publishing more closely to the deployment process.
WordPress can fill this role too. Its REST API exposes posts and pages, and Astro documents this headless WordPress setup. Your team keeps the admin it already knows. You then maintain two systems: the WordPress installation and the Astro site.
Astro also works without a CMS, using Markdown files. That option suits a team comfortable with a code editor and Git. For a marketing team, plan an editing interface.
Choose the CMS on a real test: create a page, preview it, translate it, replace an image, give a writer permissions. Ask where the content lives and how to export it if you switch tools.
When should you keep WordPress?
If your team publishes without trouble, your features are covered and the problems can be fixed within a reasonable scope, start with an audit of the existing site. A slow page can come from a theme, an image or a script, without calling for a full migration.
For features already handled by plugins, have their upkeep, compatibility and cost checked. The inventory should show which plugins are in use. A long list of plugins says little about whether your needs are covered.
When is Astro worth considering?
For a service site, an editorial catalogue or campaign pages, Astro can fit if the CMS and the integrations match the way your organisation works. The content can stay editable: check how to publish, preview and correct without opening the code.
For a logged-in area, payments or business rules, ask which components the architecture adds behind the pages. These features come with their own access, data and maintenance. The framework’s name tells you nothing about them.
Multilingual site or shop: what to check
In Belgium, a site in French and Dutch, often with an English version, needs proper translation management. WordPress does not handle multilingual content without a plugin: its documentation points to community plugins, each with a different approach. It announces built-in multilingual support for the last phase of the Gutenberg project, with no date on that page. Ask which plugin is planned, what it costs and how it links a page to its translations.
Astro has built-in multilingual routing: default language, URLs per language, fallback languages. The translations themselves are managed in the CMS. Check that the CMS you choose links each page to its translated versions and flags a missing translation.
For a shop, WordPress can rely on the WooCommerce plugin, installed in the same site. Astro connects to an external service: Astro’s ecommerce guide describes payment overlays such as Lemon Squeezy, Paddle or Snipcart, or a shop built on a payment service’s API. In that second case, orders, stock and invoicing live in another tool, with its own subscription.
Can performance make the decision for you?
The HTTP Archive technology report compares real-world experience by origin and by detected technology. To quote a rate from it, you need to keep the date, device, region, sample and filters. An average across different sites leaves the result for yours unknown.
Have your priority pages measured, and a representative page of the proposed solution tested. Ask for mobile results, interactions and the effect of third-party tools. The speed and conversion guide explains the metrics.
Whichever you choose, check the content, URLs, canonicals and forms. Switching technology guarantees neither better indexing nor more enquiries.
Security, updates and longevity
WordPress has applied automatic background updates since version 3.7: they are on by default on most sites, and translation files update themselves. Plugins and the theme still need watching. Each plugin adds code to maintain and to test after an update.
An Astro site prepared entirely in advance is made of static files: the public server runs neither PHP nor a database. The risks move to the project’s dependencies, the CMS, the hosting accounts and the deployment pipeline. A page rendered on each visit brings back a server to monitor.
Over the long term, WordPress is backed by a large open source community. The company that develops Astro joined Cloudflare in January 2026; the announcement states that Astro remains open source under the MIT licence, maintained and compatible with several hosts. Nobody can predict how a framework’s roadmap will evolve over five years: the open licence and full access to the code limit that risk for you.
What budget for a redesign?
Separate the new site from the work of migrating the old one. Get quotes for the inventory, the clean-up, content migration, redirects, translations, integrations and training. The scope of the migration can change the budget.
Add the recurring costs of the CMS, hosting, plugins or services, and maintenance. Compare the cost over the same period, along with the work left to your team.
The tests to ask for before switching over
Have a page published by the person who will be doing it. Test the draft, the preview, the translation, the image and a correction after publishing. Tell a content change apart from a new page type that needs development.
Keep the URLs that matter and prepare redirects for the ones that have to change. Check the forms, the receipt of enquiries and the integrations. Plan a backup and a rollback procedure before the switch.
For a migration from WordPress to Astro, work in this order:
- List the existing pages, posts, media, forms, plugins, roles, languages and redirects.
- Sort each piece of content: keep, rewrite, merge or delete.
- Build a representative page with the chosen CMS, its preview and a form.
- Prepare the redirect plan and check the URLs that receive traffic.
- Run acceptance testing with the people who publish.
- Measure the site after the switch and fix any gaps.
The quote should cover handing over access to the code, the CMS and the hosting, with maintenance responsibilities. The guide to comparing website quotes lists the other items to have spelled out. For a new website, I choose the technology according to how your team will publish; the website creation page sets out the formats and their prices. Before a redesign, get your free audit and tell me how you publish and which features you need to keep.
Frequently asked questions
Is Astro better than WordPress for SEO?
Not automatically. By default, Astro produces light pages prepared in advance; WordPress can get good results with a lean theme and caching. Search rankings depend on content, structure, internal links and how redirects are handled.
Can you keep the WordPress admin with an Astro site?
Yes. WordPress then acts as a headless CMS: Astro reads its content through the REST API. You keep maintaining the WordPress installation, its plugins and its hosting.
Can a non-technical team publish on an Astro site?
Yes, with a headless CMS configured for them. Test the full workflow before you sign: draft, preview, translation, publishing and correction.
Is Astro still free since joining Cloudflare?
Yes. The announcement of 16 January 2026 confirms the MIT licence and compatibility with several hosts. The cost lies in the CMS, the hosting and the development work.


