Applying hreflang only to equivalent localized pages

Map genuine equivalents before adding annotations

Create a mapping between pages that represent the same underlying content for different languages or regions. Use appropriate supported language and region codes and ensure the relationships are implemented consistently. Do not connect unrelated service or country pages simply because they target different markets. The annotation should describe a real alternative the visitor could use.

Worked example

Illustrative scenario; not a claim of measured client results.

An English service overview and its Arabic translation can form an equivalent pair when both explain the same offering. A UK delivery article and a Dubai company page may address different questions and should not automatically be paired. Review the content first, then implement the relationship. Keep canonical behavior aligned with the intended localized versions.

Checks, limitations and next decisions

Check that each referenced URL is reachable and that reciprocal references are present where required by the chosen implementation. Recheck mappings when pages are moved or translations are retired. Use official documentation for exact syntax and supported values. An annotation cannot compensate for missing or inaccurate localized content; it helps describe versions that actually exist.

A practical starting point

Work through these checks in order. Use the results to decide what needs to change in your own workflow.

1. Identify genuine alternate versions of the same page.
2. Use valid language and region codes with reciprocal references.
3. Check that each referenced URL is live and self-consistent.

A mistake to avoid

Do not connect different articles merely because they target different countries.

How to check progress

Validate the alternate graph and maintain it when a version is moved or removed.