Canonical URL resolves to a different host
ShipReady resolved the page's single supported canonical href and found a host different from the fetched page's host, excluding a www-only variant.
Why it matters
A cross-host canonical is an explicit publisher signal worth reviewing. It may be intentional for syndication or related domains, and ShipReady does not determine ownership, content relationship, or search-engine treatment.
How ShipReady detects it
What it inspects
ShipReady reads supported canonical link hrefs from a successfully fetched, readable, content-serving HTML document and resolves the single canonical href against the page URL.
What triggers a finding
The rule triggers when the resolved canonical host and page host differ after removing only a leading www. variant. Pages with conflicting canonical values are handled by the separate conflict rule first.
What the evidence shows
The fetched page's single supported canonical href resolved to a host other than the page host under ShipReady's www-normalized comparison.
Limits of this check
ShipReady does not request the canonical target, verify domain ownership, compare content, determine syndication intent, or establish which URL a search engine indexes or ranks.
How to fix it
Confirm the intended relationship between domains
Review whether the cross-host canonical is deliberate for syndication, migration, or another documented URL strategy.
Set the intended canonical host
If the cross-host value is unintended, correct the page, template, CMS, or deployment configuration that emits it and inspect the rendered result.
How to verify the change
Inspect the final resolved canonical
Request the deployed page and resolve its canonical href relative to that page URL.
Expected: The canonical host matches the deployment's intentional URL strategy.