Canonical Tag Names a Different Address Than the Page Loads On
The canonical tag points at another version of the same site (different www or http/https) than the one the page opens on. Search engines get mixed signals about which address to list.
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
The canonical tag points at another version of the same site (different www or http/https) than the one the page opens on. Search engines get mixed signals about which address to list.
Why it matters
The canonical tag points at another version of the same site (different www or http/https) than the one the page opens on. Search engines get mixed signals about which address to list. This affects crawlability, rendering, and whether the site can be interpreted correctly by search engines.
How we detect it
- FreeSiteAudit flags this issue when the rule for TECH-CANONICAL-HOST-001 fails and the page evidence points to Head metadata.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
How to fix it
- 1Make the canonical tag use the same address style the site redirects to (https, and the same www choice)
- 2Check the setting in your SEO plugin or theme that writes the canonical tag
- 3Use the same address in the sitemap
How to re-check it
- View the page source and confirm the canonical URL matches the address bar
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.