Quality and evidence, control 8 of 15
Q-08 Use honest content freshness
Visible updates, dateModified and lastmod should reflect meaningful changes, not cosmetic date refreshing for rankings.
- Priority
- High priority.
- Hard gate
- No
- Change class
- AUTO_WITH_TEST: A candidate requiring relevant tests.
- Quality bucket
- Freshness and maintenance plan
Why it matters
A fresh date on unchanged content misleads readers into trusting out-of-date prices, specifications or rules. Search engines and AI answer engines that use dates to judge freshness are given a false signal. Keeping dates honest protects the trust the page has earned.
Evidence to review
- Content diffs, fact-check records and timestamp logic.
How to implement
- Compare revision history with timestamps.
- Separate a fact rechecked without changes from substantive content modification.
- Assign owners and review triggers for volatile information.
- Do not change URLs merely to insert a new year.
- An experimental observation hold does not permit leaving a verified wrong price, security issue or materially false claim uncorrected; route an exact correction through the incident/correction path.
How UltimateSEO checks this
Partly automated. The scan records page signals, but a passing signal is kept as information: contextual or account evidence is still needed to establish the control.
The check looks at: the crawler compares dateModified in schema with the visible date and, where a previous crawl exists, sitemap lastmod with real content change; whether an update was substantive is confirmed by a person.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Sources
Part of The UltimateSEO Framework v4.3, catalogue dated 2026-10-14. Evidence states, control states and the publish gate are explained on the hub.