Arabic website design and RTL: why translation is not enough

Most broken Arabic websites were not badly translated. They were built in English and then flipped. The words are correct and the page still feels wrong: arrows point the wrong way, numbers sit oddly, and headlines are cramped. Arabic website design is a layout problem before it is a language problem.

Right-to-left changes the reading path. In Arabic the eye starts at the right edge, so the logo, the primary navigation, and the first thing you want read all move there. An RTL direction attribute handles the text itself, but it does not tell your design which element deserves the strongest position on the page. That is a decision, not a setting.

Icons and motion have direction too. A “next” arrow that points right in English should point left in Arabic. Sliders advance the other way. Progress bars fill the other way. Anything that implies forward motion needs to be checked, because CSS logical properties handle spacing automatically but say nothing about what your arrows mean.

Typography is where most Arabic sites quietly fail. Arabic script is connected and needs more vertical breathing room than Latin — the same line-height that looks tight and modern in English looks cramped in Arabic. Letterforms carry weight differently, so a font pairing that felt premium in English can read cheap in Arabic. You need a typeface designed for Arabic, not a Latin font with an Arabic fallback quietly substituted by the browser.

Mixed content is the practical headache. Phone numbers, prices, dates, and English brand names all appear inside Arabic sentences, and each has its own direction rules. Get this wrong and a phone number renders with digits in the wrong order — which is worse than a typo, because the visitor tries to call and fails.

Then there is dialect. Formal Modern Standard Arabic reads correct but distant for an Egyptian audience, and it is what most template sites default to. Egyptian companies selling to Egyptian customers usually convert better in the dialect people actually speak — while a page aimed at Gulf clients often expects a more formal register. That is a positioning choice, and it should be made deliberately rather than inherited from a translation tool.

A real bilingual build means both versions are designed, not one designed and one converted. Same quality of typography, same spacing rhythm, same care in the hero. Both language versions need their own titles and descriptions for search, and hreflang tags so Google serves the right one to the right person. Duplicating English metadata onto Arabic pages wastes the Arabic version's ranking chances.

The maintenance cost is the part that gets forgotten. Every new page, every price change, every article now exists twice. Decide before launch who writes the Arabic and who keeps it in sync. Sites where the Arabic side silently goes stale are common, and visitors notice immediately.

Test on an actual phone with Arabic set as the system language before launch. Desktop browser preview hides the failures that matter — line breaks in headlines, form fields with labels on the wrong side, buttons where the text overflows.

Bilingual scope changes the quote, so ask about it before signing. What a website costs in Egypt covers how much the second language moves the number, and how to choose a web design company covers who to trust with it.

If your customers read Arabic, the Arabic version is the main site, not the translation. We build company websites in Egypt with both languages treated as equals, and the bilingual scope is priced openly in how pricing works.