What it is
hreflang can be delivered in the HTML, the sitemap or HTTP headers, and if the sets disagree Google has conflicting instructions. I keep hreflang in one place and make it complete there. Different hreflang sets in different delivery methods. Conflicting annotations reduce reliability.
Why does hreflang conflict across html/sitemap/header matter for AI search?
Conflicting annotations reduce reliability.
How do you fix it?
Use one consistent method/set.
How do you find it on your site?
- Check which delivery methods carry hreflang: HTML head, sitemap, headers.
- Compare the sets for differences.
- Consolidate onto a single method and remove the others.
- Re-validate that the one source is complete and reciprocal.
Which ranking and citation factors does it touch?
Conflicting hreflang sets can cause Google to ignore them. A single consistent source keeps the localisation signal reliable.
What is the impact?
Low-medium. Inferred.
What is the evidence?
Keep hreflang consistent across delivery methods. Google Search Central, Tell Google about localized versions (hreflang)
Sources
Frequently asked questions about hreflang conflict across html/sitemap/header
What does "hreflang conflict across HTML/sitemap/header" mean?
Different hreflang sets in different delivery methods.
How do you fix hreflang conflict across HTML/sitemap/header?
Use one consistent method/set.