Abdelrahman GadChief Marketing Officer · Growth Systems
All services 06

Bilingual Websites (EN / AR)

An Arabic site that was built in Arabic, not translated into it.

Who it is for

Businesses selling into both Gulf and international markets whose Arabic version is visibly an afterthought.

The problem it solves

  • The Arabic version is the English one with the words swapped and the layout unchanged.
  • RTL is faked with flipped margins, so half the interface points the wrong way.
  • Arabic pages ship English structured data, so Google reads them as an English site.
  • Arabic type is set at Latin line-heights, which makes it dense and tiring to read.
Translated vs. built bilingualSame content, two very different results in search and on a phone.
One brand, two markets The same thing to say in both
Translated Words swapped Layout, schema and type left as they were
Google reads it as English And the phone view breaks
Built bilingual Two real versions hreflang, translated schema, true RTL
Both versions can rank And both read properly on a phone

What you get

  • Two real language versions, cross-linked with correct hreflang and separate sitemaps
  • True RTL built on CSS logical properties — a genuine mirror, not flipped margins
  • Arabic typography set for Arabic: an Arabic glyph box runs about 1.9× the font size
  • Translated structured data, not English schema on an Arabic page
  • Copy written for each market, because the same claim needs different proof in Cairo and Riyadh
  • Core Web Vitals and accessibility verified on both versions, on a phone

How it runs

01

Structure both languages from the start

Retrofitting Arabic onto an English build is where the RTL bugs come from. Both versions get designed together.

02

Set Arabic type properly

Line-height, weight and size are not the Latin values. Getting this wrong is the difference between a site that reads and one that is merely legible.

03

Localise the argument, not the sentences

Pricing presentation, proof points and order of reassurance change per market.

04

Verify on a phone, in both directions

Every RTL bug I have shipped was invisible in a desktop preview and obvious on a phone.

What it is not

  • Custom application or backend development
  • Ongoing content writing after launch
  • Hosting and domain costs

Not sure which one you need?

Describe the situation. I will tell you which of these it actually is — or that it is none of them — before any engagement and at no charge.