Atelier tile — Type with gold-dot period, Light palette — for the WordPress-to-Astro migration post.

A client called me last month. Her WordPress site had gone down again. Some plugin had updated overnight, conflicted with another plugin, and the contact form stopped working. She’d lost a week of leads before she noticed.

She didn’t want to hear a lecture about caching, or staging environments, or whether she should switch hosts. She wanted to know: is there a version of this where I just have a website, and it just works?

The answer in 2026 is yes. And more and more, the path looks like this: WordPress to Astro. Not because WordPress is broken — it’s still powering more of the web than every other CMS combined. But because for a small business owner who isn’t running a content factory, the math has shifted.

Here’s what that move actually looks like, and what we use instead.

WordPress isn’t dying. But it’s not the default anymore.

WordPress topped out in mid-2025 at a 43.6% share of the web, and the W3Techs numbers have been drifting down since — about 42.2% as of this spring. That’s the first real dip after years of steady growth. Not a collapse. But not the always-up trajectory it had for fifteen years either.

The other number that surprised me: by WordPress.org’s own stats, more than ten percent of WordPress sites haven’t been touched since 2022. So the real, active market share is lower than the headline. And on the other side, Astro is now hitting 2.5 million downloads a week — roughly double where it was a year ago.

If you ask me, none of that means WordPress is going away. It means it’s stopped being the obvious answer. For a small business in 2026 — five to fifteen pages, a contact form, maybe a blog, a need to actually rank locally — the obvious answer has changed.

If you’re still working through whether to switch at all, our hand-coded vs WordPress comparison covers that decision in detail. This post is for the next question down: once you’ve decided you’re leaving, where do you go?

What we move clients to: Astro plus a visual editor

Two pieces. That’s the whole stack.

Astro is the framework that builds the actual site. Pages load in under a second. No database to query, no plugins to update, no PHP to patch. The site is just files — fast files, served from a CDN, the same way Netflix serves its homepage.

Astro is also no longer a scrappy underdog. Cloudflare acquired the Astro team in January 2026, and the framework stays open source under MIT license. For a small business owner, that matters in a boring but important way: the framework your website runs on is now backed by a $30B+ infrastructure company. It’s not going anywhere.

A visual editor is what lets the client edit the site without calling me. This is the part most “just switch to Astro” advice glosses over, and it’s the part that actually decides whether the migration works for a non-developer. WordPress’s killer feature was never the CMS architecture — it was the admin panel. Click a heading, change a heading. Add an image, drag-and-drop. Publish.

The good news is you can have that experience on Astro now. You just have to pick the right editor. Which brings us to the part of the conversation everyone’s having right now.

Why not EmDash? (the option you’re seeing everywhere)

If you’ve been reading anything about Astro in the last month, you’ve heard about EmDash. Cloudflare launched it on April 1, 2026, and they’re calling it the “spiritual successor to WordPress”. It runs on Astro. It has a WordPress-style admin panel. It solves the WordPress plugin security problem in a genuinely clever way.

I’ve looked at it carefully. And in a year or two, after some bugs get ironed out and real-world feedback comes in, I might recommend it. But for the small business clients I’m building for right now, I’d advise against it. EmDash isn’t ready for prime time.

Here’s the honest read:

  • It’s a v0.1.0 preview. That’s not a marketing label — that’s the actual version number. It is currently an early developer Beta release, which means it generally should not be used for a production site.
  • The flagship security feature only works on Cloudflare. Sandboxed plugins — the headline differentiator — “runs best on Cloudflare, but it’s not locked to it.” When self-hosting, there is currently no support for sandboxed plugins.
  • The WordPress migration tool only moves content. Not plugins. Not themes. Most WordPress sites make extensive use of plugins and themes, coded in PHP. If you’ve spent five years building your WordPress site around specific plugins, EmDash imports the words, not the functionality.
  • There’s no point-and-click website builder yet. EmDash has an admin panel, but the kind of visual page-building experience small business owners expect — drag a hero, drop a testimonial — isn’t there.

This isn’t me being a hater. Search Engine Journal, the same publication that wrote the “WordPress is losing market share to Astro” piece, published a follow-up called 6 Reasons Why Cloudflare’s EmDash Can’t Compete With WordPress. Their conclusion: hopefully someday it will be a viable competitor, but EmDash isn’t that today.

I’ll add one piece of nuance. Joost de Valk — the founder of Yoast SEO — wrote a piece on launch day saying he’s planning to develop “on and with EmDash.” He thinks it’s the most interesting thing to happen to content management in years. Honestly, his case is well-made and he might be right long-term.

But Joost is building for himself. He’s a developer. He can rebuild a theme in an evening. The clients I’m building for can’t. They need to publish a blog post on Tuesday and have it just work. That’s a different job, and EmDash isn’t ready to do it yet.

Why CloudCannon (and why now)

The practical answer for small business sites today is CloudCannon.

CloudCannon is a Git-based visual editor for static sites. Editors click on the page they want to change, change it, and publish. Just like WordPress. The difference is the content lives in your code repository, version-controlled, with no database to maintain and no plugins to break.

It works specifically well with Astro because CloudCannon became an official Astro CMS partner in March 2026, with deeper technical collaboration and an integration guide built directly with the Astro core team. They also released an Astro Component Starter in March — 30+ pre-configured Astro components ready for visual editing, which means I can stand a new client site up faster.

The pricing is genuinely workable for small businesses. The Standard plan is $49/mo paid annually or $55/mo paid monthly, with three users and unlimited sites. There’s a Lite plan for Partner Program members at $10/mo per client site, which is what I use to deliver. The total cost of an Astro + CloudCannon site, including hosting, is comparable to a managed WordPress plan — and you don’t pay the plugin tax.

The other thing I like about CloudCannon: it’s what we use now. Not a bet on what might be ready in eighteen months. Today, today’s clients, today’s launches.

Want a sanity check on whether your existing site is a good migration candidate — and what the move would actually cost you? That’s what the audit at the bottom of this post is for.

How a WordPress to Astro migration actually works

The mechanics are less scary than they sound. Here’s how it goes for a typical small business site.

What gets migrated: all your content (pages, posts, images, copy), your URL structure (so Google doesn’t lose you), your forms, your branding. The new site looks like the old site, only faster — or it looks like a redesign, depending on what you want.

What gets rebuilt: templates and layouts (we write clean Astro components instead of inheriting whatever your old theme was doing). Forms move from PHP to a static-friendly handler — usually Netlify Forms or a similar service. Search, if you had it, gets a different solution. Anything that depended on a specific WordPress plugin gets evaluated: do you actually need it, or was it just there?

How long it takes: typical small business site, two to four weeks from kickoff to launch. More complex sites (lots of custom post types, e-commerce, membership areas) take longer. We give you a real timeline at the start, not a marketing one.

Will I lose my Google rankings? This is the question every owner asks, and the honest answer is: not if the migration is done right. The whole point of redirects is to tell Google “this content moved here, follow me.” A properly handled migration — clean redirects, preserved URL structure, faster load times — tends to help rankings, not hurt them.

If you want the fuller technical walkthrough of the migration steps, our hand-coded vs WordPress post covers that in more detail.

A migration I’ve run on my own site

Les Français de San Diego is a community I run. It was on WordPress — slow, hard to update, and no longer reflecting what the community had become. I migrated it to Astro. The new site is faster, cleaner, and I can update it through a visual editor without touching the codebase every time.

That’s not a client story. It’s something I’ve lived. A real San Diego organization, a real WordPress site, a real Astro replacement that’s been running in production. The case study walks through what the finished product looks like.

When WordPress is still the right call

I want to be honest about where WordPress still wins, because the goal here isn’t to talk you out of WordPress for the sake of it.

You probably want to stay on WordPress if:

  • You run a serious WooCommerce store with hundreds of products and complex order flows. WooCommerce’s ecosystem is unmatched.
  • You sell paid memberships, gated content, or subscriptions where the membership plugin is doing real work.
  • You have multiple non-technical authors publishing several times a week, and the WP editorial workflow is something your team is already trained on.
  • You have a specific WordPress plugin that does something irreplaceable and you don’t want to rebuild that functionality.

If any of those are true, the migration math changes. You’d be giving up real value to gain speed and lower maintenance, and that’s not always a trade worth making. Stay on WordPress. Hire someone good to maintain it. That’s a fine answer.

For everyone else — the brochure-and-blog small business sites, the local service businesses, the coaches and consultants and bilingual brands — the migration math is starting to favor a move.

Thinking about leaving WordPress?

If your WordPress site feels slow, expensive, or hard to update, here’s the simplest next step: I record a short personalized video — about ten minutes — looking at exactly what’s holding your current site back, and what an Astro + CloudCannon migration would actually mean for your business.

No sales call. No pressure. Three spots a week.

Apply for a Free Website Audit →

If you’d rather skip the audit and see what a build with us looks like, our pricing and plans are here. Or call me directly at (619) 259-0530.

WordPress had a great twenty years. Astro plus CloudCannon is the next twenty for the kind of small business websites I build. That’s the bet, and the case studies are starting to back it up.