The content management system (CMS) is the part of your website you live with longest. Designs get refreshed, but the CMS decides who can edit the site, what it connects to, who can look after it and what it costs to walk away. That makes how to choose a CMS a business decision first and a technical one second.
Most advice ranks products. This guide treats the website platform decision as a framework instead: seven questions, a scoring table and the warning signs of a platform chosen for someone else’s convenience. For platform-by-platform detail, see our WordPress vs Wix vs Shopify comparison.
A note on bias: we build on WordPress. The framework is platform-neutral, and it will tell you when WordPress is the wrong choice.
The short answer
Choose the CMS that fits how your team works and where the business is going, not the one with the longest feature list. Judge every option on seven things: who edits, which languages, what it connects to, how it will grow, how it is hosted and maintained, whether another developer could take it over, and what leaving would cost. Weight them, score your shortlist, and treat any failed must-have as a deal-breaker. For most content-led business websites, a mainstream, well-supported CMS beats a niche or bespoke one: more people can maintain it, and it is cheaper to leave.
What a CMS actually decides
A CMS is the software your team uses to create, edit and publish pages without writing code. It sits between the hosting and the design, one of the layers in our plain-English guide to how websites are built. Most options fall into five families:
| Type | How it works | Usually suits | Main trade-off |
|---|---|---|---|
| Hosted website builder | One subscription covers software and hosting (Wix, Squarespace) | Simple sites the owner edits | Hard to move away from |
| Open-source CMS | Free software on hosting you choose (WordPress, Drupal) | Content-rich sites that will grow | You handle updates and security |
| Hosted e-commerce platform | A hosted store with page editing (Shopify) | Product-led businesses | Costs grow with apps and payment fees |
| Headless CMS | Content sent through an API to a separately built front end | Content reused across channels | More moving parts |
| Bespoke CMS | Written from scratch by one developer or supplier | Very specific needs | Often only its makers can maintain it |
A CMS won’t make a site fast, findable or persuasive on its own. It sets the ceiling; strategy, design, content and build quality decide how close you get.
If customers will sign in to work with their own data, you may need more than a CMS: our guide to website vs web application helps you tell which you are building.
How to choose a CMS, one question at a time
These are the CMS selection criteria that matter over a website’s life. Answer them in writing before you watch a single demo.
1. Who will edit the site, and how often?
A marketing team publishing project pages every week needs something very different from an owner who changes opening hours twice a year.
What to look for. Structured fields for repeated content, such as a project or product, so editors fill in a form rather than design a page. Roles and permissions if several people edit. Revision history, so mistakes can be undone.
Check it yourself. Ask for a demo loaded with your own content, and have your real editor add a news item, swap a photo and change a price. Note every question they ask. Freedom to drag anything anywhere isn’t a virtue: it is how sites drift off-brand and break on phones.
2. How many languages, now and later?
If customers use more than one language, each needs its own page addresses, translated titles and descriptions, menus and forms, plus hreflang annotations that tell Google which version to show to whom. A translate button that swaps text in the browser does none of this.
What to look for. Built-in multilingual support or a mature add-on, translatable URLs and SEO fields per language, and a way for translators to work without touching the design. Ask whether adding a language later is a settings change or a rebuild. Our guide to planning a multilingual website covers the decisions that come first.
3. What must it connect to?
List every system the site should talk to: CRM, email marketing, bookings, analytics, a product database, payments, messaging apps. Each is either a maintained, ready-made integration or custom code someone must build and keep working.
What to look for. Well-supported integrations for the tools you use now, an API or webhooks for later, and form submissions you can export. Our guide to website integrations explains the options. Distrust any add-on nobody has updated in a year.
4. How will the site need to grow?
A scalable website platform is less about the brand than whether the CMS can model your content cleanly as it multiplies. Think three years ahead: more projects, products or locations? More editors, a second brand, online sales?
What to look for. Custom content types with their own fields, templates and listing pages, so fifty projects stay as tidy as five, and a clear upgrade path rather than a “contact sales” wall. Pay for room to grow, not for enterprise features you may never use.
5. Where will it be hosted, and who keeps it fast and secure?
On a hosted platform, the provider runs the servers, applies security updates and largely decides how fast pages can be. With a self-hosted CMS, you choose the hosting and someone on your side keeps the software updated.
What to look for. Control over caching, image sizes and the code each page loads, backups you have tested restoring, and a named person responsible for updates.
Check it yourself. Google’s Core Web Vitals count as good when, at the 75th percentile of real visits, Largest Contentful Paint is 2.5 seconds or less, Interaction to Next Paint 200 milliseconds or less and Cumulative Layout Shift 0.1 or less. The HTTP Archive’s Core Web Vitals Technology Report shows what share of real sites on each platform pass. Treat that as typical, not a limit: build quality and hosting matter as much as the CMS, as our guide to hosting for a fast website explains.
6. Could another developer take it over?
Developers move on and suppliers change. The question isn’t whether your current developer is good, but whether the next one could pick up the work.
What to look for. A mainstream CMS with a large pool of people who know it, custom code documented and kept in version control you can access, the domain, hosting and premium licences registered to your company, and administrator logins in your name.
Check it yourself. Ask: “If you disappeared tomorrow, who else could maintain this, and what would they need?” A good developer answers without flinching.
7. What would it cost to leave?
Every platform has website exit costs. What differs is their size, and whether you see them upfront.
- Content. Can you export everything, including custom fields and media, in a standard format?
- Design. Templates almost never move between platforms. Assume a new front end.
- Addresses. Can you control URLs and set redirects? Every address that changes in a move needs one, or rankings can slip, as our website migration SEO checklist explains.
- Contracts. Minimum terms, licences that stop working when a subscription ends, and data a provider keeps after you cancel.
Check it yourself. Before signing, ask for a sample export and see what actually comes out.
Score your shortlist
A weighted score turns opinions into a decision you can explain to colleagues.
- Weight each of the seven criteria from 1 (nice to have) to 3 (critical).
- Score each option from 1 (poor fit) to 5 (excellent fit) on every criterion.
- Multiply weight by score and add up each column.
- Check for deal-breakers: a score of 1 on any criterion weighted 3 rules that option out, whatever the total.
Take a hypothetical manufacturer whose marketing team updates pages weekly in three languages, sends enquiries to a CRM and won’t sell online. The scores are judgements for that scenario, not product ratings.
| Criterion | Weight | Hosted builder | Open-source CMS | Headless CMS |
|---|---|---|---|---|
| Editing for your team | 3 | 5 (15) | 4 (12) | 3 (9) |
| Languages | 3 | 3 (9) | 4 (12) | 4 (12) |
| Integrations | 2 | 3 (6) | 4 (8) | 5 (10) |
| Growth and content types | 2 | 2 (4) | 4 (8) | 5 (10) |
| Hosting, speed and security | 2 | 4 (8) | 3 (6) | 4 (8) |
| Handover to another developer | 2 | 4 (8) | 5 (10) | 2 (4) |
| Cost of leaving | 3 | 2 (6) | 5 (15) | 3 (9) |
| Total (out of 85) | 56 | 71 | 62 |
Change the business and the answer changes. A consultant with a five-page site edited twice a year would weight growth and integrations at 1, and the builder could easily win. A company publishing the same content to a website, an app and in-store screens would push them to 3, and headless starts to earn its complexity (see what a headless CMS is).
Cost is deliberately not a row: compare three-year running costs once you know which options fit, so a cheap platform that fails a must-have can’t win on price. If two options finish within a few points, pick the one that is cheaper to leave.
Warning signs a platform suits the developer more than you
Specialising in one platform is normal. The warning sign is a recommendation that can’t explain itself in terms of your business. Be wary if:
- Only they can maintain it. A bespoke CMS, or a set-up so customised no other developer would recognise it.
- They can’t say when it would be the wrong choice. Every platform has a weak spot. If they can’t name it, they haven’t weighed it.
- The stack is bigger than the job. A headless build or a brand-new framework for a ten-page company site serves the developer’s curiosity more than your business.
- Simple edits need them. If changing a photo means a support ticket, the site was set up for the builder, not the editor.
- Exit questions get vague answers. “You’ll never need to leave” is not an export plan.
Our questions to ask before hiring a web designer cover ownership and handover in more depth.
Frequently asked questions
What is the best CMS for a business website?
No single CMS is best for every business, only the best fit. Builders suit simple owner-run sites, Shopify suits product-led stores, open-source platforms such as WordPress suit content-rich, multilingual sites that will grow, and headless suits content shared across many channels.
Should our developer choose the CMS for us?
Their view matters: they know what each platform is like to build on and maintain. But agree the criteria and weights inside your business first, then ask them to score the options with you and justify each score.
Is WordPress still a sensible choice in 2026?
For many business websites, yes. At the time of writing (July 2026), W3Techs’ usage surveys show it as the most widely used CMS by a wide margin, so experienced developers are easy to find if you ever change supplier. The trade-off: updates, backups and security need an owner, whether your team or a care plan.
What to do next
Write down your answers to the seven questions before you talk to anyone selling a platform, including us. They become your brief, shortlist filter and scoring sheet, and make it much harder to be sold the wrong thing.
If WordPress scores well, our website design and development service plans the build around these same questions, with the domain, hosting and full admin access in your name, plus editor training. Replacing an existing site? A website redesign keeps what works and redirects every old URL.
Not sure the platform is really the problem? A free website audit of your current site’s speed, security and search visibility often shows whether the problem is the CMS itself or how the site was built and looked after.