Retrieval and usability, control 7 of 18
R-07 Keep URLs stable and intentionally structured
Prefer understandable, stable URLs, but do not change established identifiers merely to add keywords or a current year.
- Priority
- Optimisation.
- Hard gate
- No
- Change class
- APPROVAL_REQUIRED: Required exact authority must be valid before the consequential action.
- Quality bucket
- Retrieval and usability
Why it matters
When the same page is reachable through several parameterised or changing URLs, signals are split and users and crawlers hit duplicates or redirect chains. Stable, readable addresses give search engines and AI answer engines one identity to cite and keep links working over time.
Evidence to review
- Route inventory, existing links, redirect history and canonical relationships.
How to implement
- Identify unnecessary aliases and tracking parameters.
- Preserve functional IDs where they are part of the architecture.
- Use redirects and update internal references only under an approved URL-change plan.
- Keep meaningful variants distinct from duplicate URL noise.
How UltimateSEO checks this
Automated. A check in the scan sets PASS or FAIL for this control, and reports UNKNOWN or BLOCKED when its input is missing.
The check looks at: URL hygiene on crawled pages (query parameters, uppercase, trailing-slash duplicates, excessive length).
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.