Web development

Content Management: Questions for Organising and Maintaining Your Website

You have a website that needs updating, but every change ends up spread across emails, different documents, and uncertainty about which version is correct. Content management helps organise that work: what information is published, who reviews it, where it is edited, and how it is kept consistent.

Here you will find what it covers, what you need to define, and when a website needs more than a text editor. By the end, you will be able to decide whether organising your way of working is enough or whether you should consider a web solution that makes editing easier.

Defining questions

What is content management?

It is the organisation of the information a company publishes and maintains across its digital channels. On a website, it includes deciding what content exists, how it is structured, who can modify it, who approves it, and what happens when it is no longer current.

It is not limited to writing pages. A service description, news item, offer, frequently asked question, image, or downloadable document is also content if it needs to be created, reviewed, and updated.

What is website content management for?

It ensures that important information can be found, understood, and updated without having to improvise each time. It also reduces a common dependency: having only one person know where a text is, which version is valid, or how to change it.

The goal is not to publish more. It is to maintain the information that helps someone understand your company, your services, or the next action they can take.

What is a content management system, or CMS?

A content management system, also known as a CMS, is the tool you use to edit a website without directly changing its code. It may allow you to create pages, modify text, upload images, organise content, or schedule publications.

The tool does not solve the organisational problem on its own. If content types, permissions, and review processes are not defined, a CMS can simply move the disorder to an editing screen.

Scope questions

What should basic content management include?

It should include, at a minimum, four decisions:

  • Inventory: which pages, documents, images, and other resources exist.
  • Structure: how they are grouped so they can be found easily.
  • Responsibilities: who prepares, reviews, approves, and publishes each item of content.
  • Maintenance: when information is reviewed and what happens to content that is no longer valid.

The scope may grow if you manage several languages, a catalogue, content for different profiles, versioned documents, or data that must be synchronised with another tool.

Who should be responsible for updating the website?

The person or team responsible should be the one that knows the information and can confirm that it remains correct. The technical side can make editing easier and handle structural changes, but it should not become the only place where knowledge of your business resides.

It is advisable to assign two roles, even if the same person takes them on: the person who edits and the person who approves. This separation is useful when a change affects services, terms and conditions, prices, contact details, or messages that are sensitive for the company.

Is an editorial calendar necessary?

It is only necessary if the frequency or variety of publications makes it difficult to maintain control. For a small corporate website, a periodic review of key pages may be enough. If you publish updates, resources, listings, or campaigns, a calendar helps anticipate responsibilities, dates, and required materials.

Do not confuse a calendar with an obligation to publish. Its purpose is to provide visibility over what you have already decided to maintain.

How do you decide which content is a priority?

Prioritise based on the website's objective and the information a visitor needs in order to move forward. For example, a service page may need reviewing before an old post that is not maintained and does not represent a current decision.

A practical way to classify each item of content is:

  • Essential: explains an offering, an action, or operational information that must be available.
  • Useful: expands on or supports the main content, but can be postponed.
  • Pending validation: exists, but it is unclear whether it remains correct, necessary, or approvable.
  • To be retired: no longer serves a purpose and should be archived, redirected, or removed, as appropriate.

Technical questions

What should the editing tool allow you to do?

It should support the tasks your team needs to carry out safely and without relying on fragile steps. Before choosing a solution, define specific actions: creating a page, updating a listing, changing an image, uploading a document, reviewing a draft, or restoring a version.

Also define who can carry out each action. Providing editing access does not require giving access to all of the website's technical settings. Permissions should reflect each person's actual responsibilities.

When is structured content advisable?

It is advisable when you repeat the same type of information and want to maintain a consistent presentation. Instead of editing every page as a free-form block, you can define specific fields: title, summary, image, category, date, indicative price, or associated document, as applicable.

For example, in a hypothetical case, a company with several locations might need a listing with fixed fields for address, opening hours, services, and contact details. That structure makes it easier to check what is missing and prevents each listing from being built differently.

What is the difference between editing a page and managing structured content?

Editing a page means modifying a specific set of texts and elements. Managing structured content means maintaining records with defined fields that can then be displayed in different parts of the website.

The first option usually suits websites with a small number of stable pages. The second becomes more useful when there are catalogues, directories, cases, resources, offers, or other repeatable items that need to be filtered, organised, or reused.

Do content items need to be migrated when redesigning a website?

This needs to be decided before building the new website. Migration is not simply a matter of copying and pasting text: it involves taking inventory of what exists, deciding what to keep, rewrite, or remove, and determining how pages or documents that change location will be handled.

Not everything old is worth moving. However, removing or changing information without reviewing its purpose can create inconsistencies, broken internal links, or gaps in the visitor journey.

Limits and exceptions

Does content management replace a sales or marketing strategy?

No. It organises how information is created and maintained, but it does not independently decide what offering to make, what message to approve, or which audience to address. It is an operational foundation for ensuring that those decisions are reflected consistently on the website.

Decisions about positioning, advertising, regulatory compliance, or commercial claims require validation from the people responsible within your company and, where appropriate, specialised professionals.

Can someone without technical knowledge update every part of the website?

Not necessarily. Some updates are editorial, while others affect design, functionality, forms, integrations, performance, or security. Combining them under the same access level increases the risk of changes that are difficult to detect or reverse.

The reasonable solution is to separate what should be routinely editable from what requires technical review. That boundary depends on how the website has been built and on the tasks you intend to handle internally.

Is a CMS suitable for every project?

Not by default. It may be suitable for managing a website's content, but a project with specific rules, different user profiles, data connected to other systems, or internal processes may require a more clearly defined solution.

The choice should start with the objective and scope. First, specify what content you manage, who uses it, what operations it requires, and what changes you expect. Then it makes sense to assess the tool.

Next decision

What should you define before requesting changes or a new website?

Prepare answers to these questions:

  1. What information needs to be updated without technical intervention?
  2. What types of content will you maintain: services, news, resources, listings, documents, or others?
  3. Who edits and who validates each type?
  4. Which current content needs to be retained, reviewed, or removed?
  5. What tasks should a person with editorial access not be able to perform?

With these decisions, you will be able to distinguish between a need for internal organisation and a need for development. If you need to define a website that allows you to manage your content with the appropriate scope and permissions, you can describe your web development project to AVSISTEC.