Running Arabic and English campaigns in the UAE, and what actually changes

W3Techs put Arabic at 0.6% of websites with a known content language on 11 October 2026, ranked nineteenth, level with Hungarian. English sat at 49.5%. The demand side does not look anything like that ratio.

Arabic is the official language of the UAE. The government’s own fact sheet adds that in the courts the other five official languages are Chinese, English, French, Hindi and Russian, and that Bengali, Farsi, Malayalam, Turkish and Urdu are widely spoken. So this is not a two-language market with a long tail bolted on. It is a market where two languages carry the commercial search and a dozen more carry conversation.

What that means in practice is that a decent Arabic page competes against fewer decent Arabic pages. We have seen the same keyword cost less and rank faster in Arabic on accounts where the English version was a bloodbath. That advantage disappears the moment you publish machine translation, because then you are one of the bad Arabic pages.

Google’s guidance on multi-regional sites is explicit. It “recommends using different URLs for each language version of a page”, and it tells you not to use “cookies or browser settings to adjust the content language on the page”. One URL that swaps its own text is the single most common mistake we find on UAE sites.

Pick one of three structures. A country domain such as example.ae, a subdomain such as ar.example.com, or a subdirectory such as example.com/ar/. Google lists all three as workable and marks URL parameters as not recommended. We put Arabic in a subdirectory on nearly every build, because it inherits the domain’s authority and it is the cheapest to maintain.

Do not redirect people by their browser language. Google’s wording is to “Avoid automatically redirecting users from one language version of a site to a different language version of a site”, and warns that such redirects “could prevent users (and search engines) from viewing all the versions of your site”. Put a language switch in the header and let people choose. An Emirati executive reading English by preference will be annoyed by your helpful redirect.

Three annotation methods exist, HTML tags, HTTP headers and sitemaps, and Google says “The three methods are equivalent from Google’s perspective” while advising against using all three at once. We use HTML link tags and nothing else, so there is one place to look when something breaks.

The return link rule is the one that catches people. Google states that “If two pages don’t both point to each other, the tags will be ignored”, and that “Each language version must list itself as well as all other language versions”. So the Arabic page and the English page carry an identical block of tags, including a self-reference. Miss the self-reference and the set is silently discarded.

Codes come from ISO 639-1 for language and ISO 3166-1 Alpha 2 for region, and Google warns that “You can’t specify the country code by itself” and that values such as EU, UN and UK have no effect. For a UAE site we use en-AE and ar-AE, plus x-default, which Google describes as the value “used when no other language/region matches the user’s browser setting”.

Our multilingual SEO work starts with a validation pass on exactly these four things, because a broken hreflang set makes every other change look like it failed.

Translate your English keyword list and you will target words nobody searches. Arabic search splits across Modern Standard Arabic, which people write, and Gulf dialect, which people speak and sometimes type. Buyers also mix scripts, typing English brand names in Arabic letters and Arabic words in Latin letters, and both versions carry volume.

Then there is the plural and the definite article. The same noun appears with and without al, with different case endings, and search tools treat those as separate terms even when a reader would not. We build the Arabic list from scratch inside Keyword Planner with the language and location set to the UAE, then hand it to a native speaker to strike the words that are technically correct and commercially dead.

Volumes come out smaller than the English equivalents on most commercial terms, and that is fine. The question is not which list is bigger. It is which list has nobody competent competing on it.

Mirroring the page is not a CSS flag you set and forget. The container takes dir=”rtl”, the navigation flips, progress arrows reverse, icons that imply direction have to be redrawn, and anything positioned with left or right in pixels has to move to logical properties. Charts keep their axis order, which looks wrong until you see an Arabic newspaper do the same thing.

Numbers, prices and Latin brand names stay left to right inside right-to-left text. So a line that reads as Arabic with AED 1,250,000 in the middle of it contains two directions, and if the markup is sloppy the comma lands on the wrong side of the number. Test with real prices, not with placeholder text.

Fonts are the other trap. Poppins, which we use across new DigiStreet sections, has no Arabic coverage at all, so an Arabic page needs a separate face chosen to sit at a similar weight and height. Pick it before the design is signed off, because Arabic script needs more vertical room and the line height that looked tidy in English will feel cramped.

Google Ads decides which language a user knows from several signals. For Search it uses “search term language, the user’s language settings, and preferences”. On the Display Network it “may detect and look at the language of pages or apps that someone is visiting”. On YouTube it reads “the language preference that someone sets on the YouTube homepage” along with browser language, location and browsing history.

The sentence that matters for your copy is this one. Google says “We prioritize ads that match the user’s search term language”, and from September 2026 “Search ads will automatically match based on the language of your ads”, with “No action is required by advertisers for this change”. Read it twice. The language of your ad text is now doing the targeting work.

Which means two separate campaigns, one per language, with real copy in each. Not one campaign with both languages in the same ad group, where the budget drifts to whichever language the algorithm finds cheaper. Separate campaigns let you bid differently, pause one without touching the other, and read the cost per lead by language. The same split applies to Meta campaigns, where the creative and the form both need an Arabic version.

A native Arabic speaker reads every page and every ad before it goes live, and they are allowed to rewrite rather than correct. The three things they change most are formality, which is usually pitched too stiff by translators, the call to action, which rarely survives a literal translation, and the first line, which in Arabic marketing copy carries a different kind of weight.

Give the reviewer context, not just text. They need to know who the buyer is, what the offer is and what the page is competing against, otherwise you get grammatically perfect copy that sells nothing. We send the English page, the keyword list and the reason the page exists.

Nothing machine-translated goes live. Not as a placeholder, not as a stopgap for a launch date. A placeholder Arabic page gets indexed, gets judged, and then has to earn its way back.

Country reporting hides the thing you need to see. A UAE line in your analytics tells you nothing about whether the Arabic side is working, because both languages live in the same country. Split it by hostname or path, so /ar/ reports separately, and split your Search Console reporting the same way.

On paid, report cost per lead by language and by platform in the same table every month. On social in Dubai the Arabic creative often carries a lower cost per lead and a lower lead quality, or the reverse, and you cannot tell which until the numbers sit side by side for three months.

Validate hreflang every month, not once at launch. Developers push code, plugins update, and a self-referencing tag disappears without anybody noticing until rankings in one language quietly go flat. We put it on the same monthly checklist as the Dubai SEO and Dubai marketing reporting, because it is the cheapest check on the list and the most expensive one to skip.