Hreflang connects equivalent pages for different languages or regions. It is an annotation for the right version of a page, not a substitute for translating content or fixing canonicals. Plan the URL pairs first, then test self references, return links and language codes.
Decision framework
| Step | Practical check |
|---|---|
| Make URL pairs | List each equivalent page and its intended language or language-region value. |
| Check indexability | Confirm pages return usable status and do not have conflicting noindex or canonical choices. |
| Add reciprocal sets | Each page lists itself and its alternatives with matching URLs. |
| Validate after release | Inspect rendered tags or sitemap entries and crawl a sample of pairs. |
How to make the decision
Use a row per page: source URL, locale code, canonical URL, status, alternates and reciprocal-check result. Example pair: /en-ae/service/ points to /ar-ae/service/ and both point back to themselves and each other. A one-way link is a failing row; add the missing return annotation and retest. If a regional page is missing, do not invent an alternate URL merely to complete the table. Choose one supported implementation method, such as HTML or sitemap, and keep it consistent.
Worked example
Synthetic three-row audit: an English UAE page and Arabic UAE page are live; the English page lists both, while the Arabic page lists only itself. A third UK page returns 404. The team adds the Arabic return link, removes the dead UK alternate until a real page exists, and confirms both live pages canonicalize to themselves. The corrected two-page set passes the reciprocal check.
What can change the answer
The language code must come first; a country code alone is invalid. Hreflang does not force Google to show a page or repair a wrong canonical.
Review checklist
- Does every live variant list itself and return links?
- Do URLs and codes match the actual content?
- Were status and canonical signals checked together?
Common question
Should we add hreflang before translation?
No. Publish usable localized pages first, then annotate real equivalents.
Next useful step
Return to the market decision if the proposed variants have no distinct purpose: International Search Expansion: Choosing Markets Before Translating Pages. For help applying this to a UAE business, see Megvi’s international SEO service. Bring the source records and the decision you need to make.
Source checked 26 October 2026: Google Search Central: tell Google about localized versions. Check the current platform interface and rules before acting.
Worked examples are illustrative unless a public source is explicitly named; they are not claimed Megvi client outcomes.
Ahmed Elneil
https://megvidigital.comAhmed Elneil is a certified digital marketer and entrepreneur with over 5 years of experience helping brands grow through Search Engine Optimization (SEO), paid advertising, and CRM automation.