Proportionate optimisation, control 8 of 8
O-08 Diagnose outcomes before rollback or further optimisation
P0Hard gateNeeds your evidence
Distinguish confirmed policy or technical harm from uncertain search changes. Do not declare an over-optimisation penalty from an isolated ranking drop, and do not keep escalating edits until a chosen metric improves.
- Priority
- Gate. A FAIL stops publish or launch.
- Hard gate
- Yes. A FAIL stops publication, whatever the score.
- Change class
- READ_ONLY: Inspect authorised evidence.
- Quality bucket
- Not scored: hard gate only
Evidence to review
- Live validation, incident/measurement records, cohort exposure and data-quality checks, uncertainty and recovery decision.
How to implement
- Record whether evidence supports a manual action, suspected automated policy issue, technical regression, ordinary relevance change or unknown cause.
- Check reliable instrumentation, relevant platform exposure and mature reporting before evaluating search results.
- Use predefined guardrails and the same observation design; record seasonality, update windows and simultaneous business changes.
- Hold expansion when evidence is missing or inconclusive. Low traffic is not proof of safety or harm.
- Stop immediately on verified harmful technical/factual/security defects; distinguish stop-new-writes from an authorised safe rollback.
- Log KEEP, REWORK, HOLD, RECOVER or NO_CHANGE with evidence and a next review trigger.
How UltimateSEO checks this
Needs your evidence. No automated check covers this control, so it stays UNKNOWN until evidence is supplied.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
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.