The challenge
An Arabic version had been added by translating text inside the same templates, so right-to-left layout broke in a dozen places and search engines could not tell the versions apart.
Objectives
- Serve both languages with correct layout
- Make each language independently indexable
- Let the client publish in both without a developer
- Keep one design system across both
What we built
A properly bilingual build with RTL handled in the templates, separate indexable URLs per language, and hreflang declared so search engines serve the right version.
Technology
hreflang · RTL · WordPress
How it was delivered
- Template-level RTL support rather than CSS patches
- Separate URL structure per language
- hreflang and canonical tags configured
- Editor workflow for publishing in both languages
Outcomes
- Arabic pages render correctly rather than approximately
- Both languages are independently indexable
- Content is published in both without developer help
