“We support Arabic” usually means a mirrored layout and a translation pass. That is not an Arabic-first platform — and the difference shows up in traffic, trust, and conversion across the Gulf and Egypt.
Parity, not mirroring
RTL-ready means the Arabic experience is designed, not derived: layouts built for RTL reading order, typography chosen for Arabic scripts, and components that do not break when strings run long or bidirectional text mixes currencies and brand names.
Per-language content models
The deeper work is structural. Arabic and English pages rarely want identical component trees — promotions differ, legal copy differs, even page hierarchies differ. Sitecore handles this well when the content architecture plans for it from day one, and painfully when Arabic is bolted on later.
Editorial reality
Bilingual estates live or die on workflow: who authors first, how translation is queued, and whether Arabic editors get the same preview and scheduling tools as English ones. If the Arabic team works in spreadsheets, the platform has failed them.
What it looks like done properly
EgyptAir’s digital platform runs Arabic-first across 93 destinations — built and run by our team. The case study is public.
If your Arabic experience is a mirrored afterthought, our Sitecore health check will show you precisely where parity breaks — content model, front end, and workflow — before you commit budget to fixing it.
