Proportionate optimisation, control 2 of 8
O-02 Review naturalness across the complete rendered page
P0Hard gateNeeds your evidence
Review the meaning and user purpose of repetition across surfaces. Counts and similarity flags can triage review but cannot diagnose a penalty or order automatic deletion. Preserve exact terminology where it is useful.
- 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
- Candidate-bound screenshots/DOM and annotated before/after review; include false-positive explanations, not only an automated score.
How to implement
- Read the candidate in context, on mobile and desktop where the change affects layout.
- Compare title, H1/H2, intro, body, link labels, alt text and footer together; review visible content against structured data.
- Distinguish forced keyword insertions from accurate product identifiers, branded navigation, legal wording and repeated table labels.
- Do not impose keyword-density percentages, ideal anchor ratios, mandatory answer length or a required count of schema types.
- Resolve each flag as an evidenced defect, justified legitimate pattern or unresolved concern; unresolved material concerns hold publication.
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.