Publishing is a beginning.
Maintenance builds trust.

Map what can change

Not every element ages at the same rate. A general method may remain useful for years, while a price, procedure, software version, rule or schedule can become wrong quickly.

For each important page, identify external links, figures, dates, people, products and conditions that deserve another check. This map focuses effort where an error would have a real effect.

Assign editorial priority

Priority depends on information volatility, page use and the possible consequence of an error. A widely used administrative procedure deserves faster attention than a clearly dated historical example.

Maintenance should not become an unrealistic promise of permanent monitoring. It is better to state limits, address higher risks first and temporarily remove a passage that cannot be confirmed.

Check links and destinations

A link can disappear, redirect to different content or lead to a resold domain. Review should therefore inspect not only the response code but also the final destination and whether it still matches the link text.

A legitimate redirect can be updated. An unrelated, misleading or unsafe destination should be removed without waiting for a complete page rewrite.

Treat corrections as data

Every useful report reveals either an isolated issue or a weakness in the process. Record the page, error type, cause and applied solution to identify recurring problems.

If several corrections involve missing dates, poorly identified sources or an ambiguous category, improve the publishing model rather than only repairing reported pages.

Update without simulating freshness

A modification date should correspond to a substantive change: corrected information, replaced source, improved structure or expanded analysis. Changing only the date does not make content more reliable.

When an old passage remains useful for context, keep it with a clear period label. When it can no longer help without misleading, archive or remove it.

Create a simple editorial register

For every page, a register can record its purpose, owner, main sources, volatile elements and last substantive change. It does not need to be complex to become useful.

Add a clear state: current, review needed, suspended or archived. A page with no owner or identifiable purpose should prompt a decision instead of remaining online indefinitely.

The register provides an overview and prevents maintenance from depending solely on webmaster memory.

Define review triggers

A scheduled date suits predictable content, but some changes should trigger an earlier check: an official-source update, new product version, domain redirect, documented report or unusual rise in errors.

High-impact pages can combine periodic review with these alerts. Stable pages can be reviewed when a relevant event occurs.

A trigger should open a precise task: check the source, test the procedure, rewrite the passage or decide on removal.

Measure maintenance quality

The number of edited pages is not enough. Observe resolved broken links, eliminated recurring errors, correction time and the share of content with an identified owner.

Fewer reports can indicate improvement, but may also mean the contact route is hard to find. Combine indicators with real reading and qualitative feedback.

Good maintenance gradually removes causes of error instead of multiplying superficial edits.

Separate page updates from data periods

A page changed today may publish a series for an earlier year. When useful, keep three dates separate: observed period, source publication and consultation.

Before replacing a table, also compare unit, area and method. A new release can change coverage rather than simply add a period; retain the exact resource used.

The data.gouv.fr documentation distinguishes datasets from resources such as historical files, documentation and current data.