Hreflang Tags and Multilingual SEO Guide

Hreflang is an HTML attribute that tells Google which language and country each version of a page is for. Set up correctly, it means someone in Dubai searching in Arabic gets your Arabic UAE page, and someone in Riyadh searching in English gets your English Saudi page. If it is missing or broken, Google may show the wrong version, and your local pages can end up competing with each other.

Hreflang is one piece of multilingual SEO. A site that serves several countries and languages also needs a clear URL structure, properly localized content, and location signals that agree with each other. For most UAE brands that means Arabic and English to begin with, and often other GCC markets later.

What Are Hreflang Tags?

Hreflang tags link the different language or regional versions of a page and label each one with a language, and optionally a region. Visitors never see them. Google reads them when deciding which version to show in search results.

A hreflang value combines a language code with an optional region code. ar means Arabic for any region. ar-AE means Arabic for users in the UAE. en-SA means English for users in Saudi Arabia. According to Google Search Central, the language must use an ISO 639-1 code and the region must use an ISO 3166-1 Alpha-2 code.

Use hreflang when you have the same content in different languages, such as Arabic and English versions of a service page. It also applies when one language serves several regions, for example English pages for the UAE and Saudi Arabia with different prices or contact details. Google supports it, too, for pages where only the template, such as the menu and footer, is translated.

How Hreflang Works: The Rules Google Enforces

Every version in a hreflang set has to list every other version, plus itself. Google Search Central names missing return links as a common hreflang mistake: if page A points to page B and page B doesn’t point back, Google may ignore the tags.

Google accepts hreflang in three places and treats them the same:

HTML <link> tags in the page <head>.
HTTP headers, which suit non-HTML files such as PDFs.
XML sitemap entries, which work well for large sites.

Using more than one adds nothing, so pick the one your team can keep up to date. On large sites with many language versions, a sitemap is usually easier than editing the head of every page.

A few more rules catch people out. URLs in hreflang annotations must be fully qualified, including the https:// protocol. Region codes cannot stand alone, so AE on its own is invalid while ar-AE or en-AE is valid. Google also notes that reserved codes such as UK and EU have no effect, so a page for British users should use en-GB.

A hreflang example for a UAE and Saudi site

Here are the tags for one service page that exists in Arabic and English for both the UAE and Saudi Arabia. All four pages carry the same full set.

Each page lists itself and the other three versions, plus an x-default fallback. If you later add a Kuwait version, every existing page needs the new tag as well.

What x-default Does

The x-default value tells Google which page to show when a user’s language or region does not match any of your versions. It is usually a country or language selector page, or the version you consider your global default.

For a UAE brand with Arabic and English pages, x-default might point to a homepage where visitors pick their language. Someone in Egypt searching in French would land there instead of on a page in a language they didn’t search in. Google’s guidance says that x-default needs no language code, because it is a fallback, not a language version.

Multilingual SEO vs International SEO

Multilingual SEO covers content in more than one language. International SEO covers content for more than one country. A UAE site that targets several GCC markets in Arabic and English is doing both.

Which one you are doing changes the setup. A site that serves Arabic and English to UAE users only is mainly a multilingual SEO project. It needs translated content, separate URLs for each language, and hreflang tags such as ar-AE and en-AE. A site that serves English content to users in the UAE, Saudi Arabia, and Kuwait is mainly an international SEO project. It needs region-specific hreflang values and localized details for each country, such as currency, phone numbers, and addresses.

Google Search Central recommends using a separate URL for each language version rather than switching languages with cookies or browser settings. If the same URL shows different languages to different users, Google may only index one of them.

ccTLD vs Subdirectory vs Subdomain: Choosing a Site Structure

Your URL structure affects how clearly Google can tell which country a section targets, and how much upkeep each market takes. Google Search Central describes four options. Your budget, team size, and how separately each market needs to run will decide which one fits.

Structure	Example	Main Strengths	Main Drawbacks
Country code domain (ccTLD)	example.ae	Clearest country signal	Higher cost, separate sites to maintain, targets one country each
Subdirectory on a generic domain	example.com/ae/	Easy setup, single host, low maintenance	Weaker country signal in the URL, harder to separate markets
Subdomain on a generic domain	ae.example.com	Easy setup, can use different servers	Users may not know if ae means language or country
URL parameters	example.com?loc=ae	None that Google recommends	Not recommended by Google

When a ccTLD makes sense

A country code domain such as .ae is the clearest way to tell Google a site targets one country. It suits brands with a local team, local stock, and the budget to run a separate site. Each ccTLD is its own website, so content, technical setup, and backlinks have to be built separately for each one.

When a subdirectory makes sense

Subdirectories such as /ae-en/ and /ae-ar/ keep every market on one domain. They share the authority the main domain has built and run on one platform, so adding a market is mostly a content job. For a UAE business expanding into other GCC countries, subdirectories with correct hreflang tags are usually the most practical setup.

When a subdomain makes sense

Subdomains such as ae.example.com make sense when each market needs its own hosting or platform. For most marketing sites they add setup work without the clear country signal a ccTLD gives.

Other Geotargeting Signals Google Uses

Geotargeting is how search engines work out which country a page is meant for. Hreflang is one signal. Google Search Central lists several others, and you want them all to agree.

A ccTLD is a strong signal by itself. Server location counts for less, and Google notes it can be misleading when a site runs on a content delivery network. On the page, a local address and phone number, local currency, and content in the local language all help. So do links from local websites and a Google Business Profile.

Google also notes that it ignores location meta tags such as geo.position. Adding them to a page does not improve geotargeting.

Google advises against redirecting users automatically based on their IP address or browser language. Googlebot mostly crawls from the US, so automatic redirects can hide your other versions from it. Add a visible language switcher instead, so people and crawlers can reach every version.

Common Multilingual SEO Mistakes on Arabic and English Sites

These multilingual SEO mistakes come up often on Arabic and English sites, and most are quick to fix once you find them.

Translating instead of localizing

Arabic translated word for word from English rarely reads naturally, and it often misses the terms Arabic speakers actually type into Google. Do separate keyword research in Arabic instead of translating the English keyword list, and adapt examples, prices, and references to the local market.

Pointing canonical tags at another language

If the canonical tag on an Arabic page points to the English version, you are telling Google the Arabic page is a duplicate, and it may drop out of search results. Each language version should normally have a canonical tag pointing to itself, with hreflang tying the versions together.

Leaving untranslated duplicate pages live

Launching an Arabic section while the body text is still in English can get those pages treated as duplicates. Google Search Central says localized pages only count as duplicates when the main content is untranslated, so wait until it is translated before you publish.

Ignoring right-to-left layout

Arabic pages need a right-to-left layout, set with the dir=”rtl” attribute and matching CSS. Misaligned forms, broken layouts, and icons pointing the wrong way make pages harder to use. Check Arabic templates on mobile, where these problems are easiest to spot.

Mismatched hreflang and URLs

Hreflang tags that point to redirected, broken, or non-canonical URLs weaken the whole set. Every URL in a hreflang annotation should return a 200 status code and be the canonical version of that page.

International SEO Checklist

Use this checklist before launching or auditing a multilingual or multi-country site:

Confirm one URL structure for all markets, such as subdirectories for each country and language.
Give each language and region version its own URL.
Add hreflang tags with valid ISO language and region codes.
Include a self-referencing tag on every page.
Confirm every page links back to every other version in its set.
Use fully qualified URLs, including https://.
Add an x-default value pointing to a selector or global page.
Point each page’s canonical tag to itself, not to another language.
Localize keywords, currency, contact details, and examples for each market.
Set dir=”rtl” on Arabic pages and test layouts on mobile.
Replace automatic IP-based redirects with a visible language switcher.
Check every hreflang URL returns a 200 status code.
Review international performance in Google Search Console by country and by page.

FAQ

What is the difference between hreflang and the HTML lang attribute?

Hreflang tells search engines which alternate versions of a page exist and which audience each one serves. The HTML lang attribute declares the language of the current page for browsers and assistive technologies. Google Search Central states that it does not use either hreflang or the lang attribute to detect a page’s language, relying on its own analysis instead.

Do I need hreflang if my site only has Arabic and English for the UAE?

Yes, it is still worth adding. Tags such as ar-AE and en-AE help Google show Arabic searchers the Arabic page and English searchers the English page. Without them, Google may show the wrong language version in some searches.

Is a ccTLD better than a subdirectory for international SEO?

It depends on how you run your markets. A ccTLD such as .ae gives the clearest country signal but means running a separate site for each market. A subdirectory structure shares one domain and is easier to scale, which often suits brands expanding across the GCC.

Can hreflang fix duplicate content between English sites for different countries?

It helps. Hreflang tells Google that similar English pages for the UAE and Saudi Arabia serve different audiences, so it can show the right one in each country. The pages will do better if they also differ in substance, with local prices, contact details, and market-specific information.

Hreflang and Multilingual SEO: How to Run One Site Across Countries and Languages