Published evidence has a working life
A software consultant publishes a useful guide that cites a platform's documentation. Six months later, the platform changes its eligibility rules. The source URL still works, but the cited passage now says something different. The guide looks maintained while its central claim has quietly become unreliable.
Statistics are superseded. Credentials expire. Prices change. Case-study permissions are withdrawn. Source pages move or disappear. Publication is the beginning of an evidence lifecycle, not the end of one.
Google's people-first content guidance asks whether content demonstrates clear sourcing, expertise, factual accuracy, authorship, and a useful purpose. Those are useful trust tests after publication too. They don't guarantee a ranking or an AI citation.
If you need the principles for selecting and presenting evidence, start with what makes website content worth citing. This guide owns the next job. It shows how to keep evidence-bearing pages accurate once they're live.
Begin where the evidence audit ends
Start with an existing claim-evidence register. Each row should already name the page, material claim, supporting source, current status, owner, and risk. If that record doesn't exist, use the website claims and evidence audit to create it before building a maintenance routine.
The audit establishes what is true now. Maintenance asks what could change, who would notice, and what the team should do next.
Imagine a managed IT provider whose service page says its technicians hold a named security certification. The register connects that claim to the certification record and names the operations manager as the subject expert. Maintenance adds the credential expiry date, an alert before renewal, a review owner, and the action to take if renewal lapses.
That extra layer changes the register from an inventory into an operating record. It lets the team manage evidence deliberately instead of relying on someone to remember every claim.
Prioritise claims by consequence and volatility
Match the attention each material claim receives to two qualities: consequence and volatility.
Consequence is the harm caused if the claim is wrong. A lapsed professional credential can affect a buyer's decision and create legal or reputational risk. An outdated description of a minor interface carries less weight.
Volatility is how readily the underlying fact can change. Platform documentation, prices, staff credentials, regulations, and current statistics can move quickly. A well-sourced historical date is usually more stable.
Give closer oversight to claims with high consequences, high volatility, or both. Set a longer review interval for durable background facts, then reopen them if a relevant event occurs. Avoid assigning one quarterly or annual schedule to the whole site. It creates unnecessary work in stable areas and can still miss a fast change between review dates.
Evidence type also affects the trigger. Platform claims follow official documentation. Statistics follow new dataset editions or revised methods. Prices follow the service and commercial owner. Credentials follow renewal or role changes. Case-study results follow consent, measurement definitions, and changes to the underlying service. First-party studies need their own version, correction, and republication controls, which we cover in the original research guide.
Combine review dates with change triggers
A review date gives the owner a deadline to reassess a claim. A trigger starts a review when the world changes first.
The GOV.UK content maintenance guidance recommends assigning an owner, setting a review date, checking user needs and deciding whether content should be updated or withdrawn. Off Piste adapts that model for service-business evidence by adding claim-level triggers and source checks.
A useful register records both a next review date and the events that can bring it forward. Relevant triggers include:
- the source publisher releases new guidance or redirects the document
- a dataset receives a new edition, correction, or methodology note
- a professional credential approaches expiry or changes status
- the business changes a service, price, promise, location, or delivery process
- a case-study participant changes consent or the measured outcome is recalculated
- a monitoring check finds a broken URL, altered passage, or inaccessible document
- a customer, employee, regulator, or reader challenges the claim
Automation can detect a changed page or failed request. It can't decide whether the source still supports your wording. Send the alert to a named person who can read the evidence in context.
The IT provider might schedule a six-month review of its credential claim and trigger an immediate check when renewal status changes. The interval prevents neglect. The event trigger prevents the page remaining wrong for months.
Check meaning before checking the link
A successful status code only proves that a server returned something. It doesn't prove that the publisher, passage, method, scope, or conclusion remains suitable.
Review the page claim and its evidence together. Read the surrounding paragraph so you understand what the reader is being asked to believe. Open the source and find the precise supporting passage. Check whether qualifiers, population, location, timeframe, or conditions were lost when the claim was written.
Then inspect provenance. The W3C Data on the Web Best Practices recommends providing provenance information and citing original sources so data consumers can assess origin and trustworthiness. For a service-business page, that means preserving a traceable route to the original publisher where one is available. A summary article may remain readable while the primary standard or dataset gives the stronger support.
Check the publication date and method as part of the same decision. An older source isn't automatically wrong. A newer source isn't automatically stronger. Ask whether the method measures the thing your claim describes and whether the source's scope matches your audience.
This combined check matters because a citation can remain live while its meaning changes. Use the following prompt when a register row comes up for review.
Choose the smallest honest maintenance action
Use the evidence to make the least disruptive change that leaves the reader with an accurate page. The right action depends on what changed.
Retain the claim when the current source still supports its complete meaning. Record the check and next trigger without rewriting sound copy.
Repair a citation when the evidence is unchanged but its route is faulty. Replace a broken link with the publisher's new canonical URL, or update a citation that points to a temporary download. This is a mechanical repair when the reader's understanding doesn't change.
Narrow the claim when the source supports only part of it. A national statistic may not justify a statement about Perth businesses. Preserve the useful, supported portion and remove the unsupported reach.
Replace evidence when a new primary source supersedes the old one. Read the replacement before linking it. A current edition may use a different population or method, so it may also require revised wording.
Correct the page when the published statement was materially wrong. The Reuters Journalistic Standards emphasise accuracy, honest sourcing, and prompt correction. The Associated Press statement of principles says corrections should be clearly labelled and explain the error. These are newsroom standards, not universal website rules. The proportionate lesson for a service business is to make a meaningful correction visible enough for an affected reader to understand what changed.
Redirect a redundant page when another current page serves the same purpose and preserves the useful destination. Archive a page when the historical record still has value but its advice should no longer guide a current decision. Label its status clearly. Remove a claim when no defensible evidence remains. Remove a whole page only when it has no continuing purpose and a redirect or archive would mislead.
The IT provider can quietly repair a certification-register URL if the credential remains valid. If the credential expired, the provider should remove the claim promptly. If buyers may have relied on it, a visible correction or change note provides a more honest record than silent deletion.
Record changes without overstating freshness
The maintenance register should capture the page, claim, source, trigger, reviewer, decision, decision date, and a concise note. Record the old and new wording when meaning changes. This gives the next reviewer enough context to understand the decision without reconstructing it from a page diff.
Keep the original publication date fixed. Set a modified date when a substantive editorial revision changes accuracy, evidence, advice, conclusion, or useful scope. Google's Article structured data documentation defines datePublished as the first publication date and dateModified as the most recent modification date. Google recommends timezone information and consistency between visible dates and structured data.
A spelling fix, formatting change, cosmetic rewrite, or routine link repair shouldn't manufacture a fresh editorial date. A correction to an important fact can justify one even when only a sentence changed. The decision turns on reader meaning, not word count.
When the date changes, update the visible page and its structured record together. Our guide to accurate Article schema, authorship, and dates explains how to keep the CMS, page, and JSON-LD aligned.
A modified date tells readers that meaningful work occurred. It isn't proof that every claim was reverified, and it doesn't guarantee improved search performance. If you perform a complete evidence review, say so in a change note and record its scope.
Make the system fit the team and CMS
A small business doesn't need to imitate a national newsroom. It does need clear accountability for claims that influence customers.
Give claim approval to the person with the relevant subject expertise. They might be the service lead, compliance adviser, finance owner, or project analyst. Give monitoring to a practical content owner who can manage alerts and review dates. Give publication control to the editor or web owner who can update copy, change notes, metadata, redirects, and archives consistently.
One person may hold several roles. Name the role for each register row anyway. If they leave or responsibilities change, the business can reassign the work without losing the rule.
The CMS should support the process with a few durable fields. Store the source URL, source title, last checked date, next review date, trigger, evidence owner, decision, and change note. Templates should keep visible dates and structured data connected to the same editorial record.
When the evidence is valid but difficult to inspect, repair the page structure for readers and search systems. If the CMS can't hold review fields, truthful dates, or visible correction notes, website design and development can turn the workflow into a maintainable publishing system.
Start with reminders before buying specialist monitoring software. Subscribe to official updates, record known release cycles, and add calendar alerts for credentials and commercial changes. Introduce automated source monitoring where the volume and volatility justify it. Keep human review at the point where meaning is assessed.
A maintained evidence estate is easier to defend
Good maintenance makes responsibility, evidence, decisions, and changes visible enough to manage. It keeps claims defensible as the facts around them change.
Take the highest-consequence pages from your existing evidence audit this week. Assign an evidence owner and a publishing owner to each material claim. Add one risk-based review date and the real-world trigger most likely to make that claim stale.
If the constraint is governance, source selection, or prioritisation across a large content estate, evidence-led SEO support can help define the operating model. If the constraint is missing CMS fields, templates, correction notes, or structured data, the solution belongs in the website system.