Mirror the layout, not everything in it. Choose a real Arabic typeface, write the Arabic rather than translating it, and test every page with someone who reads Arabic first.
A company launches its new bilingual website. The English pages look sharp. The Arabic pages are the same design, flipped: the menu is on the right, the text is right-aligned, the job is done. Then an Arabic-speaking customer tries to use it. The arrows point backwards, the phone number reads in the wrong order, the font looks cramped and the contact form puts the cursor on the wrong side.
Mirror the layout.
In a right-to-left page, the reading order starts on the right, so the layout should follow: the logo and main navigation move to the right, sidebars swap sides, progress runs from right to left and “next” arrows point left. In HTML this begins with setting the language and direction on the page, as explained in the W3C guide to structural markup and right-to-left text .
Modern CSS can handle most of this automatically if the site is built with logical properties, such as start and end instead of left and right. Building it that way from day one is far cheaper than fixing it page by page later.
But don’t mirror everything.
Some things keep their direction in every language. Getting these wrong is the quickest sign that a site was flipped rather than designed.
- Logos and wordmarks stay exactly as designed.
- Phone numbers, prices, dates in digits and product codes read left to right inside Arabic text.
- Media controls such as play and fast-forward keep their usual direction.
- Charts with a time axis, clocks and maps keep their real-world orientation.
- Photographs are never flipped; a mirrored photo can show text or a car the wrong way round.
Give Arabic its own typography.
Arabic letters need more vertical room than Latin ones, so the line height, font size and spacing that work in English often look cramped in Arabic. Choose a typeface designed for Arabic on screen, with the weights you need, and set Arabic sizes and line heights separately rather than inheriting them.
Never apply letter-spacing to Arabic text: it breaks the connections between letters. And decide early whether you use Western digits (1, 2, 3) or Arabic-Indic digits (١، ٢، ٣), then use them consistently.
If the Arabic pages feel slightly harder to read than the English ones, Arabic-speaking customers will notice, even if they cannot say why.
Write it in Arabic.
Machine translation of the English copy produces pages that are understandable and unconvincing. Headlines, buttons and form labels in particular should be written by someone who thinks in Arabic and knows the audience. Short, natural button text matters: “أرسل” or “تواصل معنا” rather than a literal translation of “Submit your enquiry”.
Arabic pages also need their own search work. People search differently in Arabic, with different words and spellings, so the page titles, descriptions and headings should match how they actually search, not how the English was phrased.
Test with real readers.
Before launch, ask two or three people who read Arabic first to complete real tasks on a phone: find a product, fill in the form, call the business. Watch where they hesitate. Check forms with Arabic names and addresses, mixed Arabic and English input, and phone numbers with the country code.
A bilingual website is two websites that share a design. Give the Arabic one the same care, and it will earn the same trust.
FROM THINKING TO DOING
Let’s build a website that works in both languages.
We design and build bilingual websites with native right-to-left layouts, Arabic typography and search for each language.

