Contents11
- The core difference: different queries, not different words
- Modern Standard Arabic, dialect, and the gap between them
- Content: written, not converted
- The technical layer
- Hreflang, done properly
- URL structure
- Right-to-left is a design problem
- Where the opportunity actually is
- Measuring separately
- What to do if you have a translated site already
- Common questions
The most common Arabic SEO project we are asked to fix looks like this. A UAE company translated its English site into Arabic, added it under an /ar/ folder, and waited. Two years later it ranks for nothing, receives almost no traffic, and is quietly cited internally as evidence that “Arabic does not work here”.
Arabic works here. Translation does not.
The distinction matters commercially, because in most UAE categories the Arabic search field is considerably less contested than the English one. A page that would take eighteen months to rank in English can rank in Arabic in a fraction of that, against a fraction of the competition.
The core difference: different queries, not different words
English and Arabic speakers in the UAE search for the same services using genuinely different query structures, not translated equivalents.
An English speaker searches “dental implant cost Dubai”. An Arabic speaker looking for the same thing might phrase it around the procedure differently, might include the emirate rather than the city, might use a colloquial term for the treatment that no dictionary would give you, and might not include a price word at all because the expectation of what a search returns is different.
This is why translation fails at the first step. You are not translating the answer, you are guessing the question — and getting it wrong.
The correct process is to build the Arabic keyword set natively. Arabic autosuggest, Arabic SERP analysis, Arabic-speaking researchers, and competitor analysis of Arabic-ranking sites. Then map it against your English clusters to find the gaps. Not the reverse.
Modern Standard Arabic, dialect, and the gap between them
Arabic search in the Gulf sits across three registers, and the practical implications differ.
Modern Standard Arabic is what most people type for formal and commercial searches. It is the safe default for your page content.
Gulf and Levantine dialect is how people speak, and it leaks into search for consumer and colloquial categories — food, beauty, everyday services. Worth researching and worth including in FAQ sections, where informal phrasing sits naturally.
Latin-script transliteration is everywhere in the UAE and widely underestimated. Users type Arabic words in Latin characters, or mix languages within one query. “afdal doctor Dubai” and “shisha near me Sharjah” are real patterns. These queries are almost entirely unoptimised for, which makes them cheap to win.
Also relevant: diacritics are usually omitted in search, and Arabic has multiple orthographic variants for certain letters that users type inconsistently. Your content should be written in the standard form, but your keyword research needs to account for the variants people actually type.
Content: written, not converted
Arabic content that reads as translated is obvious to an Arabic reader within a sentence or two, and it damages trust before it damages rankings.
Three things change when writing natively.
Structure and rhythm. Arabic prose has different conventions around sentence length, connectives and how an argument is built. A literal rendering of English structure reads stiff.
Cultural specificity. References, examples, holidays, and the assumed context all shift. A guide referencing a Western tax year or a Northern-hemisphere seasonal cycle signals immediately that nobody thought about the reader.
Formality register. Arabic business communication carries different expectations around formality than English does. Getting this wrong reads as either cold or unprofessionally casual.
Use machine translation for a first pass if you like. Do not publish it. A native editor rewriting is not a luxury step, it is the step.
The technical layer
Hreflang, done properly
This is where most bilingual UAE sites break.
You need reciprocal hreflang tags across both versions, with correct codes: ar-AE and en-AE for UAE-targeted content, and an x-default pointing to your preferred fallback. Every Arabic page must reference its English counterpart and vice versa.
Common failures we find: hreflang on some pages but not others, non-reciprocal tags, pointing to redirecting or non-canonical URLs, and — very common — hreflang implemented correctly while the canonical tags contradict it.
URL structure
Subdirectories (site.com/ar/) are the right default for most UAE businesses. They consolidate domain authority, are simpler to maintain, and are what Google handles most predictably.
Subdomains and separate ccTLDs both split your authority, which is exactly what a business with limited link equity cannot afford.
Whether to translate the URL slugs themselves is a judgement call. Arabic-script slugs are technically fine and can help relevance; transliterated Latin slugs are easier to share and debug. Pick one and be consistent.
Right-to-left is a design problem
This is where “Arabic version” projects usually become expensive, and where cutting corners is most visible.
RTL is not a CSS flag. Layout mirrors, navigation flips, icons that imply direction reverse, form fields realign, and mixed-direction content — an Arabic sentence containing an English brand name or a number — needs handling.
Arabic typography also needs actual attention. Latin fonts with Arabic fallbacks produce genuinely ugly results. Line height, letter spacing and font choice all need setting for Arabic specifically. It is the difference between a site that looks like it was made for Arabic readers and one that looks like it was made for someone else.
German Medical Center is the clearest example we have published: two disconnected sites rebuilt as one bilingual WordPress platform, with right-to-left layouts, Arabic type properly set and hreflang serving each reader the correct language. Qualified enquiries rose 288 per cent. Our web design and development team treats Arabic as a design requirement from the first wireframe for exactly this reason.
:quality(82))
Where the opportunity actually is
Categories where Arabic search demand is strong and Arabic content supply is weak, in our experience of the UAE market:
Healthcare and clinics. Government-adjacent and legal services. Property, particularly for GCC national buyers. Education. Financial services. Automotive. Home services.
In several of these, well-executed Arabic pages rank within a few months against competition that consists mostly of translated content.
Measuring separately
Set up separate Search Console property filters or use the country and language dimensions properly. Reporting Arabic and English traffic as one number hides both problems and progress.
Track separately: impressions, clicks, average position, conversion rate and cost per enquiry by language. It is common to find that Arabic converts at a higher rate on lower volume, which changes where the next content investment should go.
What to do if you have a translated site already
Do not delete it. Audit it.
Pick your ten highest-value English pages. Build the native Arabic keyword set for those topics. Rewrite those ten pages natively rather than editing the translation. Fix hreflang and canonicals. Fix the RTL layout issues. Measure over three months.
If those ten move, extend. That is a far better use of budget than a full-site retranslation that repeats the original mistake in better prose.
If you want the Arabic keyword set built natively for your category, that is where our SEO content team starts on any bilingual project — and our content marketing practice writes rather than translates it.
Common questions
Should the Arabic site be on a subdomain or a subfolder? A subfolder in almost every case. Subdomains and separate country domains split the authority a UAE business usually cannot afford to divide.
Do we need every page in Arabic? No. Start with the ten pages that carry the most commercial value, built natively, and extend once they perform. A full retranslation of a large site is usually the wrong first investment.
Can we rank in Arabic without an Arabic-speaking team? Not credibly. You need native research and native writing. Everything else can be handled by your existing team.
How long does Arabic SEO take in the UAE? Often faster than English — three to six months in categories where the competition consists mostly of translated content.
:quality(82))
:quality(82))
:quality(82))