hreflang: how language tags work on UAE multilingual sites

hreflang is an HTML attribute that tells search engines which language, and optionally which region, a page is written for, and where its versions in other languages live. When the tags are correct, a reader in Dubai who searches in Russian gets your Russian page, and a reader searching in English gets the English one.

The name comes from the hreflang attribute of the <link> element, which Google documents as the way to mark localized versions of a page. In the UAE, customers read English, Arabic, Russian and other languages. Any site that serves them in more than one language needs it.

How hreflang works

Each language version of a page carries a set of tags. The set lists every version of that page, including the page itself, with a language code and a full URL. Google reads the set, groups the pages into one cluster, and shows the version that fits the searcher's language and location.

Three rules make the cluster valid:

Every version lists every other version. If the English page points to the Russian page, the Russian page has to point back. Google's documentation says tags without return links may be ignored.
Every version lists itself. The self-reference is part of the set.
URLs are absolute. Write the full address with https://, for example https://example.com/ru/services/.

The ranking position stays the same. Google swaps one URL for another inside the cluster.

The code format

The value is a language code from ISO 639-1. You can add a region code from ISO 3166-1 alpha-2 after it:

Value	Meaning
`en`	English, any country
`en-AE`	English for readers in the UAE
`ar`	Arabic, any country
`ar-AE`	Arabic for readers in the UAE
`ru`	Russian, any country
`x-default`	Fallback page when no other version fits

The language always comes first. A region on its own, such as ae, is invalid. x-default usually points to a language picker, or to the version you want people to see when their language is not on your list.

You can place the tags in one of three spots:

In the <head> of each page, as <link rel="alternate" hreflang="…" href="…">. Small sites usually choose this.
In the HTTP header. Use it for files with no HTML head, such as a PDF price list in two languages.
In the XML sitemap, as xhtml:link entries under each URL. This suits sites with hundreds of pages.

Pick one method. Two methods with conflicting data give Google two answers to the same question.

Hypothetical example: a Dubai clinic in three languages

Hypothetical example: a dental clinic in Dubai runs its site in English, Arabic and Russian. Its implant page exists in all three:

https://clinic.example/en/implants/
https://clinic.example/ar/implants/
https://clinic.example/ru/implants/

All three pages carry the same block in their head:

<link rel="alternate" hreflang="en" href="https://clinic.example/en/implants/" />
<link rel="alternate" hreflang="ar" href="https://clinic.example/ar/implants/" />
<link rel="alternate" hreflang="ru" href="https://clinic.example/ru/implants/" />
<link rel="alternate" hreflang="x-default" href="https://clinic.example/en/implants/" />

Each page also has a canonical tag pointing to its own URL.

Now the clinic opens a branch in Riyadh with different prices. It adds ar-SA for the Saudi Arabic page and changes the UAE Arabic page to ar-AE. Every page in the cluster gets the new lines. A page left with the old block breaks the return links.

Where you need hreflang in the UAE

You need hreflang wherever the same page exists in more than one language. In the UAE that covers most hospitality, healthcare, legal, real estate and rental businesses that serve expats and tourists.

The Savage Media study of 537 Dubai restaurant and venue websites was checked on 13.10.2026. Of the 409 sites it analysed in full, 82 (20.0%) had an Arabic version, 50 (12.2%) had a Russian version and 38 (9.3%) had all three languages (full study). Every one of those sites needs hreflang.

Two bilingual sites I built show the scale. Moon Mars runs in English and Russian with 128 pages (case). Lucent Legal has 213 guides in Russian and 213 in English. At that volume nobody matches pages by hand, so the site build has to output the pairs. Before tagging anything, decide which pages get a version in each language. The guide on translating versus rewriting a RU/EN site covers that choice.

For the full build of an EN/AR/RU site, with RTL layout and URL structure, see the Savage Media journal guide.

hreflang vs canonical, lang and geotargeting

People confuse four related signals:

Signal	What it does	Where it lives
hreflang	Connects language versions of one page and tells Google which to show to whom	`<link>` in head, HTTP header or sitemap
Canonical	Names the main URL among duplicates in the same language	`<link rel="canonical">`
`lang` attribute	Declares the document language for browsers and screen readers	`<html lang="ar" dir="rtl">`
Country domain (`.ae`)	Signals that the whole site targets one country	Domain level

hreflang and canonical work together. Google treats a translated page as its own version in another language, so it keeps its own canonical. Browsers and screen readers use the lang attribute, and Google says it does not use it to pick a language version. An Arabic page needs lang="ar" and dir="rtl" for correct display, plus hreflang for search.

What not to do

Pointing the canonical to another language. If the Russian page is canonical to the English URL, you tell Google the Russian page is a copy. Google then tends to drop it and ignore the hreflang set.
Missing return tags. The English page lists the Arabic page, but the Arabic template was built separately and lists nothing. Google needs links in both directions.
Invented codes. en-UK is wrong because the region code is GB. ar-UAE is wrong because the code is AE. ae on its own has no language. Copy codes from the ISO lists.
Dead or redirected URLs in the set. After a redesign, old slugs often stay in the hreflang block. Every URL in the set should return status 200, be indexable and not redirect.
Forced redirects by IP or browser language. Google's documentation says Googlebot mostly crawls from US addresses. If you send visitors to a version based on location, Googlebot may only ever see the English pages. Give people a visible language link.
Tagging thin machine translations. hreflang will send Russian readers to a Russian page that reads badly. Edit the translation before you tag it.

hreflang mistakes on RU/EN/AR sites covers these errors in more detail.

How to check your hreflang

Open the page source of one page in each language and search for hreflang. The block should be identical across all versions and include a self-reference.
Crawl the site. A crawler such as Screaming Frog reports missing return links and URLs that do not return 200.
Compare canonicals. Each page's canonical should match its own URL.
Use URL Inspection in Google Search Console. Search Console has no dedicated hreflang report. URL Inspection shows the canonical you declared and the one Google selected. If Google picked the English URL for your Arabic page, the cluster is broken. Google Search Console describes the monthly routine.
Search in the target language. Switch the Google interface to Arabic or Russian and search for your brand. The result should show the matching version.

On a new multilingual site, put hreflang in the brief from day one as part of the website build. Adding it later means auditing every page pair.

Checklist

Every page with a translation has a hreflang block.
The block lists all versions, including the page itself.
Codes follow ISO 639-1 for language and ISO 3166-1 alpha-2 for region, language first.
x-default points to a sensible fallback.
All URLs are absolute, return 200 and do not redirect.
Each page's canonical points to itself.
One method only: head, HTTP header or sitemap.
Language switching uses a visible link, with no forced redirects.
Arabic pages carry lang="ar" and dir="rtl".
After every redesign or slug change, re-run the crawl and check return links.

GEO: how AI assistants choose which sources to cite. Clean language versions help them pick the right page.
Google Search Console: where you confirm which canonical Google selected for each language version.
hreflang mistakes on RU/EN/AR sites: a practical audit for sites in the UAE.
RU/EN site: translate or rewrite: which pages deserve a version in each language before you tag them.

Questions and answers

Do I need hreflang if my site has only one language?

No. hreflang connects two or more language or regional versions of the same page. A single-language site has nothing to connect, so the tags add no value.

Does hreflang improve my rankings?

No. Among pages that already rank, it lets Google pick the right language version, so an Arabic speaker sees your Arabic page in place of the English one.

Should I use ar-AE or plain ar for my Arabic pages?

Use plain ar if one Arabic version serves every Arabic speaker. Add a region such as ar-AE only when you run separate Arabic pages for different countries, for example the UAE and Saudi Arabia with different prices or services.

Can my web developer add hreflang to an existing site?

Yes, through the page head, HTTP headers or the XML sitemap. The work depends on whether every page has a clear counterpart in each language, so ask for a list of page pairs before the tags go in.