Technical eligibility, control 3 of 20
T-03 Align canonical signals without collapsing distinct resources
Redirects, canonical annotations, sitemaps and internal links should agree on preferred equivalent resources. A canonical is a signal, not an instruction guaranteed to be obeyed.
- Priority
- Gate. A FAIL stops publish or launch.
- Hard gate
- Yes. A FAIL stops publication, whatever the score.
- Change class
- APPROVAL_REQUIRED: Required exact authority must be valid before the consequential action.
- Quality bucket
- Technical eligibility
Why it matters
When redirects, canonical tags, sitemaps and internal links name different URLs, search engines have to guess which version to keep. Visitors can land on duplicate or redirected addresses, and AI answer engines that draw on Google's index may cite a version you did not choose. Loops and chains add further friction because crawlers must follow extra hops to reach the page.
Evidence to review
- Canonical graph, original and rendered HTML, redirects and selected-canonical evidence where available.
How to implement
- Build a canonical graph; identify chains, loops, cross-domain targets and accidental template defaults.
- Compare declared and engine-selected canonicals.
- Do not canonicalise materially different products, languages or pagination pages to one generic URL.
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: canonical tags on crawled pages are self-referencing, absolute, https and consistent with redirects and the sitemap.
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.