In the UAE you are dealing with at minimum two languages: English (business, information search) and Arabic (trust, purchase decision-making).
(01) Multilingualism is everything
Recommended structure: use subdirectories. For example: site.ae/en/ for the English version and site.ae/ar/ for the Arabic version.
Why this is better than a subdomain (ar.site.ae): because all link weight accumulates on the main domain and is passed to all language versions. Arabic pages benefit from links pointing to the English pages.
These are tags that tell Google: "This is the English version of the page and this is its Arabic counterpart."
(02) Hreflang is a must, not an option
The problem in Dubai: hreflang is misconfigured in 80% of cases. Errors in these tags lead to:
- Arabic pages ranking for English queries (and getting no clicks)
- English pages showing to Arabic-speaking users
- Google ignoring one language version entirely, treating it as a duplicate
What to check:
- Every English page has a link to its Arabic version and vice versa
- Correct codes are used: en-ae for English (UAE) and ar-ae for Arabic (UAE)
- No broken links in hreflang (no tag pointing to a 404 page)
Arabic is written right-to-left (RTL). If your Arabic version is simply translated text in a left-aligned layout, users will leave.
Google factors in behavioural signals.
Poor layout = high bounce rate = drop in rankings.
(03) Adapting for Arabic script (RTL)
Navigation should mirror the English version: logo on the right, menu on the left
Icons and arrows should point in the opposite direction
Forms and buttons should be right-aligned
Local specifics: structure for the UAE market
Dubai and the UAE as a whole have a unique audience structure, which dictates special requirements for website architecture.