Building one website in Arabic, French and English without wrecking your SEO

A brand operating across MENA and North America eventually needs the same site in Arabic, French and English. The request sounds like a translation job. It is mostly an architecture job, and the decisions made in the first week determine whether the site accumulates search authority or splits it three ways.

Decision one: the URL structure

There are three viable patterns, and one popular non-viable one.

• Subdirectories — example.com/ar/, example.com/fr/. All authority accrues to one domain. Simplest to run. Correct answer for the large majority of businesses.
• Subdomains — ar.example.com. Cleaner separation if the content genuinely diverges by market, at the cost of treating each as a semi-separate property.
• Country domains — example.tn, example.ca. Strongest local signal, highest cost, and you are now maintaining several sites. Worth it when the offering, the pricing and the legal entity actually differ by country.
• Query parameters — example.com?lang=ar. Avoid. Crawlers handle it poorly and users cannot share a link reliably.

Unless there is a specific reason to do otherwise, use subdirectories. Everything you publish in any language strengthens one domain rather than three weak ones.

Decision two: hreflang, done properly

The hreflang annotation tells a search engine which version of a page to show which user. It fails more often than it works, for reasons that are entirely mechanical.

Every language version must reference every other version and itself. The references must be reciprocal — if the Arabic page points to the French one, the French one must point back, or the whole cluster is ignored. Use full absolute URLs. And declare an x-default for visitors who match nothing.

Get the codes right, too. Arabic for the Gulf is ar-AE; Arabic for Tunisia is ar-TN; plain ar covers all of it. French in Canada is fr-CA and differs from fr-FR in vocabulary that customers notice. Only split by region if the content actually differs — otherwise one language code is cleaner and harder to break.

A common and expensive mistake: pointing several hreflang values at a single URL. It is not a shortcut. It is ignored.

Decision three: right-to-left is not a stylesheet flip

Arabic reverses the reading direction, and with it the visual logic of the page. Modern CSS handles most of this if the site was built with logical properties from the start — margin-inline-start rather than margin-left, padding-inline rather than left and right. Set dir="rtl" on the html element and a well-built layout largely mirrors itself.

What does not mirror itself:

• Icons with direction — arrows, chevrons and progress indicators must flip. Logos and play buttons must not.
• Numbers and Latin text — phone numbers, prices and brand names stay left-to-right inside an RTL paragraph. Bidirectional text is where layouts break.
• Line height — Arabic script needs more vertical space than Latin at the same size. Copying the Latin type scale produces cramped text.
• Text expansion — French runs roughly 15–20% longer than English. Buttons sized to fit English will overflow.
• Shadows and animation — anything with a directional bias needs a mirrored variant.

Fonts are a performance decision, not a design one

Arabic webfonts are large. Loading a full Arabic family alongside a Latin one on every page is a straightforward way to lose the performance work everywhere else. Serve each language only the font it needs, subset aggressively, and use font-display: swap so text is readable before the file lands.

Translate the metadata, not just the body

The single most common failure we find in audits is a site where the visible content is beautifully translated and everything the crawler reads is not. Title tags, meta descriptions, image alt text, structured data, breadcrumb labels, URL slugs, form labels and error messages all need translating. A page with Arabic body copy and an English title tag will not rank for Arabic queries.

And translate the keywords rather than the words. The term a Tunisian buyer types is often not the literal translation of the English term — sometimes it is the French word, sometimes it is the English one written in Arabic script. That is keyword research, in each language, not a job for a translation memory.

What we would actually build

For most businesses in this position: one domain, language subdirectories, reciprocal hreflang including x-default, logical CSS properties from the first line, per-language font subsets, and fully translated metadata. Nothing exotic. It is a set of decisions that are cheap to make correctly at the start and expensive to retrofit.

Our teams in Tunisia and Canada work across Arabic, French and English daily, which is the reason this list reads like it was written by someone who has cleaned up the alternative. If you are planning a multilingual build, our web development and SEO pages cover how we approach it.