Understand content and its lifecycle
Useful content retains context after publication. Identify its facts, origin and places where they are reused. Good organisation lets you correct information without leaving a document, translation or list in contradiction.
55 concepts to explore with definitions and practical advice.
Search the full glossary
A reading path
1. Identify information
Separate a claim, its source and reviewer. For a photo or portrait, also retain usage rights and the context actually depicted.
- Source citation
Precise reference to the resource supporting a claim, allowing readers to check context, date and limits.
- Claim register
Editorial register linking a page’s figures, dates, quotations and other important claims to sources, owners and next review dates.
- Content provenance
Set of elements documenting a piece of content’s origin, author, date, sources and transformations.
2. Classify for discovery
Choose categories helping readers or editors find the record. Taxonomy should not silently change the meaning of a document reused elsewhere.
- Taxonomy
Organization of content through categories, terms and explicit relationships. A taxonomy supports finding and grouping information; it may distinguish broader, narrower and related concepts. Its value lies in understandable classification rules rather than the number of labels created.
- Content inventory
Register of a website’s pages and media recording URL, purpose, owner, status and decisions to retain or update them.
- Resource library
Organised collection of documents or tools presented by need with an entry to assess before opening.
3. Plan review
Define the owner and change triggering review. A new editorial date does not prove that every fact has been rechecked.
- Content owner
Person responsible for approving accuracy, publication and updates for content or a set of pages.
- Content lifecycle
Stages through which content is managed: preparation, approval, publication, review and eventual removal or archiving according to usefulness. This lifecycle requires ownership and update criteria. A publication date alone does not determine whether information remains accurate, relevant and accessible.
- Document version
Identified state of a published file linked to a date and exact content, distinguishing the current document from older copies.
Useful distinctions
Content freshness / Content trust
Freshness concerns whether information is temporally suitable; trust also depends on provenance, precision and limitations. Recent copy can remain poorly sourced.
Metadata / Microcopy
Metadata describes content or context. Microcopy supports an interface action: help, button, error or confirmation. Both should remain consistent with the main content.
Use the vocabulary to make a decision

Situation
A record changes price but its download retains the old amount.
Before deciding
Find representations of the same information and choose the source to maintain. Then connect the record, download and translations.
A concrete check
Open documents through public links and compare amount, scope and effective period.
Trace a published fact back to its source
The same information may appear on a detail page, a summary and several translations. Identify its reference and conditions so a correction reaches every relevant representation.
On a narrow screen, scroll the table horizontally to read all three columns.
| Observed signal | What to check | What it means |
|---|---|---|
| Two pages state different amounts | Compare unit, period, tax basis and included service. | Different scope may explain the gap; otherwise a version needs correction. |
| A statistic has no time period | Find the survey, population and collection date. | A number becomes interpretable when its context is known. |
| An image resembles client work | Check origin, licence and caption. | Readers should be able to distinguish documentation from a fictional illustration. |
Next step : Name the reference page and its owner, then review dependent pages when the fact changes.
Technical reference : W3C — Data on the Web Best Practices. The scenarios and numerical examples above are educational, not measurements of this website.
One reference, four representations to reconcile
Fictional example: the reference has moved to v2. The FAQ already states this version, while the offer page and translation remain at v1. The summary version is unknown. Three representations therefore need review, without assuming that the unknown version is wrong.
- Offer pagev1Older version
- FAQv2Aligned with the reference
- SummaryUnknownVersion to verify
- Translationv1Older version
On a narrow screen, scroll the table horizontally to read all three columns.
| Representation | Recorded version | Follow-up |
|---|---|---|
| Offer page | v1 | Compare with the reference and update where needed. |
| FAQ | v2 | Check meaning and conditions of application. |
| Summary | Unknown | Identify the version and provenance before concluding. |
| Translation | v1 | Compare with the reference and update where needed. |
Matching versions does not establish factual accuracy or translation quality. This example describes editorial tracking, not the state of this website’s pages.
Reference : W3C: Data Provenance.
A page change is not a factual review
Fictional teaching case. Open each interpretation to examine its scope; there is no score or professional assessment.
- Change dated
- Facts scoped
- Source retained
A listing’s layout was corrected today. Its opening hours and contact details came from older information that was not reviewed during the change.
Which date can be stated without creating confusion?
A useful next step : Where useful, distinguish page modification from information verification. Keep the source and the person who validated the facts.
Reference to explore : W3C · Data on the Web Best Practices · Consulted .
All concepts in this topic
Links open the full definition on its alphabet page. Acronyms and synonyms remain searchable in the main glossary.
- API-first content
- Arrival directions
- Blog
- C2PA
- Claim register
- CMS
- Confirmation email
- Content Credentials
- Content decay
- Content freshness
- Content gap
- Content inventory
- Content lifecycle
- Content owner
- Content provenance
- Content pruning
- Content replacement
- Content trust
- Direct answer
- Document version
- Email subject
- Event page
- Event recap
- Event status
- Event time zone
- Evergreen content
- EXIF
- FAQ review date
- Frequently asked question
- Guest blogging
- H1
- Headless CMS
- Information gain
- IPTC photo metadata
- Media inventory
- Metadata
- Microcopy
- Newsletter
- Open Graph
- Original content
- Outdated content
- Portrait permission
- Resource library
- Resource type
- Resource version
- RSS
- Source citation
- Taxonomy
- Team profile
- Topical map
- Translation review
- User-generated content
- UX writing
- Video transcript
- WYSIWYG
Frequently asked questions
Should old content be kept?
Keep it if it retains identifiable usefulness, stating its context. Otherwise choose an equivalent destination or missing-resource state, then check links citing it.
Who should validate information?
The person or organisation able to confirm the fact. A writer organises and explains; they should not invent a missing amenity, client outcome or commercial condition.
Primary reference documents
These documents explain technical concepts. Reading paths and examples are editorial methods to adapt to your project.