Hreflang

Why it matters

Without it, a multilingual site risks the wrong language version ranking for a given search, or worse, being treated as duplicate content across its language variants, diluting ranking signal that should be consolidated per language rather than split or confused between versions. It also has to be paired correctly with genuinely distinct content per language, since hreflang tells search engines which version to show but does nothing to fix content that was machine-translated poorly or left identical across supposedly different language versions. It also needs to include a self-referencing tag on every page, each language version pointing to itself as well as to every other version, which is easy to miss when the tags are added incrementally over time.

What goes wrong when it's handled badly

A common mistake is implementing hreflang tags that do not reciprocally reference each other correctly, every language version has to link to every other version including itself, and a broken or one-directional set of tags is often silently ignored by search engines rather than erroring visibly, which makes the mistake easy to miss without deliberately testing it. A concrete example is an English page correctly tagged as targeting English-language visitors while its supposed Arabic counterpart, still under construction, is left live and indexed with placeholder text, actively misdirecting Arabic searchers to an incomplete page. Testing the full set of hreflang tags with a validation tool before publishing, rather than assuming each one was added correctly by hand, is what catches a broken reciprocal link before it costs ranking. Keeping hreflang tags automatically generated from a single source of truth, rather than maintained by hand across many pages, is what prevents this kind of drift at scale.