Maintain content: What needs to stay current and what has lasting value

Different content needs different review cycles

Companies should assign content to at least three maintenance classes: timeless fundamentals, conditionally stable technical information, and current content.

Each class requires its own review intervals, responsibilities, linking rules, and decisions on updating, merging, archiving, or removal. Without this distinction, a content inventory grows whose reliability no one can safely assess anymore.

Initial situation in December 2024

Many websites contained articles from several years. Older content could remain relevant because it answered fundamental questions. Other pages seemed current even though examples, data, products, or technical notes were no longer correct.

The visible publication date alone did not solve the problem.

An old article may still be technically valid. A new article may already be outdated if it refers to a short-term product state. The decisive factor is the change dynamics of the statement.

Typical risks were:

• outdated prices, features, or legal information,
• broken source and download links,
• old service names,
• contradictory definitions,
• multiple articles on the same topic without a clear reference page,
• current news that remained permanently in the navigation,
• timeless posts that were unnecessarily replaced because of their age.

Three classes of digital content

1. Timeless Basics

Timeless content covers basic principles, definitions, methods, or decision-making logic whose core remains stable over a longer period.

Examples:

• Why a digital strategy is more than just a list of measures
• What task content must fulfill
• How responsibilities are clarified in a project
• What role a website plays in the information and decision-making process

Timeless does not mean maintenance-free. The following must also be checked:

• Terms,
• internal links,
• sources,
• examples,
• Service connections,
• technical representation.

The technical core usually remains the same. Connectivity can change.

2. Conditionally stable technical information

This content has a stable basic structure but contains variable details.

Examples:

• technical recommendations,
• Platform and tool comparisons,
• legal or regulatory classifications,
• market and search developments,
• Process descriptions with specific systems,
• product or service details.

Fixed review events make sense for this class:

• publication of a new standard,
• Product change,
• legislative amendment,
• Relaunch,
• Renaming a service,
• Change of an internal responsibility.

A blanket annual review can be too infrequent or unnecessarily frequent. Risk determines the rhythm.

3. Current content

Current content relates directly to a month, an event, a publication, or a specific product version.

Examples:

• monthly reviews,
• event information,
• short-term market reactions,
• product announcements,
• time-bound campaigns,
• current disruptions or transitional arrangements.

These types of content require a decision as early as creation:

• When does immediate relevance end?
• Will the content be kept as a historical record?
• Will it be converted into a permanent foundational article?
• Does it need to be removed or redirected?
• Which data and links should not remain visible indefinitely?

Content maintenance is more than updating

Confirm

Content has been reviewed and remains valid unchanged. The review is documented internally.

Update

Individual statements, sources, examples, or links are adapted while the page role remains the same.

Merge

Several overlapping pieces of content are bundled into a binding reference. Old URLs receive appropriate redirects.

Reorganize

A current contribution can later remain valuable as a historical perspective. Then its time limitation must be clear.

Archive

Content of documentary value is preserved, but removed from active user guidance and marked as historical.

Remove

Content without ongoing utility, with legal risk, or containing false statements will be removed. Before doing so, check whether forwarding, documentation, or retention is required.

Perspective from practice

Content maintenance rarely fails because nobody wants to update. It fails due to unclear responsibility.

The editorial team can check links, but cannot technically evaluate every technical statement. Subject matter experts recognize changes, but lack an overview of all affected pages. Web managers can remove content, but do not always know its business significance.

Therefore, every important content area requires at least three clearly designated roles:

• subject matter owner,
• editorial maintenance,
• technical implementation.

In small companies, these functions may be held by the same person. Nevertheless, they must be consciously distinguished.

Framework of action

1. Classify content

Every relevant page is assigned a lifecycle class and a risk level.

2. Define review events

In addition to fixed dates, triggering events are defined, such as product changes or new guidelines.

3. Assigning responsibilities

Not "Marketing" or "Department", but a specific role bears responsibility for the review.

4. Document changes

Important technical changes are recorded in a comprehensible manner. Visible date indications are not required in every case. Technical and internal review data nevertheless remain important.

5. Consider links

If a core message is changed, all using pages and documents must be identifiable. A knowledge architecture facilitates this traceability.

6. Treat removal as regular maintenance

Deletion is not failure. A well-maintained system does not contain as much as possible, but rather the knowledge currently needed and justifiable.

What companies should not do

Not sensible are:

• to replace any older content solely because of its age,
• treating current reports permanently as fundamental knowledge,
• changing a "last updated" date without a genuine review,
• maintaining legal or technical content without subject matter responsibility,
• deleting outdated URLs without replacement if a suitable target exists,
• reviewing all content on the same annual cycle,
• keeping unclear content online solely for SEO reasons.

Consequences for companies

Content governance begins with the realization that content is a lifecycle object.

Companies need not only a process for new publications. They need an equally clear process for review, confirmation, modification, and removal.

This keeps the digital knowledge base credible, clear, and usable for both humans and systems.

Subject-matter connection

Content governance as an ongoing management task

Content governance connects content classes, review events, responsibilities, and technical maintenance. In SDC-Growth, this logic can be set up as an ongoing review system so that relevant content is further developed and outdated statements are systematically cleaned up.

Controlling content systems and maintenance within the scope of SDC-Growth