Canonical Points to a Different Protocol or Host
Canonical URL references a different protocol or host than the current page, causing indexing issues.
By Seoxpert Editorial · Published
Why it matters
When a page's canonical tag points to a different protocol (HTTP vs HTTPS) or host (www vs non-www), search engines may split ranking signals between URLs. This can dilute SEO value and cause duplicate content issues, making it harder for your preferred URL to rank.
Impact
If unresolved, search engines may not consolidate signals, harming rankings and causing inconsistent indexing.
How it's detected
A crawler compares the page's URL with the canonical tag and flags if the protocol or host differs.
Common causes
- Mixing www and non-www versions in canonical tags
- Referencing HTTP instead of HTTPS in canonical tags
- Copy-pasting canonical tags across domains without updating
- Incorrect CMS or plugin configuration
How to fix it
Code examples
Incorrect canonical (different protocol and host)
<link rel="canonical" href="http://www.example.com/page.html" />Correct canonical (matching protocol and host)
<link rel="canonical" href="https://example.com/page.html" />FAQ
Can I canonicalize from HTTPS to HTTP?
No, it's best practice to canonicalize to HTTPS, as it is more secure and preferred by search engines.
Should I use www or non-www in my canonical URLs?
Pick one (www or non-www) as your canonical host and use it consistently in canonical tags and redirects.
What happens if my canonical tag points to a different domain?
Cross-domain canonicals are only appropriate for syndicated content; otherwise, it can confuse search engines and split signals.
Do I need to update both canonical tags and redirects?
Ensure both are consistent. If you redirect to the canonical, the tag should match the destination.
Found this issue on your site?
Run a scan to see if Canonical Points to a Different Protocol or Host affects your pages.
Scan my website →