In 15 Years, Almost None of My Clients Ever Edited Their Own Website

Maybe you don't need WordPress.

By Phil Smith8 min readGet each post by email

I’ve built about 100 websites for clients over the last 15 years, most of them on WordPress. How many of those clients ever logged in and edited their own site? I could count them on one hand.

About 100 client websites, and how many owners ever edited their own A grid of 100 dots, one for each client website. Only five are highlighted, for the owners who ever logged in and edited their own site. Owners who ever edited their own site
About 100 client sites in 15 years. I could count the owners who edited theirs on one hand.

That matters, because editing your own site is one of the two big reasons people choose WordPress. The other is plugins: need a feature, install a plugin. For years, that pitch made sense.

WordPress isn’t going anywhere soon. It runs about 39% of all websites, and most of the sites I host still run on it. But I think the ground under both of those promises is shifting. I’ve started moving some clients to Astro, a framework for building fast, content-driven websites, and I’m building new sites with it.

You don’t need to do anything about it today. I just think it’s worth starting to look at your website differently, before someone pitches you your next redesign.

The Feature Most Clients Never Used

Here’s what I actually saw. Clients paid for the ability to edit their own site and almost never used it. They’re busy running their businesses. When something needed to change, they called me.

There’s nothing wrong with that. Your time is better spent on your customers than on learning a website dashboard. But it raises a fair question: why build your whole website around a feature you’re not going to use?

The Login Was the Real Risk

When someone did log in, it often wasn’t the client. And I think I’ve seen it all.

  • The helpful employee. A client let an employee install a plugin so their contact form could accept file attachments. That form turned out to be insecure. Hackers used it to upload malicious code, which installed malware and brought a swarm of foreign bot traffic with it. The client paid to have the malware removed, then paid for extra security and firewalls to hold back the bot traffic, which kept coming for years.
  • The SEO company. I’ve had clients hire SEO companies that butchered their sites: pages that worked great for search crawlers and terribly for real people. One of them even wrote articles about the client’s competitors, on the client’s own website, linking to them and promoting them.
  • The full-size photos. Some clients do edit their own sites. One kept uploading full-size 30 MB photos straight from the camera into a gallery. The site ballooned to 20 to 30 GB, slowed to a crawl, and dragged down the other sites sharing that server.

The same openness that makes WordPress easy to change makes it easy to damage.

WordPress Made My Life Easier, Not Always My Clients’

WordPress was great for people like me. I could do a lot more without writing as much code. For my clients, the benefit was mostly indirect: it probably saved them some money on my time.

There was a trade-off. To do more with less code, most WordPress sites ended up depending on bloated plugins. Every plugin is someone else’s code running on your website. That makes every plugin another security risk, and every one of them has to be kept up to date.

That’s where most of the risk lives now. Patchstack counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, and 91% of them were in plugins. WordPress itself had six.

Where WordPress security holes were found in 2025 Of 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 91 percent were in plugins. WordPress itself had six. 91% of new WordPress security holes in 2025 were in plugins 11,334 found in all WordPress itself: 6
Source: Patchstack, State of WordPress Security in 2026.

Plugins Decide What Gets Built

Looking back, I never needed a giant plugin library. I never advocated for one, either. My philosophy has always been minimal: the fewest plugins, the fewest moving parts. But on WordPress, even a lean site still runs on plugins someone else wrote.

And a plugin-based system is self-limiting. WordPress designers and developers, me included, make decisions based on what plugins exist and what they make possible. That limits the websites we can design to what the community already supports.

Even when there’s a niche plugin that fills exactly the need a site has, it often isn’t widely used enough to feel safe running on a live business website. So you settle for a popular plugin that does 80% of what you want and comes with a pile of things you don’t.

What your business needs versus what a plugin does Two overlapping circles. One is what your business needs, the other is what the plugin does. They overlap on most of it, the part the plugin covers. The rest of what you need is left uncovered, and the plugin brings extras you didn’t want. What your business needs What the plugin does Covered What youstill need Extras youdidn’t want
“Close enough” is the usual compromise. The plugin covers most of it, misses some of it, and brings code you didn’t ask for.

What’s Changing

The plugin library was WordPress’s biggest advantage, because custom code used to be slow and expensive. Now the code is getting much easier to write. That advantage starts to shrink, and the trade-offs that came with it (the bloat, the updates, the security risk) start to look a lot less worth it.

All I ever needed was to explain what I wanted in plain English, get help writing the code I couldn’t write myself, and make better websites. That’s possible now.

I build with Claude Code, an AI tool that writes code from plain-English instructions. I still make every decision about strategy, design and what the business needs. But instead of hunting for a plugin, I can describe the exact feature and have it built for that one site.

That only works because I know what I’m looking at. I direct and manage the work like a lead engineer, and Claude fills the gaps the way specialists would. That’s what lets me build the features I actually want. I don’t guess at what Claude can do or what’s possible. I know what’s possible, because I understand websites, servers and the tech stacks that power them.

That’s why it feels like a superpower. Not because I type “make me an event calendar” and trust whatever comes back without understanding it. That’s vibe coding, and it’s a different thing.

It also means truly custom websites. A plugin only does what its developer decided it should do, and it has to work on thousands of other sites at the same time. When the code is written for your site, the design, the features and how they fit together can all be built around your business. The site you’re reading this on has a contact form, scheduled posts and share images that were each built for it, not installed.

The rest of the industry is moving too. In January 2026, Cloudflare, a major internet infrastructure company, brought in the team behind Astro. Astro stays open source and can still be hosted elsewhere.

What I’m Seeing So Far

The sites I’ve moved from WordPress to Astro all score near 100 on Google’s PageSpeed tests, and they’ve done much better in organic search (the unpaid results), partly because they’re faster and partly because I can build in much more of the behind-the-scenes detail that Google and AI tools read.

The bigger difference is having less that can go wrong. These sites are static, meaning every page is built ahead of time and simply handed to visitors. No plugins, no bloat, and no WordPress login page for bots to hammer at all day. That’s far less to attack and far less to maintain.

What sits between a visitor and your site On a typical WordPress site, a visitor's request passes through a server that builds the page, WordPress, a theme, several plugins and a database, with a login page open to the internet. On a static Astro site, the visitor gets a finished page. Forms and extras run separately, built for that one site. Typical WordPress Static Astro Visitor Visitor Server builds the pageWordPressThemePluginPluginPluginDatabase Login page, open to the web Finished page Forms and extras runseparately, built forthat one site.
Everything in the left column has to be updated and watched. That’s the difference.

What a Move Could Look Like for You

If your site moves off WordPress someday, whether I build it or someone else does, a few things will probably feel different.

Your website on WordPress versus after a move Changes: on typical WordPress you log in or call someone; after a move you ask whoever runs your site. Features: a plugin that’s close, versus built for your site. Upkeep: plugins to keep updated, versus far less to maintain. Security: a login page bots attack, versus no login page to attack. Ownership: many people with keys, versus fewer keys, in your name. Whoever builds it, make sure the accounts are in your name, you’re an owner, the code is in a repository and the build notes are kept with it. Typical WordPress After a move CHANGESFEATURESUPKEEPSECURITYOWNERSHIP Log in, or call someoneA plugin that’s closePlugins to keep updatedA login page bots attackMany people with keys Ask whoever runs itBuilt for your siteFar less to maintainNo login page to attackFewer keys, in your name Whoever builds it, make sure: Accounts in your nameYou as an ownerCode in a repositoryBuild notes kept with it
The whole move in one view. The details are below.
  • Changes. You’d do what most owners already do: ask whoever runs your site. My clients text me changes, sometimes almost every day, and most are live almost right away, because everything about each site is documented in my own AI system: how it’s built, how the business talks, what’s been done before. (I don’t promise turnaround times. It’s one person, not a team.) If your team really does want to edit things themselves, that can still be built in.
  • Features. Instead of shopping for a plugin, you describe what you need, and it gets built for your site. The contact form on this site is an example: it emails me, keeps a backup copy of every message and screens out spam, with no plugin involved.
  • Reliability. It’s fair to ask whether a site built with AI can be trusted. Only if someone who knows what right looks like is checking it. I review what gets built, and it isn’t done until it works on a phone, in Google, in a shared link and a week later.
  • Ownership. This one matters most. Fewer people with keys to your site shouldn’t mean you’re stuck with one person. The accounts should be in your name, with you as an owner and your developer as an admin, and the code should live in a repository (a secure online home for the code that keeps every past version) with the build notes documented right alongside it. That’s how I set mine up, and I’d ask any developer for the same.

Here’s the honest part: this is a frontier. Everyone in the industry is learning it right now, so how easily the next developer can pick up someone else’s work will vary. That’s how it always goes when the technology shifts. What shouldn’t change is that the accounts, the code and the site are yours.

Who Should Stay on WordPress

WordPress is still a good choice for a lot of businesses. If your team is in the site every week publishing content, or your site depends on tools built specifically for WordPress, it may be exactly the right fit. Most of the sites I host are still on it, and many of them should stay there.

Make the Code the Easy Part

Platforms change. I’ve built on several over the years, and I’ll probably build on more. The job stays the same: protect the investment you’ve made in your website, and build what serves your business and your customers.

After years of WordPress, I think it’s time to get business owners focused on running their business again, not on the bells and whistles.

Let’s make the coding the easy part, and put the real work into the business: the strategy, getting results and measuring them.

So before your next redesign, ask yourself one question: when was the last time you logged in to your own website?

If you're on WordPress and wondering what this shift could mean for your site, I'm happy to talk it through. Let's talk.

Get the next one in your inbox.

The new post every Tuesday morning, the hour it goes live. Building with AI and calling out the hype, from someone who does the work.

One email a week, no spam, unsubscribe anytime. Privacy

Check your inbox.

I just sent you a confirm link from phil@news.flipcreative.io. Click it and you're in. Nothing there in a few minutes? Check spam or promotions.

More from Beyond the Tactics