Technical fix guide
Hreflang and Canonical Conflict
Page has hreflang annotations but the canonical URL points to a different page, creating a conflict that may cause search engines to ignore the hreflang.
Issue ID: TECH-HREFLANG-CANONICAL-001
Severity: moderate
Impact: High
Effort: S
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
Page has hreflang annotations but the canonical URL points to a different page, creating a conflict that may cause search engines to ignore the hreflang.
Why it matters
Page has hreflang annotations but the canonical URL points to a different page, creating a conflict that may cause search engines to ignore the hreflang. 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-HREFLANG-CANONICAL-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
Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.
How to fix it
- 1Ensure each hreflang page has a self-referencing canonical URL
- 2Do not point canonical to a different language version
- 3Canonical and hreflang self-reference should match exactly
How to re-check it
- Confirm canonical URL matches the self-referencing hreflang URL
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.