Date the claim, not just the page
A profile can contain a stable identity and a fast-changing integration claim. Give fields their own observed date, review due date and state: current, needs review, disputed or superseded. A site-wide “last updated” stamp cannot explain which part was actually checked.
- Identify facts that change frequently or strongly affect choice.
- Store observed-at and reviewed-at separately; show the appropriate date to readers.
- Expire or flag a claim when its evidence exceeds the policy for that field.
Make stale state actionable
When a source breaks or a claim ages past its threshold, the operator needs to know which pages and comparisons depend on it. A freshness label should link to a source and an owner for recheck. If the fact cannot be verified, disclose uncertainty rather than extending the date mechanically. This is how a Market remains useful without pretending every field is equally current.
Field-level freshness policy with review states
| Decision field | Record or rule |
|---|---|
| Current | verified inside the defined review window. |
| Review due | still visible but needs reconfirmation. |
| Disputed | conflicting evidence prevents a definitive claim. |
- 01Current
- 02Review due
- 03Disputed
A profile with mixed-age evidence
The official domain and product identity were checked recently, but an integration claim comes from an older page. The profile should not receive a single green “current” badge that covers both. Keep the integration at needs-review and leave the stable identity current. A buyer can then decide whether the older claim matters to their task. The operator can also target the exact source that needs rechecking instead of rereading the whole profile whenever any field ages.
A freshness policy also needs a consequence for expired claims: hold them, label them, or remove them from comparisons until checked. The choice depends on the risk of misleading a buyer. Merely assigning a review date without an action at expiry creates a calendar, not a quality control.
Do not extend a claim by changing its date
Freshness is not equivalent to truth. A very recent vendor claim may still require independent or direct buyer verification.
References and source notes
Original 1000&1 methodology reviewed and approved by the author. Public claims and historical measurements are bounded by the linked sources and dates.