Sites that don't need WordPress shouldn't keep it

If your site is a handful of pages that change a few times a year, it doesn’t need WordPress, and keeping it costs you more than you think.

Every plugin is a door

A typical small business WordPress site has a theme, a page builder, a contact form plugin, an SEO plugin, a backup plugin, a security plugin to watch the others, and a few more someone added years ago. Each one is code written by a different company, updated on its own schedule. Each one can break when another updates. Each one is a way in if it falls behind.

That’s why WordPress sites need someone logging in every week to click update, and why the ones nobody logs in to are the ones that get hacked. The owner didn’t do anything wrong. They just ran software that needs a caretaker, for a site that mostly doesn’t change.

What a static site changes

When I move a site off WordPress, it gets rebuilt on Astro and hosted on Cloudflare. Astro turns the site into plain files ahead of time. Cloudflare serves those files from its network. There’s no database behind the page and no admin login on the public site.

For an owner, that changes four things:

• Nothing to update. No plugins, no core updates, no theme updates. The site you launch keeps working without a weekly patch.
• Much less to attack. There’s no login page for a bot to guess at and no plugin to exploit. A file on a network is a small target.
• Fast everywhere. The pages are ready before anyone asks for them, and Cloudflare serves them from close to the visitor.
• You own the files. The site is a folder of code in a repository, on your own domain. It isn’t locked inside a builder or a hosting company’s control panel.

Nothing about the move has to break what already works. Every old link gets a redirect to its new home, so Google and anyone with a bookmark still land in the right place.

What you give up

A WordPress dashboard lets anyone with a login change a page on a Tuesday afternoon. A static site doesn’t work that way. Changes go through whoever looks after the site. For most of the owners I work with, that’s a relief, because they were never editing the site anyway. The small fixes are part of a care plan.

When WordPress is still right

Some sites should stay on WordPress, and I’ll say so.

• A real editorial team. If several people publish every week and need drafts, roles and scheduling, WordPress was built for that job.
• A store that depends on it. A WooCommerce shop with years of orders, customers and extensions wired into how the business runs isn’t a quick move. Sometimes the right answer is to leave it and look after it well.

If neither of those is you, the question is simple. You’re paying, in time or in risk, to keep software running that your site doesn’t use.

What the move looks like

I audit the old site, rebuild it on Astro and Cloudflare, set a redirect for every old link, launch, and look after it for the first month. If you’re on Wix, Squarespace, GoDaddy or Weebly instead, the move is the same idea with a different starting point.