Build dedicated Arabic URLs (not a language switcher that swaps strings on the same URL), write native Arabic content from scratch instead of translating English copy, and ship a real RTL layout that flips icons, paddings, and form fields, not just the text direction. Get those three right and you have a chance in Google UAE. Get them wrong and you stay on page two no matter how much you spend on backlinks.
Why Arabic-first is different from "translated" in 2026
UAE search has shifted. Around 38% of consumer queries on Google.ae now come in Arabic script, and another 20% mix Arabic with English transliteration ("بيتزا near me", "Emirates ID renewal مكان"). Google's Arabic AI overviews rolled out across the Gulf last year, and they pull from sites with genuine Arabic depth, not auto-translated DeepL output.
Translated sites lose for a specific reason. Google reads sentence patterns and entity relationships in Arabic. A translated page has English structure with Arabic vocabulary on top. It reads wrong to natives and ranks below sites written in Arabic from the start. I have seen Dubai SaaS companies with DR 60 sit at position 8 for their main Arabic keyword while a Sharjah competitor at DR 22 sits at position 2, because the latter had a native writer producing original content for two years.
The technical foundation: URLs, hreflang, RTL
For URL structure, pick one of three patterns and commit:
example.ae/ar/subdirectory: cheapest to run, inherits domain authority, easiest to manage in Next.js or WordPress. This is the default I recommend for 90% of UAE businesses.ar.example.comsubdomain: useful when the Arabic site is run by a separate team with its own stack.example.aeversusexample.com: a UAE ccTLD gives a small but real geo-signal boost in Google UAE. Pair it with a/ar/subdirectory for the best of both.
Hreflang is where most Dubai sites quietly break. The minimum set you need:
<link rel="alternate" hreflang="ar-AE" href="https://example.ae/ar/page" />
<link rel="alternate" hreflang="en-AE" href="https://example.ae/en/page" />
<link rel="alternate" hreflang="ar-SA" href="https://example.ae/ar/page" />
<link rel="alternate" hreflang="x-default" href="https://example.ae/en/page" />
Add return tags on every page (the AR page must reference the EN page and vice versa). Validate in Google Search Console under the International Targeting report. If you are chasing Saudi traffic spillover, add ar-SA pointing to your UAE Arabic page; Google treats Gulf Arabic content as relevant across the GCC.
RTL is not a dir="rtl" attribute and a prayer. In Next.js, set <html dir="rtl" lang="ar"> based on the locale segment. In Tailwind, use the rtl: and ltr: variants for padding, margin, and flex direction. Mirror directional icons (arrows, chevrons, progress bars). Use logical CSS properties (margin-inline-start over margin-left) so one component works both ways.
For fonts, Cairo and Tajawal render well at UAE body sizes (14-16px). IBM Plex Sans Arabic is strong for editorial sites. All three are free, self-hostable, and tuned for screens. Avoid system Arabic fonts; rendering varies wildly across Safari, Chrome, and the Samsung browser.
Arabic SEO that actually moves rankings
Run keyword research in Ahrefs or Semrush with country set to UAE and keyword language to Arabic. Pull the main keyword (كلمة مفتاحية) and its synonyms; Arabic morphology means one English term often maps to 4-6 Arabic variants. Example pairs:
- "web development Dubai" (1,900/mo) maps to "تصميم مواقع دبي" (2,400/mo) and "تطوير مواقع الإمارات" (880/mo).
- "ERP software UAE" (720/mo) maps to "برنامج ERP الإمارات" (1,100/mo) and "نظام إدارة موارد المؤسسة" (390/mo).
UAE searchers mix scripts constantly. Target the pure-Arabic query but include transliterated brand names in the body. Set Article.inLanguage to ar (not ar-AE) and add dc:language metadata for older crawlers. Arabic FAQ schema earns rich results about 40% more often than the English equivalent.
Content that ranks for Arabic queries in UAE
Translation is the wrong frame. Adaptation is what you want. A direct translation of "We deliver enterprise-grade solutions" reads, in Arabic, like a 2008 government press release. A native writer would land on "نبني لك حلولاً تشتغل من اليوم الأول" (We build you solutions that work from day one). Different rhythm, same intent.
Hire human Arabic writers. Rates in the UAE start around AED 130-220 per 500 words for general business copy and AED 230-330 for legal, finance, or medical content. Use Modern Standard Arabic (MSA) for B2B, government-facing, and corporate pages; this is what Emirati nationals and educated GCC readers expect. Use Gulf flavour for retail, F&B, and consumer apps.
Plan for Saudi traffic. Around 30-40% of Arabic search traffic to UAE content sites comes from Saudi. Skip heavy Emirati slang, lean MSA with Gulf vocabulary, and you will rank in both markets.
Technical implementation choices
| Platform | RTL Support | Performance | Build Cost (AED) | Annual Maintenance |
|---|---|---|---|---|
| WordPress + WPML | Mature, plugin-driven | Average; needs caching | 4,500 - 18,000 | 7,200 - 18,000 |
| Webflow + Weglot | Limited; CSS hacks required | Good | 6,000 - 22,000 | 3,600 - 12,000 |
| Next.js + Sanity/Strapi | Full control via next-intl | Excellent | 15,000 - 60,000 | 14,400 - 36,000 |
WordPress is the right call under AED 20k when you have a content team that needs a familiar editor. Webflow works for marketing sites but its RTL story is patchy; expect custom code. Next.js with a headless CMS is the option for teams that need real Core Web Vitals, a custom design, or an app roadmap. Most freezone tech businesses we work with land on Next.js plus Sanity.
Common mistakes Dubai businesses make
- Machine-translating product names and category pages. Google indexes the garbage and your brand looks unprofessional.
- Missing hreflang return tags. One-way hreflang is treated as broken and effectively ignored.
- Setting
font-family: 'Inter'without an Arabic fallback. On Windows it falls back to default Arabic, which looks like a 2003 PDF. - Ignoring Bing. Bing holds 8-12% of UAE desktop search and is the default in many government offices. Submit your sitemap.
- Mirroring English layouts pixel for pixel. RTL is not "English flipped". Test with native readers.
- Forgetting the Samsung browser. It is the default on roughly 35% of UAE Android devices and renders Arabic differently from Chrome.
- No Arabic alt text on images. Easy win; almost everyone misses it.
