English-Arabic Website SEO in the UAE: Getting Bilingual Signals Right

Most UAE businesses serve customers in English and Arabic, but most bilingual websites quietly sabotage one of the two languages. The usual result: the English pages rank a little, the Arabic pages not at all, and Google occasionally shows the wrong language to the wrong searcher. This guide covers the signals that make bilingual SEO work in the UAE.

Why bilingual sites underperform in the UAE

Three patterns cause most of the damage:
• One URL, two languages. A language switcher that swaps text on the same URL means Google sees a mixed-language page and ranks it for neither language properly.
• Machine-translated Arabic. Word-for-word translation carries English phrasing into Arabic, misses how Arabic speakers actually search, and reads as low quality — to users and to search engines.
• Missing or broken hreflang. Without hreflang pairs, Google treats the English and Arabic versions as unrelated (or worse, duplicate) pages and picks one to show — sometimes the wrong one.

The URL structure that works

Use a clear, crawlable separation — one language per URL:
• Subdirectory (recommended): `example.com/services` and `example.com/ar/services`. One domain, one authority pool, easiest to maintain.
• Subdomain: `ar.example.com`. Works, but splits some signals and adds setup overhead.
• Separate domain: rarely worth it in the UAE unless the brands genuinely differ.

The subdirectory approach keeps every backlink you earn feeding both languages. This matters even more on a young domain, where authority is scarce — the same principle behind an SEO-friendly website structure.

Hreflang: the pairing signal

Each English page should declare its Arabic sibling and vice versa, plus itself:

The rules that trip people up:
• Hreflang must be reciprocal — if the English page points to the Arabic one, the Arabic page must point back, or Google ignores the pair.
• Point hreflang at the canonical URL of each version, never at a redirect.
• `x-default` tells Google which version to show searchers who match neither language.
• Pages that exist in only one language simply have no pair — do not point hreflang at an untranslated page.

Arabic content is a rewrite, not a translation

Arabic searchers phrase queries differently, use different commercial vocabulary, and often mix Arabic script with English brand terms. Practical rules:
• Research Arabic keywords separately — the Arabic query for a service is rarely a literal translation of the English one.
• Rewrite headlines and CTAs for Arabic reading patterns; keep proof points (prices, timelines, locations) identical so the two versions never contradict each other.
• Set `dir="rtl"` and `lang="ar"` properly, and design the layout to mirror — a left-to-right layout with Arabic text pasted in signals low effort.
• Keep metadata in the page language: Arabic pages need Arabic titles and meta descriptions.

Signals that must stay consistent across both languages

Search engines cross-check the two versions. Keep these identical: business name (NAP), prices, schema.org data (translate text values, keep the structure), and internal-link architecture — if the English services page links to five sub-services, the Arabic one should link to the same five Arabic sub-services. This consistency is also what AI answer engines look for when citing a business.

Rolling Arabic out without hurting existing English rankings

If your English site already ranks, add Arabic incrementally:

1. Start with the pages that get UAE Arabic-language search demand — usually the homepage, core service pages, and contact. 2. Add hreflang pairs as each Arabic page goes live, not before. 3. Submit both language versions in your sitemap and check indexing in Search Console under a separate filter for `/ar/`. 4. Watch for cannibalization: if an Arabic page starts appearing for English queries, the hreflang pair is usually broken.

A full pre-launch pass on the Arabic section is the same discipline as an SEO checklist before launching any website — crawlability, metadata, internal links, and schema, just in the second language. And if you serve different emirates in different languages, bilingual pages combine naturally with local service pages for Abu Dhabi and Dubai.

Arabic keyword research in practice

The single most valuable habit in UAE bilingual SEO is researching Arabic queries as their own project, never as translated English. A few practical realities:
• Dialect and register matter. Gulf Arabic speakers often search in Modern Standard Arabic for formal services but slip into dialect for everyday needs. The right target sits between the textbook term and how people actually type.
• English brand terms survive in Arabic queries. UAE searchers routinely mix scripts — searching an Arabic service phrase alongside an English brand or product name. Your Arabic content can and should accommodate that blend rather than forcing pure Arabic.
• Search volumes look smaller — and convert harder. Arabic queries frequently show lower volume than their English equivalents, but they are less contested and often reach decision-ready local buyers. Judge them on intent, not just the number.
• Validate against the live SERP. Search your candidate Arabic terms in a UAE context and read what already ranks. If the results are informational when you sell a service, the intent is wrong regardless of volume.

Feed the winners into Arabic titles, H1s, and body copy written for those phrasings. This is the same one-intent-per-page discipline behind a good SEO-friendly website structure, applied independently to each language.

Measuring both languages separately

If you report English and Arabic together, you will never see which one needs help — averages hide the language that is quietly failing. Keep them separate:
• Filter Search Console by the `/ar/` path to track Arabic impressions, clicks, and queries as their own dataset, and do the same for the English section.
• Watch for cross-language leakage. If an Arabic URL starts collecting impressions for English queries (or vice versa), a hreflang pair is almost certainly broken — the diagnostic step from the rollout section above.
• Compare intent, not just totals. Arabic may show fewer clicks but a stronger enquiry rate; connect this to actual leads using the GA4 lead-tracking setup, segmented by page path so each language's real contribution is visible.
• Track them on their own timelines. A newly launched Arabic section is a young site in Google's eyes even if the English one is established; give it the same patience and indexing checks you would give any new launch.

Related resources