Aaron Charlton · November 16, 2026
Why I’m Moving My Websites From WordPress to Astro
Static sites give me less software to maintain, and AI made the rebuild practical. Here’s what I’m changing and how I’m protecting search visibility during the move.

I really like static sites. Mostly because I’m tired of babysitting servers. For the kinds of sites I run, I can publish the same pages as prebuilt files and take WordPress, PHP, and the database out of the public hosting setup. AI made the rebuild fast enough that it was finally worth doing. So I’m moving my own sites to Astro.
Less software to keep patched
A typical WordPress site has a PHP runtime, a database, a login page, and some combination of themes and plugins. Caching can serve many visitors without running WordPress for each request, but the software behind the cache still needs updates.
This fall offered a good example. WordPress 7.1.4 fixed a security flaw in the core upgrade process, and CISA added it to its catalog of known exploited vulnerabilities on November 3, as noted in the Canadian Centre for Cyber Security advisory. If you run WordPress, keep core, plugins, themes, and your PHP version up to date.
On a fully static Astro site, I build the pages ahead of time and deploy HTML, CSS, JavaScript, and images. There’s no public WordPress login, PHP runtime, or database serving those pages. That’s fewer things for me to operate and fewer ways for someone to compromise the public site. I can also serve the files from a CDN, host a modest site cheaply, and use Git to track and roll back changes to content and code.
What AI changed for me
I could have built these sites in Astro before. The question was whether I wanted to spend the time rebuilding templates, moving content, and checking every page. Now I can describe the layout I want and have AI draft the components or help convert content to Markdown. I still review the code and check what the build actually produces. The time savings are enough to make the migration worthwhile.
My setup is Astro, a private GitHub repository, and Cloudflare Pages. The generated pages are ordinary files, so I can move them to another static host. I’d still need to account for anything tied to Cloudflare, such as redirect rules or serverless functions.
What I check before switching
- URLs and search visibility. Keep existing URLs wherever possible. If one has to change, send it to the closest equivalent page with a permanent HTTP redirect, and test the response after launch. I also compare page titles, canonicals, internal links, and the sitemap before switching over.
- Accounts and builds. Protect the accounts that control the domain, DNS, repository, and deployment. I keep the dependency lockfile in Git so builds use a known set of packages, and I review and apply security updates promptly.
- Forms and other features. A static page can display a contact form, but something still has to receive the submission. For a medical practice, I’d keep a general inquiry form separate from anything intended to collect patient information.
- Who edits the site. Markdown and Git work well for me. If staff need to publish or revise pages every day, WordPress’s editor may be worth keeping.
Where I’d still use WordPress
WordPress can still be a good fit for a membership site, a store, or a team that relies on its publishing workflow. For a local service business whose site mostly needs to explain what it does, show where it works, and help customers get in touch, I’d start with static.
I’ll write more about the SEO side of these migrations, especially how I handle titles, canonicals, redirects, and schema in Astro. If you’re considering a move and want a second opinion on what you’ll need to preserve, get in touch.