All Essays

Essay 03

The Arabic web deserves first-class

2026-09-20

Arabic is not a translation task: it is an engineering and authoring discipline that starts at the first sketch.

Something quietly strange happens on most bilingual websites. The Arabic version is a mirror of the English one: flipped, translated, and slightly broken. A search box that lands on the wrong side. Numbers that jump direction mid-sentence. Errors no native reader would forgive. The site works, technically. It just was not written for you.

We build in the other direction. On this very site, Arabic and English are two equal trees with independently authored copy, not a translated skin over an English source. The Arabic is not derived; it is written. Its sentences carry their own rhythm and their own way of arriving at the point, which is why nothing here reads like a translation.

The craft is unglamorous and cumulative. Logical CSS properties instead of left and right, so direction is a declaration rather than a refactor. Arabic-Indic numerals in Arabic copy, consistently, dates included. Layouts composed for right-to-left rather than mirrored into it. Typography that respects the script's joining rules. None of this shows up as a feature; all of it shows up as ease.

There is a strategic reading, too. As answer engines and assistants begin to cite their sources, the Arabic side of that index is remarkably thin: content that is authored, structured, and quotable is scarce relative to the readership it serves. The field is not empty because it is small; it is empty because it is hard. That gap is where a bilingual-first group compounds quietly.

This is why Arabic is a service line for us, not a courtesy. When we build a platform for a client, the Arabic experience is built, tested, and read aloud, not converted in the final week. The region's first language deserves the same engineering budget as everyone else's second.

Hold any site that claims bilingualism to the standard we invite for ours: switch the language and read. If the Arabic feels like a translation, it is one.

FAQ

Direct, unambiguous answers

Why do so many bilingual websites feel broken in Arabic?

Because the Arabic version is usually a mirror of the English one: flipped, translated, and slightly broken. A search box lands on the wrong side, numbers jump direction mid-sentence, and errors appear that no native reader would forgive. The site works technically, but it was never written for the Arabic reader.

What does building a website for Arabic natively involve?

It involves concrete engineering choices: logical CSS properties instead of hard-coded left and right, so direction is a declaration rather than a refactor; Arabic-Indic numerals in Arabic copy, dates included; layouts composed for right-to-left from the start; and typography that respects the script's joining rules. None of it shows up as a feature, all of it shows up as ease.

Do you translate the English site into Arabic, or write it separately?

We write it separately. On our own site, Arabic and English are two equal trees with independently authored copy, not a translated skin over an English source. The Arabic carries its own rhythm and its own way of arriving at the point, which is why nothing there reads like a translation.

Why does Arabic content matter for answer engines and search?

Because the Arabic side of the index answer engines cite from is remarkably thin: content that is authored, structured, and quotable is scarce relative to the readership it serves. The field is empty because it is hard, not because it is small, and that gap is where careful bilingual engineering compounds quietly.

Next step

Web Platforms

Web platforms and engineering (bilingual, RTL-native, fast, and built to be found) on the same stack that runs this site and our ventures.

Start an order, request a private consultation, or simply ask a question: one WhatsApp message in Arabic or English opens the conversation.

Talk on WhatsApp