WordPress or Astro? What I Actually Recommend to Clients

I get asked this a lot, usually by someone who’s already half-decided based on a YouTube video. The honest answer is that the “better” platform question is the wrong question. The right one is: who’s going to touch this site after I’m done, and how often?

WordPress wins when the client needs to drive

If a business owner wants to log in and change a headline, add a blog post, or swap out a photo without calling me first, WordPress is the right call every time. It was built for exactly that, and pretending otherwise to chase a technically “cleaner” stack just creates a client who’s stuck waiting on me for updates a $10 plugin or the built-in editor could have handled. Ownership after launch matters more than what’s under the hood.

Astro wins when speed and control matter more than a dashboard

For sites where content changes rarely — a portfolio, a service business with a handful of static pages, a project like this one — Astro produces a site that loads faster, has fewer moving parts to secure and update, and gives me tighter control over the exact SEO structure I want, page by page. There’s no plugin bloat, no database to keep patched, no monthly hosting bill inflated by WordPress’s overhead. The tradeoff is real, though: editing content usually means a code change, not a dashboard login.

The mistake I see most: picking Astro (or any static-site tool) for a client who needs to self-edit

This is the one I actively talk people out of. A fast, modern stack is worth nothing if the business owner can’t add their own testimonials or update pricing without emailing a developer every time. I built Kayship’s site on infrastructure the client could actually maintain, because a dispatch business updating routes and coverage regularly needed that far more than it needed shaving a few hundred milliseconds off load time.

The mistake on the other side: WordPress for a site that never changes

The opposite mistake happens too — paying for WordPress hosting, security updates, and plugin maintenance indefinitely for a site that will get edited twice a year. That’s ongoing cost and ongoing risk (WordPress sites are a much bigger target for automated attacks) for a convenience nobody’s using.

How I actually decide

I ask one question before anything else: after launch, who’s opening this site to make a change, and how comfortable are they with code? The answer points at the platform. Everything else — themes, plugins, frameworks, hosting — gets figured out after that, not before.