You have a multilingual site. Each language version has hreflang annotations and a canonical tag. But Google ignores hreflang, or indexes the wrong language version. The cause may be a conflict between canonical and hreflang. This guide explains why canonical and hreflang conflict and how to fix it.
What canonical and hreflang do
Canonical tells search engines which URL is the preferred version of a page. Hreflang tells search engines which language and regional version to show to which user.
They serve different purposes:
— canonical consolidates duplicate content;
— hreflang serves the right language version.
When configured correctly, they work together. When they conflict, Google may ignore one or both.
Why conflict breaks multilingual SEO
If the canonical of a German page points to the English page, Google may treat the German page as a duplicate and ignore it. The hreflang annotation becomes meaningless.
What happens:
— Google sees canonical pointing to another language;
— Google treats the page as duplicate;
— the page is not indexed;
— hreflang is ignored;
— users see the wrong language version.
This is one of the most common multilingual SEO mistakes.
Reason 1: canonical points to another language
The most common cause. The canonical of a language version points to a different language version, often English.
What to check:
— does canonical point to the same language;
— is canonical self-referencing;
— is canonical generated automatically.
The fix: each language version should have a self-referencing canonical. Canonical should not point to another language.
Use canonical tag checker to see the canonical on each page.
Reason 2: hreflang missing return links
Hreflang requires return links. If the English page references the German page, the German page must reference the English page.
What to check:
— does each language version reference all others;
— are return links present;
— are there broken hreflang links.
The fix: ensure every language version references all others, including itself.
Reason 3: x-default points to wrong page
x-default tells Google which page to show when no language matches. If x-default points to a page that is canonicalized elsewhere, conflict occurs.
What to check:
— is x-default set;
— does it point to the right page;
— is it consistent across the cluster.
The fix: set x-default to the global version. Ensure it is consistent.
Reason 4: canonical and hreflang in different places
If canonical is in HTML but hreflang is in sitemap, they may conflict if not aligned.
What to check:
— where canonical is set;
— where hreflang is set;
— are they consistent.
The fix: align canonical and hreflang. Use one method for hreflang and ensure canonical matches.
Reason 5: canonical points to a redirect
If canonical points to a URL that redirects, Google may ignore canonical or follow the redirect.
What to check:
— does canonical point to a redirect;
— where does the redirect lead;
— is the final URL canonical.
The fix: canonical should point to the final URL, not a redirect.
How to diagnose canonical-hreflang conflicts
A practical sequence:
— check canonical on each language version;
— check hreflang annotations;
— check return links;
— check x-default;
— check for redirects;
— test with Search Console.
If canonical points to another language, fix it first. Then verify hreflang. For a broader audit, SEO audit can help verify canonical, hreflang and indexing in one place.
How to fix canonical-hreflang conflicts
Fix steps:
— make canonical self-referencing on each language version;
— add return links to hreflang;
— set x-default correctly;
— align canonical and hreflang methods;
— avoid redirects in canonical;
— test after changes.
FAQ
Why do canonical and hreflang conflict?
Most often because canonical points to another language version. This makes Google treat the page as duplicate and ignore hreflang.
Should canonical point to the same language?
Yes. Each language version should have a self-referencing canonical.
Can hreflang work without canonical?
Yes, but canonical helps consolidate signals. If canonical conflicts with hreflang, both may be ignored.
What is x-default?
It tells Google which page to show when no language matches. It should point to the global version.
Do I need return links for hreflang?
Yes. Every language version must reference all others, including itself.
Can canonical point to a redirect?
No. Canonical should point to the final URL, not a redirect.
Does canonical-hreflang conflict affect SEO?
Yes. It can cause the wrong language version to be indexed, or pages to be excluded from the index.
How do I check for conflicts?
Use a canonical checker and hreflang validator. Check that canonical is self-referencing and hreflang has return links.
Can I use canonical and hreflang together?
Yes, if configured correctly. Canonical should be self-referencing, hreflang should have return links.
What if only some languages are affected?
Check those language versions for canonical and hreflang errors. Fix them individually.
