Do I need WordPress? What a small business website actually needs

I have a confession that is probably bad networking at a web-design conference: I do not think every small business needs WordPress.

That does not mean WordPress is bad. It powers an enormous number of websites and there are businesses for which it is exactly the right choice. I just do not think the platform should be chosen before anybody has asked what the website actually needs to do.

If you are opening a cabinet shop, running a clinic or replacing a ten-year-old contractor website, you should not need a degree in content management systems to make a good decision.

Start with the business, not the platform.

Before choosing WordPress, Wix, Squarespace, a custom build or anything else, I would ask a much duller set of questions:

• Who needs to update the site?
• How often will pages change?
• Do you need a blog?
• Do you sell products or take payments?
• Do customers need to book appointments?
• Are there staff members with different editing roles?
• What systems does the site need to connect to?
• Who owns the domain, hosting and third-party accounts?

Those answers tell us much more than “most websites use WordPress.”

What WordPress is good at.

WordPress makes sense when a business wants a mature content-management system, needs several nontechnical people publishing frequently, already has a well-built WordPress site, or depends on a WordPress-specific integration.

There is also a huge ecosystem of themes, plugins and developers. If your organization already knows that ecosystem and maintains it well, moving away just because a different technology is fashionable would be a strange use of money.

Where WordPress can become heavier than the job.

A six-page local business website may not need a database, page builder, theme framework and a collection of plugins just to display services, photos, contact information and a form.

The problem is rarely WordPress by itself. The problem is accumulation. A plugin gets added for forms. Another handles SEO fields. Another creates a slider. The theme adds its own builder. Years later, nobody remembers why half the pieces are there and everyone is nervous about updating them.

For a simpler business site, I often prefer building only the pieces the business actually needs. Fewer moving parts can mean less maintenance and less mystery.

But I want a blog. Do I need WordPress then?

No. A blog is a type of content, not a WordPress feature.

A custom site can have an article index, categories, images, authors, SEO titles, descriptions and clean URLs. If the owner wants to write posts personally, I can connect a simple browser-based editor so nobody has to touch code. If the owner would rather send me a document, I can format and publish it.

The right publishing setup is the simplest one the person who actually has to use it will keep using.

What about ecommerce?

I do not believe in rebuilding secure payment and inventory machinery just to prove I can. A custom website can provide the design and customer experience while a proven platform such as Stripe or Shopify handles the parts it is specifically built to handle.

For a few products, that might mean Stripe checkout connected to a custom site. For a real catalogue with inventory, variants, shipping and order management, Shopify may sit underneath the storefront. The customer does not need to care which tool handled which layer. They need the experience to work.

Booking works the same way.

If a clinic, consultant or service business already has a booking system, the useful job is usually to integrate it clearly into the site and make the path feel intentional. If they need a new booking system, I can set up a proven service, connect availability and calendars, and make the website hand customers into it cleanly.

Again, the goal is not to custom-code a scheduling engine for sport. The goal is to give the business a reliable booking process it owns and understands.

The ownership question matters more than the logo on the dashboard.

Whatever platform you choose, I want the important accounts in the client's name: the domain, hosting, payment account, store account and booking account. You should know what you are paying for and be able to take the finished site or accounts elsewhere.

A website is too important to a business to depend on one developer remaining reachable forever.

My rule: use the least complicated technology that comfortably does the real job, and use proven specialist tools for the parts where security, payments, inventory or scheduling make specialist software the sensible choice.

So, should you use WordPress?

Maybe. If it fits the business, I have no interest in talking you out of it for philosophical reasons.

But if the only reason is “websites are supposed to be WordPress,” then no. They are not. A professional business website needs to be clear, fast, accessible, secure, maintainable, searchable and owned by the business. There is more than one good way to get there.

Useful reference

Google's SEO Starter Guide is deliberately platform-neutral. The important work is making useful pages accessible and understandable to people and search engines, regardless of the publishing system underneath.