A content management system, or CMS, is software for creating, organising and publishing content. It usually gives authorised staff an editing interface for routine changes, without rewriting the site's code. Whether you need one depends on your content, people and update process, not page count.
For the bigger picture, see our small business website guide.
What does CMS mean and what does it manage?
The definition is simple. The useful part is what it lets your team do.
Typical routine tasks include:
updating opening hours
correcting a service description
publishing an article
replacing an approved team photo
retiring an expired offer
What a given person can actually do depends on their permissions and how the site was built. Routine editing can avoid touching code, but setup and supported tasks depend on the build.
A CMS often sits beside other systems with similar sounding jobs:
Term | Plain language meaning |
|---|---|
CMS | Manages content and the process for publishing it |
Website builder | Helps construct pages or layouts, often alongside a CMS |
CRM | Manages customer or prospect records and relationships |
Hosting | Runs or serves the website or application |
Domain | The registered name people use to reach a service |
Theme or template | Defines how content is displayed within the chosen system |
Products often bundle several of these. A form can pass details from the website to a CRM. That doesn't make the CMS and CRM the same thing. Content held in an outside booking or store service may need editing there.
Does every site need one?
Not every site needs a full CMS. A small site that rarely changes might use a simpler, maintained workflow. The case gets stronger with frequent updates and many reusable items. Several editors or approval steps add to it. Decide from the tasks and ongoing support, not a count of ticked boxes.
How a CMS works
Most systems follow a four part pattern, from the editing screen to the public page.
Here, you means the business's editors. Agency means the developer or platform, and shared means both. It's a simplified model. The layers can sit in one service.
Storage often means a database plus media files, but systems differ. Hosting and caching, the saved copies that help pages load faster, are related services. So are domains and integrations. None of them is another name for the CMS.
One service record, start to finish
Here's what happens when an editor changes a service record:
Not every CMS offers approvals or review dates without setup. A cache or a scheduled build can also delay the public change after you click publish.
An example service record might hold these fields:
Field | Purpose |
|---|---|
Service name and description | Reusable information with a clear editorial owner |
Service area reference | A link to the correct location information |
Contact or booking destination | A verified next action for the visitor |
Image and meaningful alternative | Visual content with an accessible meaning |
Review date and owner | A prompt to check accuracy after publishing |
A content type is the reusable definition, like a service. Fields are its pieces of information. Entries are the individual records. One template can then display many entries consistently.
That's the trade off. Fixed fields keep every service page consistent and easy to update. Free layout editing gives each page more freedom, but pages can drift apart over time. Plenty of sites need both, so decide which pages need which.
Shared content can stop different phone numbers or prices appearing across pages. A change can also affect many places at once. Preview representative pages before publishing, and don't assume every CMS keeps every repeated value in sync. A common mistake is changing a shared detail without checking every page that shows it.
Editing an entry is usually straightforward. Changing a template or field definition can need a developer. That's the useful line: editing content versus changing how the system works.
Hosted, self hosted and headless explained
Three separate questions describe any CMS. People often blur them together.
Question | Options and what they mean |
|---|---|
Who operates it? | A hosted service runs specified infrastructure for you. A self hosted CMS runs on hosting the business arranges, often with a managed service. Either way, responsibilities need an explicit agreement. |
How is content delivered? | A coupled CMS connects editing and presentation in one main system. A headless CMS supplies content to a separate website or channel. Hybrid setups combine both. |
What's the licence? | Open source and proprietary software have different terms. Open source doesn't mean no running cost, and hosted doesn't always mean proprietary. |
The dimensions overlap. A headless product can be hosted and open source, depending on the product and arrangement.
What headless means
An API is a way for software systems to request or exchange data. Headless setups rely on one:
A headless setup keeps the presentation layer separate and delivers content to it through APIs. That doesn't mean editors need code for every change. They can still have a normal content interface.
Existing systems can work this way too. WordPress's REST API lets separate applications use WordPress content. Headless can help reuse content across channels or support a custom experience. It also raises questions to answer first:
who hosts and deploys the front end, the part visitors see
how previews and caching work
how search engines see the pages
who supports each part
Those are questions, not proof that headless always costs more or always loads faster.
WordPress.org and WordPress.com
WordPress is open source software. WordPress.com is a hosted service running that same software. With a self hosted setup, you arrange the hosting yourself, with any provider. Plan details belong in our guide to whether WordPress fits your business.
Custom builds raise a similar mix up. Custom isn't the opposite of a CMS. A custom built site might use WordPress, a headless service or a custom admin area. Some use no CMS at all. Ask what the editor sees and who maintains each part.
Which CMS do common platforms use?
Each platform manages content its own way. These are examples, not rankings:
Platform or approach | What manages the content | What to check |
|---|---|---|
WordPress | WordPress content types, editors and extensions | Editor permissions, templates, maintenance and export |
Shopify | Shopify's store admin and content features | Products, pages, blog and the commerce workflow |
Webflow | Webflow CMS Collections and visual tools | Structured items, editing roles, plans and delivery |
HubSpot Content Hub | HubSpot content tools on its platform | Content and CRM needs, permissions and the plan |
Wix | Wix editing tools and CMS collections | Dynamic content, editor workflow and integrations |
Squarespace | Pages, sections, blocks and collections | Content types, editing limits and export scope |
Custom or headless | The chosen existing or custom content system | Editor experience, front end support and ownership |
These products aren't all built on WordPress. Capabilities depend on the current version, plan and build. A few examples of how they handle content:
Shopify's online store covers webpages and a blog as well as products
Wix's CMS supports structured collections and dynamic pages
Webflow uses CMS Collections for structured content, and Webflow AI can generate Collection items
Squarespace has collection pages for blog posts, events and products
WordPress includes the block editor. With a block theme, it also has the Site Editor. Third party page builders are optional. Our guide to WordPress editing and page builder choices compares them.
Popularity alone doesn't prove suitability.
Pick the CMS most websites use
Pick the CMS whose editing, permissions, costs and exit fit your tasks
For stores, see Shopify and WooCommerce for Australian stores. For the full decision, see the detailed website platform comparison. We build on WordPress, Shopify and custom stacks, chosen by project fit.
How does a CMS help SEO?
A CMS can make it easier to publish, organise and maintain useful content. It doesn't earn rankings just by being installed. The output, the content and the day to day operation matter.
This CMS is the best for SEO
Show how our team manages content, URLs, metadata, links and the published page output
Ask the supplier to demonstrate each capability:
Capability | Question to ask |
|---|---|
Content and headings | Can the editor create a clear page with meaningful headings, links and image alternatives? |
URLs and redirects | Can suitable URLs be kept, and changed URLs redirected correctly? Who approves that? |
Metadata and canonical intent | Can titles, descriptions, canonical tags (which tell Google the preferred version of a page) and indexing settings be managed? |
Discovery and structure | Can the team build navigation, internal links and a sitemap, the file listing your pages for search engines, without thin duplicates? |
Structured data | Can accurate markup match the visible content and stay right when content changes? |
Rendering and performance | Does the page people and search engines actually receive contain the important content and links? Who diagnoses slow pages? |
Maintenance | Can owners review stale content, repair links and keep useful content through a migration? |
A plugin or settings field isn't proof the final page is right. Ask the supplier to show the public page, not just an admin screen. Some controls need an extension, developer setup or a different plan.
On a headless site, content management and public delivery are separate jobs. Confirm how each of these reaches the actual page:
titles, descriptions and canonical tags
internal links
previews of unpublished changes
published updates
Don't assume a headless site can't be indexed, or that one rendering method guarantees good SEO. For strategy, see SEO foundations for small business. For structure, see organising pages and internal links.
What about AI and AEO features?
Many systems now offer optional AI help for drafting, refining text or creating structured content. Check the exact feature, plan, permissions and usage limits before relying on it.
HubSpot's Breeze can generate or improve content in its editors, once a Super Admin switches it on. Webflow's AI item generation, mentioned above, is similar. Neither vendor claim proves better results for a business.
Use a review process whatever the tool:
Check generated image descriptions against each image's purpose. Translations need review by someone who knows the language. A common mistake is publishing AI drafts without checking the facts.
Check what data the feature sends to providers, and whether you're allowed to use that material. Never paste confidential customer records into an unreviewed tool. Our guide to privacy and information handling covers the obligations.
What AEO means
AEO, answer engine optimisation, usually means work to make content useful or visible in answer style search. There's no single AEO certification for a CMS. Ask what a vendor's AEO feature actually changes and how its claimed result is measured.
For Google's AI Overviews and AI Mode, Google says SEO foundations still apply, with no extra technical requirements. A page must be indexed and eligible to show a snippet. Appearance isn't guaranteed.
That covers Google's features, not every assistant. Some providers document separate controls for search, answer retrieval and model training. Check which apply before changing settings. No AEO plugin, AI text file or batch of generated FAQs guarantees inclusion. For the wider picture, see AI search and the role of SEO.
Can your team edit the site themselves?
Test with the intended employee's role. A common mistake is running the demonstration on a supplier's administrator account. Ask the editor to try:
a routine edit to an existing page
a new content entry, like a service
an image with a meaningful alternative
a preview and review
publishing, then a correction
Then note where developer work begins, like changing the content model or a site wide template. Each responsibility needs its own demonstration:
Responsibility | Ask them to show |
|---|---|
Author | Creates and revises permitted content without changing unrelated settings |
Reviewer or publisher | Checks the real preview and approves the right version |
Administrator | Manages access and settings, with privileges limited to those who need them |
Technical support | Maintains the agreed infrastructure, integrations and recovery process |
Content owner | Tracks accuracy, expiry and the next review after publishing |
These are functional responsibilities, not universal role names. In WordPress, an Editor publishes and manages posts but doesn't get the Administrator's site settings. Confirm the actual capabilities on your build.
Staff accessibility matters too. Editors need to use the admin screens with their usual technology, so ask your editor to try them. A public accessibility claim doesn't prove the editing screens work for your staff. ATAG, the Authoring Tool Accessibility Guidelines, treats that separately from the tool helping produce accessible content. See accessible editing and published content.
Revisions, exports and backups
Three different tools help you recover. Each covers different things:
WordPress revisions record saved drafts and published updates. By default they track the title, author, content and excerpt. The WordPress export produces structured content data, not a complete restorable copy.
A full WordPress backup needs the database and the files. Confirm your own platform's retention and restore scope. A common mistake is treating revisions as a backup. See backups and restore testing.
Create individual accounts, keep business controlled recovery and record who can publish. For WordPress, see WordPress access and security responsibilities.
How to choose using a real publishing task
Start with your essential requirements:
content types and update frequency
editors and approval steps
languages and integrations
accessibility and performance needs
support capacity and what must stay portable
Separate must haves from preferences. A failed must have can't be averaged away by attractive extras.
Then run the same task on each candidate system, in a safe demonstration environment:
Create a service entry from the same approved copy and image.
Assign the right category or location.
Add a meaningful image alternative.
Preview it and send it for approval.
Publish through the permitted route and check the public page.
Correct a deliberate, harmless typo.
Record each attempt the same way:
System: [platform, plan and build]
Editor: [role, experience and access needs]
Task: [same approved content and acceptance criteria]
Timing: [setup, editing, approval and delivery separately]
Help: [assistance and errors]
Result: [public output, correction and limits]
What to record | Why it matters |
|---|---|
Platform, plan and build | A product name doesn't describe the actual editing experience |
Editor role and experience | An expert administrator and a first time office manager aren't a fair pair |
Task, input and instructions | Use the same content and acceptance criteria |
Setup, editing and waiting time | Keep configuration, work and approval delays apart |
Assistance and errors | Note the help needed, failed attempts and corrections |
Quality and completion | Check the published page, accessibility, metadata and the correction |
Repeat observations | Record sample size and variation, not a universal speed ranking |
Measure real, consented tasks before quoting any timings. Don't compare an expert demo with a beginner, or differently scoped tasks. If the sample is small, say so beside the result.
Run an exit test too
Ask for a sample export, with an explanation of:
what's included and where media lives
whether forms and their entries come across
how fields and relationships map
which URLs and metadata survive
what needs rebuilding elsewhere
Ask who owns the domain, accounts, content and licensed assets. Admin access and an export don't prove you can take everything with you. Themes, licences and integrations may stay behind. See handover and account control.
Check another maintainer could understand the documented setup. A fashionable CMS can still be poorly configured. A simple one, set up well, can suit the workflow better.
Our platform comparison builds an example shortlist of up to five options from three questions. Its relative score isn't a mark out of ten. It also can't check essential features. Your task test still decides.
Our free audit checks your current setup and how you edit it, then names the first fix.
What does a CMS cost beyond launch?
The licence is only one line. Separate the full set:
initial design, setup and training
moving existing content across
hosting or the platform subscription
extensions and integrations
maintenance and support
internal content time
eventual exit work
In a real comparison, include renewal prices, GST treatment and any seat or usage limits. Don't count hosting twice if a subscription includes it.
Here's the full working:
Cost item | Assumption | Three year amount |
|---|---|---|
Initial setup and training | $4,200 once | $4,200 |
Hosting or subscription | $600 each year | $1,800 |
Extensions and integrations | $240 each year | $720 |
Maintenance and support | $900 each year | $2,700 |
Internal content labour | $600 each year | $1,800 |
Total over three years | $4,200 plus 3 x $2,340 | $11,220 |
All figures are examples, in AUD excluding GST, with constant annual amounts. They aren't a platform quote, a market average or an Elev8d offer.
Annual operation is $600 + $240 + $900 + $600 = $2,340. External spend is $9,420 over three years, plus $1,800 of assumed internal time. Don't add GST to internal salary time. Tax treatment depends on the business and supplier.
The example leaves out a major redesign, moving out, new features and transaction charges. Real costs can change at renewal or with usage. See ongoing website maintenance costs and website build and running costs.
Open source software can be free to license and still cost money to build, host, maintain and edit. A hosted service takes on specified tasks. The business still owns its accounts, content, permissions and decisions.
Common CMS mistakes and ongoing ownership
A CMS makes maintenance possible. It doesn't keep facts current by itself.
Give important content an owner and a review or expiry date, especially:
prices and offers
service availability
team details and photos
legal material and external links
Reminders only help if someone acts on them. For the planning side, see planning and reviewing business content.
Choosing by trend
Pick the system that fits your tasks and team, not the one people talk about most.
Confusing product features with a working build
Ask to see the feature working on a build like yours.
Granting excessive permissions
Give each person only the access their work needs.
Assuming revisions are backups
Keep a tested backup of the database and files.
Ignoring export limits
Run the exit test before you commit.
Buying AI features as a ranking guarantee
Treat AI as drafting help that still needs review.
Comparing only the first year subscription
Compare the full cost over several years.
What we recommend at Elev8d
Choose the CMS your team can actually run. Test a real task with the real editor, check the exit and budget for the years after launch. We can run that test with you as part of our website planning and development help.
Frequently asked questions
Is a CMS the same as a CRM?
No. A CMS manages website content. A CRM manages customer and prospect records. A form can connect them.
Does a static website mean there is no CMS?
Not necessarily. Some static sites are generated from a CMS. Others are edited in code or through a simpler workflow.
Can a small business use a headless CMS?
Yes, if there's a clear reason and someone supports the front end. Check the extra hosting, preview and support work first.
Can I move content to another CMS later?
Some of it, depending on the platforms. An exit test shows what exports, what maps across and what needs rebuilding. A platform change isn't always a complete rebuild.
Do I need a developer for every update?
No, not for routine content edits on a well built site. Changes to templates, fields or integrations can need one.
Next steps
Pick the step that fits.
Choosing a CMS
List your essential tasks, then run the same publishing test on each candidate.
Already have a CMS
Have your usual editor complete one real task and note where they needed help.
Planning to switch
Ask for a sample export and map what moves before committing.
