Technical eligibility · Branch T.B, Canonical, discovery and URL management
T-03 Canonical signals must converge on a single target
Redirects, rel=canonical, the sitemap and internal links must all point to the same preferred URL. Redirect loops and chains must not be created.
- Scope
- All public content
- Priority
- Gate. A FAIL stops publish or launch.
- Quality bucket
- Technical eligibility
- Legacy coverage
- SEO-35
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.
How to implement
- Decide the one preferred URL for each page.
- Point redirects, rel=canonical, the sitemap and internal links at that URL.
- Collapse any redirect chains so each old URL redirects straight to the final one.
- Remove redirect loops.
- Compare your declared canonicals with the Google-selected canonical and fix mismatches.
How to audit
- Check the canonical graph and the Google-selected canonical.
How UltimateSEO checks this automatically
Automated. Checked automatically: 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.1, revised 2026-10-07. Evidence states, control states and the publish gate are explained on the hub.