Why We Don't Build on WordPress (Even Though Everyone Asks)

We get the question constantly. “Can you just build it on WordPress? Everyone uses WordPress.”

The short answer is no. The longer answer is the rest of this post — because if you’re a local business owner reading this, the math on WordPress vs. Astro for a small marketing site genuinely doesn’t favor WordPress in 2026, and we want you to understand why.

What WordPress is and isn’t

WordPress powers about 43% of the web. That number is correct and it’s not the gotcha most people think it is.

WordPress is a 22-year-old PHP CMS designed in an era when JavaScript was a sidecar, mobile traffic didn’t exist, and AI crawlers weren’t a category. It does some things well — large publishing platforms, sites with frequent multi-author content, e-commerce via WooCommerce.

For a local business marketing site (5–15 pages, monthly content updates, no e-commerce, no member portals), WordPress is the wrong tool. It’s overengineered, vulnerable, slow by default, and difficult to maintain. We’ve migrated hundreds of these sites over sixteen years; the math is consistent.

The four problems

1. Performance

The median WordPress site loads in 2–5 seconds (Largest Contentful Paint). The median Astro site loads in 0.3–0.9 seconds.

This isn’t because WordPress hosting is bad. It’s structural. WordPress generates pages on-demand from a PHP / MySQL backend with each request. Astro renders pages once at build time and serves static HTML. The static HTML is faster than the dynamic generation, and it’s not close.

Why it matters: Google’s Core Web Vitals are now a confirmed ranking factor. Sites with LCP under 2.5 seconds outrank sites over that threshold all else equal. For a local business, “all else equal” includes your competitors who are also trying to rank in the local pack — and the WordPress sites are losing this race.

2. Vulnerabilities

WordPress and its plugin ecosystem disclosed approximately 11,000 vulnerabilities in 2024, the most recent year with full data. The same data shows about 9,000 in 2023 and 6,500 in 2022. The trend is up.

Astro static sites have zero attack surface. There’s no PHP runtime, no database, no admin login, no plugin API. The site is HTML and CSS files served from a CDN.

This isn’t a paranoia argument. We’ve cleaned up dozens of compromised WordPress sites over the years. The forensic work is annoying. The downtime damages local rankings. The Google “this site may be hacked” warning in search results destroys conversion rates for weeks. None of that happens on a static Astro site.

3. AI-crawler readability

This one’s recent. AI crawlers — GPTBot, ClaudeBot, PerplexityBot, GoogleBot’s AI Overview crawler — read websites differently from traditional search engine crawlers. They prioritize:

• Clean semantic HTML
• Schema.org structured data
• Fast response times
• No JavaScript-rendered content

WordPress sites with heavy theme JavaScript and SEO-plugin-generated schema score poorly on AI-crawler readability — recent third-party analyses peg WordPress at roughly 54% readability vs. 100% on well-built Astro static sites.

In 2026, a non-trivial chunk of “search traffic” is AI crawlers retrieving your content for inclusion in AI Overviews and chat answers. If your site is the WordPress one and your competitor’s is the Astro one, your competitor wins the AI mention. Compounded across dozens of queries, that’s a real volume difference.

4. Maintenance overhead

A WordPress site requires:

• Ongoing core updates (4–6 per year)
• Plugin updates (typically weekly)
• PHP version upgrades (every 1–2 years)
• Theme updates
• Backup management
• Security monitoring
• Hosting cost ($20–100/month minimum for managed WordPress)

An Astro static site requires:

• Nothing.

This isn’t an exaggeration. Once an Astro site is built and deployed to Vercel, it sits there serving HTML files until you change the source. There’s no PHP version to upgrade, no plugins to patch, no hosting cost (Vercel’s free tier handles most local-business traffic).

The maintenance overhead is the hidden cost most WordPress site owners don’t see clearly. It’s bundled into a “monthly maintenance” line item from a developer or agency that runs $50–300/month. That cost evaporates with Astro.

The “yours forever” question

Most clients ask, somewhere in the first month: “if I leave, do I keep the site?”

WordPress: yes, you keep the database export and the theme files and the plugin licenses, and good luck. The site requires a developer to host elsewhere. The handoff is messy.

Astro (us): yes, and the handoff is clean. We export the rendered HTML/CSS as a static folder. You upload it to any free static host (Vercel, Netlify, Cloudflare Pages, GitHub Pages) and your site is live. No developer required for the move. No database to migrate. No PHP version to match.

That’s not a marketing line. It’s in the contract.

When WordPress is actually the right call

To be fair: WordPress is the right tool for some sites.

• Multi-author publishing with editorial workflows, scheduled drafts, complex permissions. WordPress’s admin UI is unmatched here.
• E-commerce at scale via WooCommerce, with hundreds of products and complex variations.
• Membership sites with paid content, course delivery, drip access.
• Sites where the owner explicitly wants to self-edit every paragraph and doesn’t want to bother an agency.

For a local plumber, HVAC company, attorney, dentist, or chiropractor with 5–15 marketing pages and monthly-ish content updates: none of those apply. The right tool is static.

What this looks like in practice

Every WMS client gets an Astro static site:

• 5 pages on Charter, up to 10 on Core, up to 20 on Professional
• Built once, hosted free on Vercel under our infrastructure
• Schema markup correct from day one
• Core Web Vitals 95+ default
• Site updates included in your monthly retainer (you email what to change; we change it)
• Clean export anytime if you ever leave

If you’re on WordPress and curious whether a migration would help your local SEO, request the free audit. We’ll send a one-page report in 48 hours including a Core Web Vitals snapshot and an honest read on whether migrating is worth the effort for your specific situation.

If your WP site is fine, we’ll tell you that too.