Bilingual Arabic and English Websites: What Actually Matters

Adding a translation plugin to an English site takes an afternoon, which is exactly why so many Gulf businesses have one. It also produces an Arabic experience that reads as machine output, breaks visually the moment text direction flips, and is largely invisible to Arabic-language search. If Arabic buyers matter to your business, this is worth doing properly.

Right-to-left is a layout problem, not a text problem

Flipping text direction is trivial. Everything around the text is where the work lives. Navigation order reverses. Icons that imply direction — arrows, progress indicators, carousel controls — have to mirror, while icons that do not imply direction, like a phone or an envelope, must not. Padding and margins that were deliberately asymmetric need to swap sides. Form field alignment, table column order and breadcrumb separators all change.

Modern CSS handles much of this if the site was built with logical properties from the start — using inline-start and inline-end rather than left and right. Retrofitting that onto a site built the other way is substantially more work than building it in from day one, which is why bilingual is a decision to make before the build, not after.

Arabic typography needs its own attention

Arabic script is connected, and letterforms change shape based on position within a word. It generally needs more line height than Latin text to stay legible, and font sizes that look balanced in English often look cramped in Arabic at the same value. A font stack chosen for a Latin brand will not automatically carry — you need a genuine Arabic typeface that shares the brand's character, not a fallback the browser picked.

Content parity is a commercial decision

Full parity means every page exists in both languages. It is the strongest signal to both buyers and search engines, and it is the most expensive to maintain, because every future update is two updates.

Partial parity — where core commercial pages exist in Arabic and deeper technical content stays English — is a legitimate choice, and often the right one for industrial suppliers whose specification sheets are English by industry convention anyway. What does not work is partial parity that is not signposted, where an Arabic visitor clicks through and silently lands back in English.

The technical signals that make Arabic pages findable

• ◆Distinct URLs per language — /ar/ paths or a separate subdomain. The same URL serving two languages cannot be indexed properly for both.
• ◆A correct lang attribute and dir="rtl" on the html element, not on a wrapper div.
• ◆Reciprocal hreflang annotations between the language versions, each pointing at the other and at itself.
• ◆Arabic metadata written in Arabic — titles and descriptions translated with intent, not run through an API.
• ◆Structured data with Arabic name and description values on the Arabic pages.

Arabic keyword research is not translated English keyword research

This is the step most projects skip. Arabic speakers searching for a service frequently use different phrasing than a direct translation would produce, and dialect varies meaningfully across the Gulf. There is also substantial code-switching — Gulf professionals often search in English for technical terms and Arabic for commercial ones, sometimes within the same session. Translating your English keyword list and targeting the output produces pages aimed at queries nobody types.

When bilingual is not worth it

If your buyers are procurement engineers at multinationals in Dubai or the Eastern Province, your business may genuinely run in English, and a half-maintained Arabic section will look worse than none. Bilingual is worth the investment when Arabic-speaking decision-makers are the ones choosing, when you sell to government or government-adjacent entities, or when your competitors have it and you do not. Otherwise, put the budget into making the English site excellent.