The Challenge
A medical center serving both Arabic- and English-speaking patients had an Arabic-only web presence. English-speaking patients — including medical tourists — could not read the services, find the contact details, or book. A typical agency "translation" bolts on machine-translated pages and breaks the layout the moment text runs right-to-left.
Our Approach
- Built a true bilingual architecture, not a translation layer: a parallel English section with its own URL structure and hreflang signals for search engines.
- Engineered the layout for both right-to-left Arabic and left-to-right English, so neither audience gets a second-class experience.
- Shipped incrementally: the four most-requested English service pages went live first, prioritised by real demand.
- Configured every not-yet-built English URL to redirect to a sensible fallback instead of a 404, so patients and search engines never hit a dead end mid-rollout.
Results
- The center now speaks to both patient audiences from one site.
- English pages expand page-by-page on a live production system — no big-bang relaunch, no downtime.
- Zero broken paths throughout the rollout: every English URL resolves, whether the page is built yet or not.
Key Takeaways
- A bilingual site and a translated site are different products; only one of them feels local to both audiences.
- Incremental rollout with redirect fallbacks lets you ship value early without ever exposing a broken site.
- RTL support has to be designed in, not patched on.