Measurement, control 4 of 17
M-04 Refresh while protecting proven assets
Preserve successful facts, sections, links and conversion paths unless evidence justifies changing them. A rewrite is not progress by itself.
- 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
Spinning up a new page when a relevant one already exists splits signals and leaves the older URL to go stale. Stripping out titles, sections, links or conversion elements that were working can throw away the very things that earned the traffic. Without a baseline and a change log, nobody can tell whether a refresh helped or hurt.
Evidence to review
- Before/after content, baseline metrics, hypothesis and regression tests.
How to implement
- Capture a baseline and identify the parts producing value.
- Correct stale information and actual task gaps.
- Prefer a bounded diff over a complete rewrite.
- Monitor the changed cohort and retain a tested rollback path.
- Record NO_CHANGE or DEFER as successful action-selection outcomes when evidence does not justify an edit. Protect valuable pages even when they do not match the preferred template.
How UltimateSEO checks this
Needs your evidence. No automated check covers this control, so it stays UNKNOWN until evidence is supplied.
Evidence needed: before-and-after metrics and the change log for refreshed pages.
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.