English-Arabic Hreflang for UAE Websites: Implementation Guide

Direct answer: An English-Arabic UAE website needs a separate crawlable URL for every intended language version, reciprocal hreflang links between true counterparts, and a visible language switch. Each genuinely translated page should normally use its own self-referencing canonical. Do not force a redirect based only on a visitor’s location or browser language, and do not present boilerplate-only translation as a complete Arabic experience.

hreflang is a signal that helps Google associate localized versions; it is not a canonicalization directive, a ranking guarantee or a substitute for crawlable content. Manage duplicate or near-duplicate same-language regional URLs separately. Google determines a page’s language from its visible content rather than from the URL or lang attribute alone.

Give each language a stable URL

Use a structure your team can maintain, such as /en/ and /ar/ subdirectories. Subdomains and separate country domains can also work, but the important requirement is a distinct, stable URL that loads without a cookie, form submission or browser-language header.

Avoid swapping English and Arabic on one URL according to Accept-Language. Google explains that Googlebot usually crawls from the United States and generally does not send that header, so an adaptive-only version may not be discovered reliably. Every language URL should also be reachable through ordinary HTML links.

Translate the page, not just its template

The main copy, navigation, form labels, validation, breadcrumbs, titles and important image text should consistently use the selected language. An Arabic menu around an English article is not a complete Arabic version. Localize material details such as currency, availability, legal wording and contact instructions only when the underlying facts genuinely differ.

For Arabic, set the document language and base direction explicitly, for example <html lang="ar" dir="rtl">. The W3C notes that language and text direction are separate concepts: lang does not automatically establish right-to-left presentation. Test mixed Arabic and English text, numbers, product codes, punctuation, forms, icons and directional controls. Use targeted direction markup for mixed-script fragments rather than relying on visual CSS alone.

Map only true equivalents

Maintain a simple language matrix with one row per topic or function. Record its English URL, Arabic URL, canonical, index status, translation status and intended hreflang code. Connect pages only when they serve the same purpose. Do not map every untranslated English page to the Arabic homepage.

If an Arabic equivalent does not exist, omit that alternate. The language switch can explain that the page is unavailable in Arabic or link to a relevant language hub, but that hub should not be declared as the page’s equivalent.

Use valid language and region codes

Use an ISO 639-1 language code such as en or ar. Add an ISO 3166-1 Alpha-2 region only when the version is genuinely aimed at that country. Valid UAE combinations include en-AE and ar-AE; AE by itself is invalid because a region cannot replace the language.

Do not invent market codes. For example, Google does not treat UK, EU or UN as regional targeting codes; use GB for the United Kingdom. If one Arabic version serves Arabic readers generally, ar may be more accurate than duplicating it across several regional annotations. A language-only catchall can also sit alongside specific regional versions.

Make every hreflang set reciprocal and self-inclusive

Each member of a language set should list itself and every alternate. If the English page points to Arabic, the Arabic page must point back. Google may ignore annotations that lack return links. Use absolute final URLs and keep the same set on every equivalent page.

<link rel="alternate" hreflang="en-AE" href="https://example.com/en/service/">
<link rel="alternate" hreflang="ar-AE" href="https://example.com/ar/service/">
<link rel="alternate" hreflang="x-default" href="https://example.com/language-selector/">

x-default is optional. It is useful for a neutral language selector or fallback page shown when no listed language-region combination matches. It does not repair an incomplete or conflicting set.

Keep canonicals aligned with the language version

For distinct English and Arabic pages, the English URL should normally canonicalize to itself and the Arabic URL to itself. Canonicalizing Arabic to English asks Google to consolidate the Arabic URL while hreflang presents it as a localized alternate—two different intentions.

There is one important nuance: genuinely duplicate same-language regional pages may need one preferred canonical combined with regional hreflang. A canonical is still a hint, and Google can select a different representative. Do not apply that exception to a fully translated English-Arabic pair.

Before diagnosing hreflang, confirm that each intended alternate returns a normal page, is crawlable, is not marked noindex, and does not redirect to a different language. Those conditions make the page eligible to be discovered and considered.

Choose one controlled implementation method

Google supports three equivalent approaches: HTML <link> elements, HTTP headers and XML sitemap annotations. Using all three provides no Search benefit and creates more places for mismatches. HTML is straightforward for ordinary pages, HTTP headers suit non-HTML files, and sitemap annotations can be easier on large platforms.

When using HTML, place one separate <link rel="alternate" hreflang="…"> element per variant in a well-formed <head>. Do not combine hreflang with media or other alternate-representation attributes in the same element. On WordPress, inspect the rendered output rather than assuming a multilingual or SEO plugin configured it correctly. Two plugins can produce duplicate, stale or contradictory sets, especially when one translation is unpublished.

Offer choice instead of forced redirects

Provide a visible switch that links directly to the corresponding page. A language suggestion based on browser settings can help, but users should be able to decline it and access every version. Google’s international-site guidance warns that automatic redirects can prevent both people and search engines from seeing all versions.

Run a pair-by-pair release check

1. Open the English and Arabic URLs without cookies and confirm each returns the intended page.
2. Inspect the rendered <head> for one canonical and one complete, matching hreflang set.
3. Confirm reciprocity, self-references, absolute URLs and valid language-region codes.
4. Check robots directives, response status, redirect targets and sitemap inclusion.
5. Test the language switch and same-language internal navigation.
6. Review Arabic direction, mixed-script content and forms on mobile and desktop.
7. Use URL Inspection on representative pages after release to compare Google’s selected canonical and rendered output.

If annotations appear in JavaScript-generated markup, use a rendering diagnostic workflow to compare raw HTML, the browser DOM and Google’s rendered version. Keep both canonical language URLs in clean XML sitemaps.

Measure and maintain each language separately

Segment Search Console pages and queries by language folder, country and device. Compare qualified actions by landing-page language in analytics. A weaker Arabic result can reflect translation quality, mobile layout, service availability or tracking—not simply keyword selection.

Log every new pair, removed pair and changed target. When one URL moves, update its equivalent, reciprocal annotations, switch links and sitemap entry in the same release. PAKWM’s website development service can support bilingual templates, while its SEO service covers international indexing and technical QA.

Primary sources

• Google: tell Google about localized versions
• Google: managing multilingual and multi-regional sites
• Google: canonicalization and duplicate URLs
• Google Search technical requirements
• W3C Internationalization: structural markup and text direction

Planning an English-Arabic website? Request a quote from PAKWM and share the current URL matrix, translation workflow and target markets.