What Is a CMS? Content Management Systems Explained

What is a CMS?

A CMS is the part of a website that lets you change pages without a developer. This guide explains how it works, which kinds exist and what to check before you pick one.

A CMS, or content management system, is software that lets people create, edit, organise and publish website content without writing code. It keeps content separate from the design, so you can change a page, add a post or update a menu from an admin area. Small sites that rarely change may not need one, but a site you edit yourself usually does.

A CMS, short for content management system, is software that lets people publish, organise, change and remove the content of a website without editing code. Text, images, menus, products and posts are entered through forms and editors, and the system turns them into the pages that visitors see.

The central idea is that content and design are kept apart. The words and pictures are stored in one place and the design is held in templates. When you change a service description, the system places the new text in the same template, so nobody rebuilds the page. When a developer changes the template, every page that uses it changes too.

Most systems share the same set of parts. The table lists them, with what to look for in each.

How a CMS works behind the scenes

Behind the admin area, a CMS keeps your content in a database or in files, and a theme or template layer decides how it appears. When a visitor asks for a page, the system either builds it at that moment from those parts or serves a copy it prepared earlier. Developers call the second approach caching or static generation.

This has practical effects. The way pages are produced affects speed. The software layers underneath need regular updates, which affects security. The way content is stored decides how easily you can move to another system later. Each of these returns in the questions further down.

Do I need a CMS for a small business website?

You need one if you or your staff will change the site yourselves, or if the site holds many similar items such as articles, products, events or team profiles. You may not need one if the site is a handful of pages that change once or twice a year and you are happy to ask a developer for each edit.

Three questions settle it. How often will the content change? Who will make the changes? What does a delay cost when a price, an opening time or a notice must be corrected today? If the answers are often, your own staff and a great deal, a CMS earns its place. If they are rarely, a developer and not much, a simpler build can be easier to keep secure, because there is less software to maintain.

A one-page site or a campaign page often needs no CMS at all. The guide to what a startup website needs first suggests which pages to build before you decide how editable they should be.

Types of CMS

Suppliers use different labels, but most systems fall into one of five types. Where a platform sits in the table affects who hosts the site, who updates it and how easily you can leave.

WordPress is a well-known open-source example of the self-managed type. Other systems exist in every row, and this guide does not rank them, because the right one depends on your needs, your team and your budget.

How to choose a CMS: questions to ask

Choose against the work your team does, not against a list of features. Start with these questions, which a developer or supplier should be able to answer plainly.

Who will edit, and how often?

List the people who will change the site and what they change: text, prices, images, blog posts or product details. Choose a system whose editing screens fit those tasks. A tool that can build any layout may be harder for a busy owner than one with a few fixed templates. Ask to try the editor yourself before you decide.

What kinds of content does the site hold?

Pages are only one kind. A site may also need posts, products, events, staff profiles, case studies or downloads, each with its own fields. Write the list before you compare systems, because a content type the system does not offer can mean extra add-ons or custom development. The website brief guide shows where this list belongs.

Who owns it, and can you leave?

Ask which accounts will be in your name: the domain, the hosting, the admin login and any paid licences. Ask what can be exported, in which format, and what would need rebuilding. The design and the features that came from add-ons usually do, and form entries sometimes do. A system that cannot export your content in a usable form ties you to its supplier.

What does it do for search?

You should be able to set the page title, description, headings, page address and image descriptions on each page, and to redirect an old address to a new one. Google's sitemap documentation says many content management systems create a sitemap for you, and its guidance on titles says that with a CMS you may need to do little technical work beyond writing good ones. Check that this is true of yours, that the sitemap lists only the pages you want found, and that titles can be edited page by page.

How fast will the pages be?

A CMS does not make a site fast or slow by itself. The theme, the add-ons, the images and the hosting do much of that. Look at how the system handles pictures, because web.dev's guidance on images describes plugins and built-in features in content management systems and frameworks that resize images and generate several sizes. Ask to see the speed results of a live site built on the same setup.

How is it kept secure and up to date?

Every system needs updates. Ask who applies them, how often, what happens if an update breaks the site and where backups are kept. A self-managed system with many add-ons has more parts to update. A hosted builder updates itself, but you depend on the supplier's decisions about features and changes.

What will it cost to run?

The first price is only part of it. Running costs come from hosting, paid themes or add-ons, developer time for changes, training and the hours your staff spend editing. Ask every supplier to give the build and the yearly running costs separately, and to say which items renew each year.

Can it grow with you?

Ask how the system would handle a second language, a shop, a members area or a new section. You may not need these now, but it helps to know whether adding one later means an add-on, a rebuild or a move to a different system.

Test a CMS before you commit

Spend some time in a trial or a demo site before you decide. Ask an editor, not the developer, to carry out the tasks your team will do every week: change a heading, replace an image, add a page to the menu, save a draft and publish it, and restore an earlier version. Then log in with a limited role and check that it cannot reach settings it should not.

Look at the result on a phone as well as a computer. Try the admin area with the keyboard alone, because editing tools differ in how accessible they are. If your team gets stuck on a routine task during the trial, it will keep getting stuck after launch.

Mistakes to avoid when choosing a CMS

• Choosing from the look of a demo. Designs can be changed; the editing experience and the ownership terms are harder to change.
• Choosing the most powerful system when a simple one would do. Every extra feature is one more thing to update.
• Letting a supplier hold the domain, the hosting or the only admin login.
• Adding an extension for every small need, until nobody knows which ones the site depends on.
• Having no plan for who writes and updates content after launch.
• Assuming the CMS handles search for you. It provides the fields, but someone still has to write good titles and useful pages.

Choosing a CMS as part of a website project

The choice usually comes early, after the brief and before design. The website development process guide shows where it sits and who makes the decision. Give your developer the list of editors, content types and integrations, and ask for a recommendation with reasons, including what you would give up by choosing it.

Enquiries need a destination too. Decide whether form submissions are emailed, stored in the CMS or sent to another tool, and what the contact page must hold. The guide to what a contact page should include covers the content. The website development service page describes the websites Liftup builds.

Questions and answers

What is a content management system?

A content management system is software that lets you create, edit, organise and publish website content through an admin area instead of writing code. It stores content separately from the design templates, so changing a page does not mean rebuilding it. Many also manage users, drafts, images and menus.

Do I need a CMS for a small business website?

You need one if you or your staff will edit the site often, or if it holds many similar items such as articles or products. A small site that changes once or twice a year can work without one if you are happy to ask a developer for each change. Decide by how often content changes and who will change it.

What should I check before choosing a CMS?

Check who will edit and how easy the editor is, which content types you need, who will own the domain, hosting and admin login, and what you can export if you leave. Also check the search controls, how updates and backups are handled and what it will cost to run each year.

What is the difference between a CMS and a website builder?

A website builder is a hosted tool that bundles a CMS, hosting and design templates into one package. A CMS on its own is the editing and content system, which you can install on hosting that you or your developer choose. Builders are quicker to start but may limit design, features and export, so check those before committing.

What is a headless CMS?

A headless CMS stores and manages content but does not produce the website pages itself. A separately built website or app fetches the content through an interface and displays it. It suits teams that publish the same content in several places, and it needs more developer work than an all-in-one system.

Does my choice of CMS affect SEO?

A CMS does not rank a site by itself. It affects search through the controls it gives you, such as titles, descriptions, headings, addresses, redirects and sitemaps, and through the speed and tidiness of the pages it produces. Check Google's current documentation for what it asks of site owners, and test real pages before you commit.