Astro vs WordPress: when to choose each one

For a long time, WordPress was my go-to option for building all kinds of websites, except complex ecommerce sites, where I opted for PrestaShop or Shopify. I even used WordPress with WooCommerce for smaller shops.

For membership sites and corporate websites too. And, of course, for blogs and magazines.

So when I tell you I chose something else for my latest project—a corporate services website—you can be sure it really convinced me.

That doesn't mean I'm going to migrate everything from now on or always use Astro. No.

Just as I use PrestaShop when I think it's a good fit, I'll use Astro for the right projects. And yes, WordPress will stop being my default choice in many cases.

Just because you can build a website with either one doesn't mean they're equally good options.

Astro and WordPress aren't the same kind of tool

WordPress is a CMS, a content management system: it includes an admin area, editing, users, a media library, and a system of themes and plugins. I'm talking about the WordPress software installed on hosting, of course, not WordPress.com's commercial plans.

Astro is a framework for building websites. Editorial management and business services are decided separately.

That's why comparing them makes sense when you're trying to deliver a specific project: if you need to publish articles from a dashboard or manage users, you already know what you need. If none of that is necessary and you can focus on performance and the speed of the public-facing site, the other option is probably simpler.

How each one works behind the scenes

Time for a little technology.

How WordPress generates a page

In a conventional installation, WordPress runs PHP, uses its database, and combines content, a theme, and plugins to generate a response. A page cache can serve a prepared copy for many visits.

This lets you publish changes from the dashboard, but it also means maintaining the application and the infrastructure it uses.

How Astro generates a page

The great thing about Astro is that it can prepare pages before publication or generate them on demand. In the first case you deliver prebuilt files, while features that need processing can be handled by separate services.

Anyway, I explain how it works in more detail in this article about what Astro is.. 

Content management and databases

It's worth understanding where the work will sit: in an integrated system or in separate pieces you'll have to organize.

WordPress and MySQL

WordPress normally uses MySQL or MariaDB to store content, users, and much of its configuration. Media files are usually in the file system or external storage.

A copy of the theme, WordPress core, and its code files is not a copy of the entire website. To restore it you also need the database and the relevant static files.

Astro and its many content sources

With Astro you can store text in project files or retrieve it from a CMS and other services.

I'm focusing here on keeping it in the repository, where you can review content and code together, since, in fact, when generating HTML files, code and content are combined in certain files.

Editing content

Getting down to the actual work, the differences here are substantial.

The advantage of WordPress as a CMS

Imagine your client wants to add a news item, change an image, or schedule an article. WordPress already provides an interface for these tasks, although you'll have to configure permissions and prepare templates.

That reduces dependence on the developer for day-to-day work. Obviously, it doesn't mean anyone can change any part of the design without breaking anything, but it does provide an editorial experience from the outset.

For a project where the team publishes frequently, this advantage may matter more than a technical improvement in page delivery.

What Astro needs to provide a similar editorial experience

With Astro, you can choose how you edit and publish.

You can work with files, add a Git-based CMS, or connect an external content management system.

Not every approach offers the same capabilities for images, revisions, roles, and previews. Before choosing, test a real task and consider whether someone with limited technical knowledge can do it easily.

In any case, the idea is to build websites with Astro that will change very little in the future, apart from occasional updates. Otherwise, choosing Astro over WordPress is just making life more complicated.

Performance

Here's where the tables turn.

Astro's starting point

A lightweight static page has a head start when serving stable content without running an entire application or needing a server-side language during a visit. That makes optimization easier.

How WordPress achieves performance

WordPress can deliver a fast website with suitable hosting, a sensible theme, caching, and a careful selection of plugins and resources.

The thing is, the stack it needs is slower to begin with than Astro's.

JavaScript and frontend

In WordPress, the code that reaches the browser depends largely on the theme, plugins, and anything you embed. You can build a lightweight site or pile up libraries and scripts you barely use.

Be aware that, generally speaking, the more features a theme or installed plugin has, the more JS it accumulates.

Astro makes it easier to decide which parts need code running in the browser. That control can be useful on a services website with few external calls. If you load third-party tools—Google Analytics, for example—the potential extra load will be similar.

If you want to weigh up this point along with its downsides, I cover it in the advantages and disadvantages of Astro..

SEO

Let's look at another key area.

What WordPress makes easier

A lot.

The free versions of plugins such as Yoast or Rank Math give you plenty of options. And you can always pay for more features.

A well-configured plugin can reduce repetitive work.

What Astro lets you control

You can design rules to generate metadata, links between language versions, sitemaps, and structured data from each page's information.

There are integrations that help, but you have to check the result. If a template generates an incorrect canonical URL, you can spread the same error to every page that uses it.

Overall, I'd say this is a bit harder to implement with the framework, especially if you're not an expert, since you're forced to make every decision, whereas WordPress plugins often guide you through the process.

That said, neither WordPress nor Astro ranks well on its own. It depends on your content, internal linking, etc.

Security

Another point for Astro.

WordPress's attack surface

There's PHP code, a database, user access to the admin area and, well, code from themes and plugins—or your own—that has to be maintained and reviewed. That calls for updates, suitable permissions, backups, and protective measures.

There are plenty of potential attack vectors. Even though WordPress is constantly updated, you still need to stay current and follow good practices.

The attack surface of a static Astro site

The public-facing side can consist of files alone, so the possibilities are minimal.

However, email accounts, GitHub, forms, and connected services still need to be checked.

The comparison changes if you use Astro with a complex backend, but as I said, that's not the option I'm considering here.

Plugins versus development and integrations

Suppose your client needs to manage bookings. In WordPress, you can look for a plugin with calendars, notifications, and payments, assess whether it suits the business, and install it if it does.

With Astro, you might need to connect an external service, but depending on the situation it may not be as plug and play as with WordPress, which means more development work..

Of course, as we'll discuss later, AI makes life much easier here.

Forms and backend functionality

Forms are a good example of the previous point, because almost every business website needs one.

In WordPress, a plugin can handle the fields and submissions with appropriate email settings. In Astro, serving HTML makes it more complicated. You can use a specialized service such as the Zoho Mail API or build a backend to process the request, which would complicate things again.

Hosting and deployment

Here they're nothing alike. Despite both being used to build websites for visitors.

WordPress: PHP, MySQL, and a server

A conventional installation needs hosting that runs PHP and provides MySQL or MariaDB. Many providers offer that combination preconfigured, along with installation, backups, and management.

Publishing content from the dashboard is part of normal use.

Code changes deserve their own testing process; just because WordPress lets you modify production directly doesn't make it a good way to work.

Astro: build, Git, and CDN

With a static website, you need to build and host the files. The good thing is that many domain providers already offer enough space to spare you separate hosting.

In a standard workflow, Astro generates a build that you can upload directly to services such as CloudFlare, with or without going through a Git repository to track changes.

It's an incredibly lightweight and agile way to work. And, as I said, much cheaper.

Maintenance and updates

WordPress requires you to maintain the core, themes, plugins, and environment for as long as the site is online.

Astro may need no maintenance at all if the website doesn't need changes.

Yes, absolutely no maintenance.

However, to be fair, more complex projects may require maintaining the framework, dependencies, build process, and integrated services.

Git and version control

In Astro, a project with file-based content lets you review many changes together: code, text, and configuration. This makes it easier to work with small, verifiable changes. In other words, Git fits like a glove here..

WordPress can also use Git for its theme and custom plugins. The trouble is that content and many settings usually live in the database, outside that history.

So reverting to an earlier code version doesn't guarantee you'll recover the website's previous state.

Internationalization

WordPress has plugins for managing languages, translations, and relationships between content. They're useful for a team that needs to edit from the dashboard, although you should check compatibility with content types and the rest of the site.

With Astro you can organize routes and data by language and generate pages from shared structures. There are more decisions to make: what to translate, how to link pages, what to show when a version is missing, and how to publish changes.

As with SEO, there are more decisions to make in Astro; it doesn't hold your hand like the WordPress Polylang plugin. And you can mess it up.

Development with AI

This deserves a section of its own, because it's fundamental.

The thing is, these days and looking at what's coming, learning to use AI to develop all kinds of software is essential. Websites included.

In this case, having used AI on both WordPress and Astro projects, I think it's cleaner to do it with the latter..

Creating a Codex project on your computer, linking it to GitHub and CloudFlare, and starting development with the framework all fits together really well. Before you know it you'll be flying, and the only limit will be the AI tokens your plan allows. That's how it is.

It also works with WordPress, sure, but I find it a bit more tedious: you have to install WordPress locally, , optimize it, use AI to develop code and make database changes, often install plugins manually, and migrate to production, where you will have to repeat some changes manually. Git does not store the database either, which adds another point of friction.

I don't know, I suppose you get used to everything, but building the system with Codex and Astro certainly feels much cleaner to me, as I said.

The real cost of each option

It's hard to make this comparison.

What I can tell you is that for websites that can be built with static HTML, Astro may cost more to develop (more hours) unless you use AI, but it's cheaper to maintain. In both time and money (you save on hosting).

For websites with more features (ecommerce, memberships), I'm sure I'll keep choosing WordPress, given everything involved in development.

Astro vs WordPress comparison table

To sum up, here's a table comparing each point we've discussed for a website that could be built with either system, such as a corporate site. The winner is in bold.

Area	Astro	WordPress
Tool	Development framework	CMS with editorial dashboard
Page generation	Static, on demand, or a combination	Dynamic, with caching available
Content	Files, CMS, APIs, or databases	Database and integrated editorial system
No-code editing	Requires a chosen, integrated solution	Included for standard editorial tasks
Business features	Services and integrations depending on the project	Extensive plugin ecosystem
Performance	Good starting point for lightweight content	Depends on implementation, resources, and hosting
Security	Less public-facing logic in static deployments	Application and extensions must be maintained
SEO	You have to build it yourself	Easier with plugins
Publishing	Build and deployment for prerendered content	Publishing from the dashboard, with cache management
Versioning	Code and file-based content can go together	Code in Git; content usually in a database
Multilingual	Architecture and integration to be designed	Editorial tools via plugins
Development with AI	Easier once the system is set up	A more cumbersome process overall
Cost	More expensive to develop, cheaper to maintain	Depends on development, hosting, and extensions
Maintenance	Dependencies, builds, and services	Core, themes, plugins, and environment

When to choose Astro

I'd choose it for a website with relatively stable content, such as:

• Corporate website.
• Portfolio.
• Documentation.

With clearly defined features and someone who can maintain the publishing workflow (the client or me).

When to choose WordPress

I will still choose it when frequent editing from a dashboard is necessary, when the client needs editorial independence, or when its plugins provide a simpler way to deliver the required features.

Examples:

• Blog or magazine with frequent posts and several authors.
• Small online shop.
• Membership site.
• Corporate website with a blog: I'd build everything with WordPress rather than mix systems.
• Website with constantly changing listings: property agencies, hotel bookings…

The hybrid option: Astro with WordPress as a CMS

I'm mentioning this option so you know it exists and is possible, but it's not one that convinces me. It would have to be a very, very specific project to justify making the systems this complicated.

In that case, you can keep WordPress for editing and retrieve its content through an API to display it with Astro. This is usually called a headless WordPress setup: the content management system operates separately from the public-facing site.

This lets you retain a familiar editorial experience and build a different frontend. But you have to handle previews, publishing, images, and the features that previously depended on the theme or plugins.

A plugin doesn't transfer its behavior to the Astro frontend. A specific integration is usually required.

It's a duplication of systems that needs to be justified.

Conclusion: how I choose between Astro and WordPress

Ultimately, when a new project comes along, these are the questions I need to answer:

1. What content changes are expected, and how frequently? If they're constant, I go with WordPress. If they're very occasional, Astro gains points.
2. Who's going to edit it, and how independently? If the client needs to make changes, WordPress. If I'm making the changes, Astro is an option.
3. What does the website need to do? As mentioned, if it's a corporate site or a website that can be built as HTML pages, Astro. If other features are needed (blog, membership), I'll stick with WordPress.
4. What tools does the business already use? This matters for integration: there may already be a WordPress plugin that makes it simple, whereas Astro might require custom development. That almost always rules Astro out for me, apart from small additions.
5. Who will maintain everything, and how much will it cost? If no changes are needed, Astro is ideal because it does not require maintenance as such. If the website will change or new content will be published, I lean toward WordPress, and we will work out who handles what.

With those answers, I know which route to choose. The important thing is meeting the business's needs as well as possible. Technology comes afterwards..