Why I use WordPress to design client websites comes down to five things: the client owns the whole site and can take it anywhere, there is a plugin for every real business need without a custom build, any developer in the world can maintain it after me, and it scales from a five-page brochure to a shop or a publication without changing platform. I also do not use it for every client, and the second half of this post is about that, because the honest version of “why WordPress” includes the sites where I steer people to Squarespace or Showit instead. If you are choosing a platform for your own site, or trying to understand why a designer recommended one, this is the reasoning from the inside.
Why I use WordPress to design client websites
1. The client owns it
A WordPress site is files and a database on hosting in the client’s name, under a GPL licence. If they stop working with me, fall out with their host, or want a different designer in five years, they export the site and move. Hosted builders let you export content, not the site; the design, the settings and the URL structure stay behind. For a business, the website is an asset, and I would rather build assets than subscriptions. Why WordPress became so popular is mostly this point at scale.
2. Plugins cover the real requirements
Every client project has one requirement that sounds simple and is not: a booking system with deposits, a members’ area, a quote calculator, a shop with B2B pricing, a multilingual site, a directory. On WordPress each of those is a well-maintained plugin with years of edge cases handled. On a hosted builder it is a workaround, an embed, or a no. The essential plugins list is short, but the long tail is what makes the unusual request routine.
3. Anyone can maintain it
I build sites to be handed over, not to keep clients dependent. A WordPress site can be maintained by any of thousands of freelancers and agencies, and the client’s own team can learn the editor in an afternoon; the roles system gives each person the access they need and nothing more. A site on a niche builder or a custom framework is tied to whoever knows it.
4. It grows without a rebuild
The brochure site that adds a blog, then a shop, then a course, stays on the same platform with the same theme. I have watched clients outgrow builders and pay for a migration that a WordPress site would have absorbed as a plugin install.
5. SEO control when it matters
For content-led clients, the speed engineering, schema and technical control described in Squarespace versus WordPress for SEO are real advantages. For a ten-page local site they are unused; for a publisher or a national service business they decide rankings.
What I do differently on WordPress builds
- Few plugins, all from active developers. Six to twelve on a business site. Every plugin is code someone else maintains; fewer is safer and faster.
- A lean theme or a block theme, not a multipurpose theme with 40 demo layouts. Page builders only where the client’s team will genuinely use them.
- Managed or good shared hosting in the client’s own name, with staging and daily backups, chosen before design starts; what hosting WordPress needs sets out the minimum.
- A maintenance plan or a maintenance handover. Every client leaves knowing what maintenance WordPress needs and who will do it; the sites that get hacked are the ones where nobody was asked.
- Documentation. A short guide to editing the pages they will actually edit, recorded as a video at handover.
When I do not use WordPress
| Client | Platform I recommend | Why |
|---|---|---|
| Photographer or creative with a portfolio-led site and no shop | Showit (with a WordPress blog) | Design freedom and a visual editor; the blog stays on WordPress |
| Service business, five to fifteen pages, nobody to maintain it | Squarespace | No updates, no plugins to break; the platform handles security |
| Product shop with standard needs | Shopify | Purpose-built commerce; apps for everything a shop needs |
| Landing page or one-page site with a short life | Squarespace or Framer | Fast to build; ownership matters less for a page that will be retired |
| Client who has told me they will not pay for maintenance | Squarespace | A WordPress site with no maintenance is a liability I will not hand over |
That last row is the important one. WordPress is the right tool when someone will look after it. Choosing the right platform walks through the decision for owners, and custom design versus a theme covers the build depth once WordPress is chosen.
What clients worry about, and what I tell them
| Worry | Answer |
|---|---|
| “WordPress gets hacked” | Unmaintained WordPress gets hacked. Updated core, few plugins, strong logins and backups make it as safe as any platform; the signs of a compromised site are covered in the hacked-site post |
| “It is slow” | Cheap hosting and 30 plugins are slow. Decent hosting, caching and optimised images produce sites faster than any builder |
| “I heard WordPress is dying” | It runs 40 percent of the web; the share is slipping among sites that never suited it. The is-WordPress-dying post has the numbers |
| “It looks complicated” | The editor the client uses is a few screens. The complexity is mine, at build time |
| “Is it more expensive?” | Usually cheaper to run than a builder subscription, with maintenance as the cost that replaces it |
Two of those answers link to posts on this site because the worries deserve more than a line: how to tell if a WordPress site has been hacked and whether WordPress is dying.
The short version
I use WordPress for client websites because it gives the client the most ownership, the widest range of real functionality, the largest pool of people who can maintain it, and room to grow, at a price most businesses can run. I do not use it for clients who need a portfolio-first design, a standard shop, or a site nobody will maintain, and I say so in the first call. If your project is in the first group, WordPress development is what I would propose; if it is in the second, I will tell you which platform fits and build it there.
Frequently asked questions
Because the client owns the site outright, plugins cover almost any business requirement, any developer can maintain it afterwards, it scales from a brochure site to a shop or publication without a platform change, and it gives full SEO control when that matters.
Yes for businesses that need functionality, ownership and room to grow, and that will maintain the site or pay for maintenance. For simple portfolio or brochure sites with no maintainer, a hosted builder is often the better recommendation.
For portfolio-led creative sites (Showit), standard product shops (Shopify), short-lived landing pages, and clients who will not maintain the site or pay for a maintenance plan.
When maintained: updated core and plugins, a small plugin set from active developers, strong logins with two-factor, and backups. Unmaintained WordPress sites are the ones that get hacked.
Usually cheaper to run: hosting costs less than a builder subscription and the software is free. The offset is maintenance, which costs time or a monthly plan.
Only the editor for the pages they update, which takes an afternoon. The setup, plugins and maintenance are the designer’s side and can be handed to any WordPress professional later.
