Run your English copy through Google Translate, flip the text to the right, and call it an Arabic version — this is, roughly, how a large share of bilingual websites in the Gulf are still built. It ships, it technically contains Arabic, and to anyone who does not read the language it looks finished. To the Arabic reader it looks like exactly what it is: an afterthought, assembled by people who were not really thinking about them.
Doing it properly is not harder because Arabic is exotic. It is harder because a genuine bilingual Arabic-English website is two equal experiences sharing one structure, and that touches almost every layer of the build — layout direction, typography, tone of voice, numerals and dates, and how each language is found in search. Get one layer wrong and the whole thing quietly signals second-rate. Here is what the layers actually are, and where most Dubai sites come apart.
Bilingual is not the same as translated
The first mistake is treating the Arabic side as a copy of the English one in different words. A translation answers 'what does this sentence say in Arabic'. A bilingual website has to answer a larger question: what does an Arabic-speaking visitor need to see, in what order, phrased how they would phrase it themselves. Sometimes that is the same content mirrored; often it is not. Headlines that land in English fall flat translated literally, and calls to action that work in one culture feel abrupt or too soft in the other.
This matters more in the UAE than almost anywhere, because your Arabic-speaking audience is not a minority you are accommodating — for many businesses it is half the market or more, and it is a discerning half. Emirati and wider Gulf readers notice within seconds whether the Arabic was written or merely generated. A site that gets it right earns a kind of trust an English-only competitor cannot buy; a site that gets it wrong tells its most valuable local audience that they were an export setting, not a priority.
RTL is a mirror, not a text-align
A proper RTL website does not simply push text to the right edge. It mirrors the entire interface. The navigation flows from right to left, the logo moves to the right, progress steps and timelines reverse, form labels and their fields swap sides, and directional icons — back arrows, next chevrons, breadcrumbs — flip to point the correct way. Done with CSS logical properties and a single dir attribute rather than a pile of overrides, the same layout serves both directions cleanly. Done as an afterthought, you get an English page with the paragraphs shoved rightward and every arrow pointing the wrong way.
Then there are the details that separate a considered build from a converted one. Arabic can use Arabic-Indic numerals or Western digits depending on audience and context, and the choice should be deliberate, not accidental. Dates, phone numbers, and prices are read left-to-right even inside right-to-left text, which the bidirectional algorithm handles only if the markup is clean. Some icons should mirror and some must never — a play button, a company logo, a clock still face the same way in Arabic. Knowing which is which is most of the craft.
Real Arabic type, not a Latin fallback
Open a poorly built bilingual site, switch to Arabic, and you can often see the exact moment the design gives up: the Arabic renders in whatever system font the browser reaches for, because the brand typeface has no Arabic glyphs at all. The result is legible but lifeless — mismatched weight, cramped line height, letters that do not belong to the same visual family as the English. It is the typographic equivalent of speaking your language with a heavy, indifferent accent.
Arabic is a connected, calligraphic script with its own rules for weight, spacing, and vertical rhythm. It generally needs more line height than Latin text and a typeface actually drawn for Arabic, not a Latin font stretched to cover it. The professional move is either a single family designed with both scripts in mind or a carefully matched pair — a Latin face and an Arabic face chosen to sit beside each other at the same optical weight. This is unglamorous work that almost nobody notices when it is right and everybody feels when it is wrong.
White Arabic: choosing a tone, not just words
Arabic forces a decision English does not: which Arabic. Egyptian and Levantine dialects feel warm but regional; heavy classical Arabic reads as formal to the point of stiffness, like a legal notice. For a brand speaking to the whole region, the answer is what writers call white Arabic — clean modern standard Arabic, stripped of any single dialect, but kept natural rather than stiff-classical. It is the register educated readers across the Gulf, the Levant, and North Africa all accept as native-adjacent without anyone feeling addressed in someone else's accent.
This is precisely the register machine translation cannot reach. Automated tools default to either an over-formal classical Arabic or an awkward literal rendering of English word order, and both mark a page instantly as untended. White Arabic is a writing skill, not a translation task — it requires someone who thinks in the language, understands the brand, and can carry tone across from the English rather than just carry meaning. It is the difference between a site that speaks Arabic and one that merely contains it.
Two languages, two search presences
A bilingual website is also two SEO problems, and hreflang is where most get the plumbing wrong. Each language needs its own real, indexable URL — not a version swapped in by JavaScript — with reciprocal hreflang tags telling Google which page serves Arabic and which serves English, correct lang and dir attributes, and both included in the sitemap. Skip this and Google may index only one language, or serve the wrong one to the wrong searcher, quietly wasting half your content.
The deeper point is that Arabic search is not translated English search. People phrase queries differently, use different terms for the same service, and often mix Arabic with an English brand or product name mid-sentence. Real Arabic SEO starts from its own keyword research and its own metadata written for how Arabic speakers actually search — not English titles run through a dictionary. The reward is a less contested search space: while your competitors fight over the same English keywords, a properly optimised Arabic side reaches an audience they are not even showing up for.