Why bilingual RTL/LTR websites win more clients in the Arab market
The fastest way to spot a 'translated' Arabic website is to open it. The text reads right-to-left, but everything else still behaves like an English site wearing an Arabic costume: the back arrow still points the wrong way, the icons on a progress bar still move left to right, and a price like "25 د.أ" sits awkwardly broken across a line because nobody told the layout that Arabic and Latin characters need to coexist. None of this is a translation problem. It's a direction problem, and it's solved in the CSS and component architecture, not in the copywriting.
The single biggest mistake I see repeated across the Arab web is treating `direction: rtl` as the whole job. Flipping the text direction is step one of about ten. Padding and margin declared with `left` and `right` need to become logical properties (`margin-inline-start`, `padding-inline-end`) so they flip automatically with direction, instead of being hard-coded and then overridden with a second, RTL-only stylesheet that someone forgets to update six months later. Arrows, chevrons, and 'next/previous' icons need their direction computed from the locale, not just mirrored with a blind `scaleX(-1)`, which breaks the moment an icon contains text or an asymmetric shape like a play button.
Carousels and sliders are where this shows up the most visibly. A slider built assuming left-to-right scroll will autoplay backwards in an RTL layout unless the scroll direction and the dot indicators are both locale-aware. I keep the scroll container itself forced to `dir="ltr"` for consistent touch/scroll physics, while the arrow icons and their click handlers read the locale and point the correct way. It is a small detail that is invisible when done right and glaringly broken when it isn't.
Typography deserves its own paragraph. An Arabic typeface and a Latin typeface living on the same page need a similar x-height, similar weight steps, and ideally a similar personality, or the page looks like two different websites stitched together depending on which script is being read. I pair IBM Plex Sans Arabic with Space Grotesk on this site specifically because their proportions sit close enough that switching between English and Arabic doesn't feel like a jump cut. Picking an Arabic font that is really a Latin font's glyphs 'stretched' into Arabic shapes is a common shortcut, and Arabic readers notice it immediately, even if they can't always say why it looks off.
Mixed-direction content inside a single line, like an Arabic sentence containing a brand name, a phone number, or a price, is governed by the Unicode bidirectional algorithm, and it does not always do what a designer expects without help. Wrapping Latin-script tokens (a product SKU, a US dollar price, an English brand name) in the correct isolation markup keeps them from reversing their internal character order or jumping to the wrong side of a punctuation mark. This is invisible until the one order where it breaks, and then it's the kind of bug a client screenshots and sends with a confused question mark.
Bilingual SEO is the part agencies skip entirely. Each locale needs its own URL (`/en/...`, `/ar/...`, not a client-side toggle on one URL), `hreflang` alternate tags pointing each language version at the other, and translated metadata, Open Graph tags, and structured data, not just translated visible copy. A site that is bilingual in the UI but monolingual in its `<head>` is invisible to half its potential search traffic.
None of this is cosmetic. In the Arab market specifically, an Arabic-speaking visitor can tell within seconds whether a site was built for them or adapted for them, and that first impression affects trust before a single word of copy is read. For e-commerce, local services, and anything collecting a lead or a payment, that trust gap is a conversion-rate gap. Designing RTL in from day one, rather than retrofitting it, is cheaper to build and it is the difference between a site that happens to support Arabic and a site that was actually made for an Arabic-speaking customer.
