DEV Community

Cover image for Is WordPress Still a Good Choice for a New Client Site in 2026? Be Honest.
Hannan Shoukat
Hannan Shoukat

Posted on AI-assisted

Is WordPress Still a Good Choice for a New Client Site in 2026? Be Honest.

Here's a number that surprised me. According to W3Techs, WordPress ran 43.0% of all websites on 1 January 2026. Today it's 38.7%. That's after a decade of almost nonstop growth, from 23.3% in 2015.

Shopify, Wix and Squarespace didn't take all of it. Most of the gap shows up in sites W3Techs can't match to any CMS at all, which I read as more custom builds and AI-generated sites. I could be wrong about that.

Either way, it made me ask a question I hadn't asked in a while: if a small business came to me today for a new site, would I still pick WordPress?

Why I'd still say yes, most of the time:

  • The client can edit their own pages without calling me. That still matters more to most owners than anything technical.
  • Hosting is cheap and everywhere, and no single company can raise the price on them.
  • WooCommerce, forms, SEO plugins: almost anything a small business asks for already exists.
  • When I disappear, another developer can pick it up tomorrow.

Why I hesitate more than I used to:

  • Plugin sprawl. A "simple" site with 25 plugins is 25 things that can break or get hacked.
  • Updates are the client's problem until they suddenly become yours.
  • For a five-page brochure site, a static site or a hosted builder is faster and has almost nothing to maintain.
  • Page builders make sites easy to edit and easy to make slow.

Where I've landed for now: WordPress for anything the client will update often or sell through, something lighter for sites that barely change. But I keep changing my mind on the middle ground.

So, be honest:

  • If you build sites for clients, what's your default in 2026, and why?
  • Have you moved a client off WordPress recently? What made you do it, and was it worth it?
  • If you still use it, what's your rule for keeping plugins under control?

I'd especially like to hear from people who switched and regret it, and from people who switched and never looked back.

Top comments (7)

Collapse
 
rushdeploy profile image
Rishabh Mishra •

My default is still WordPress when the client will update content or sell through it, for the same handover reason you gave.
My plugin rule is one plugin per job, no overlaps, and nothing installed that has not been updated in the last six months.
I also put updates and backups in a small monthly care plan, so they stop being the client's problem until something breaks.

Collapse
 
hannanshoukat profile image
Hannan Shoukat •

The six-month rule is a good one, I'm stealing it. It's a simple filter that catches abandoned plugins before they become a security problem. The monthly care plan is the part I think a lot of freelancers skip, and it changes who owns the problem when something breaks. Do clients usually accept it at handover, or do you end up selling it after the first thing goes wrong?

Collapse
 
rushdeploy profile image
Rishabh Mishra •

Most accept it at handover once I frame it as updates and backups, not as a retainer.
I include the first month in the build price, so it feels like part of the site, not an extra.
The ones who decline usually come back after the first update breaks something.

Collapse
 
alexshev profile image
Alex Shev •

WordPress remains a reasonable choice when the ownership model is clear. I’d judge it on update discipline, plugin budget, backup-and-restore testing, editor permissions, and an exit path for content and media—not on whether it is fashionable. A boring site with a maintained core and few well-understood extensions usually beats a custom stack nobody services.

Collapse
 
hannanshoukat profile image
Hannan Shoukat •

"A boring site with a maintained core beats a custom stack nobody services" might be the best one-line answer to the question. The exit path point is underrated too. Most people only think about getting content and media out when they're already leaving. Do you actually test the export at handover, or is it more of a checklist item?

Collapse
 
cwsaad profile image
M Saad •

I think your conclusion makes a lot of sense. WordPress is still a very practical choice when clients need to manage content themselves or have e-commerce requirements. The bigger question is whether the project actually needs everything that comes with a traditional CMS.

Also, hosting plays a bigger role in the overall WordPress experience than people sometimes realize. Options like Cloudways and Kinsta offer managed hosting environments that take some of the server management burden off developers while still allowing them to work with WordPress. Having proper caching, staging environments, backups, and server resources configured correctly can make a noticeable difference.

For plugin management, I'd stick to a simple rule: only install plugins that serve a clear purpose, avoid overlapping functionality, review updates regularly, and test changes on staging before pushing them live.

I also wouldn't automatically move a client away from WordPress just because a static site is technically lighter. If they're actively publishing content, managing products, or relying on integrations, the flexibility can easily outweigh the maintenance overhead.

Ultimately, I'd choose based on the client's workflow rather than whatever technology is trending in 2026.

Collapse
 
hannanshoukat profile image
Hannan Shoukat •

Agreed that hosting is half the WordPress experience. A lot of "WordPress is slow" complaints I hear turn out to be cheap shared hosting plus a heavy page builder. Staging is the one I'd push hardest, since testing updates there catches most breakages before the client ever sees them. And "choose by the client's workflow" is a better rule than mine. Do you set up staging even for small brochure sites, or only once there's a store or regular publishing?