Redesign a Doha corporate website as one bilingual project, or expect to keep running two different companies online. The English version gets the new services, current case studies and the enquiry form that works. The Arabic version gets last year's structure, machine-shaped sentences and pages nobody updated — and Arabic-speaking buyers judge the firm on exactly that version. The fix is procedural: audit page parity in both languages, build one design system for two directions, write the Arabic natively, protect both sets of rankings while URLs move, and launch both languages together, finished.
The short answer: redesign both languages as one project, or do not start
A bilingual redesign is not an English redesign plus a translation task at the end. It is two first-class versions sharing one design system, one content plan and one launch date. Every stage — audit, wireframes, copy, build, testing — is scoped and scheduled for both languages from day one.
The moment a proposal separates "website redesign" from an optional "Arabic version" line, the Arabic site has been demoted. It will be designed late, written in a hurry and tested least — precisely how the current split happened. If the budget cannot carry both languages properly, shrink the site: fewer pages, done equally well in both, beat a large English site with an Arabic shadow.
The parity audit: which pages exist, rank and convert — per language
Start by listing what you actually have, language by language. For each language, record:
- Which pages exist — and which exist in only one language - Which pages bring search traffic and enquiries - Which pages are stale: old services, former staff, superseded projects - Which enquiry paths work: forms, phone links, WhatsApp entry points
Then decide, per page pair, whether the redesign keeps, merges, rewrites or retires it. The Arabic column matters most: pages that rank and convert in Arabic are assets even if the English team considers them minor, and retiring them silently destroys search equity. The output is a parity map.
One design system, two directions: RTL as layout work, not mirroring
Right-to-left design is not flipping the finished English site. A mirrored layout keeps the visual logic of English — where the eye starts, what it meets first, which side carries weight — and simply reverses the geometry.
Proper RTL work designs the Arabic reading path deliberately: navigation order, hierarchy, image placement, icon direction, table alignment and call-to-action position follow how Arabic is read. Technically, this is why modern CSS uses logical properties — inline-start and inline-end instead of fixed left and right (MDN's CSS documentation) — so one component behaves correctly in both directions. Scope it that way: designed once, verified in both directions, adjustments named rather than discovered in testing.
Arabic content written natively: where translation-after-sign-off fails
The standard failure runs like this: English copy is written, debated and signed off, then sent for translation under deadline. The Arabic arrives literal where it should be idiomatic, formal where the English is direct, and stuffed with terms no Qatari buyer would type into Google. Nobody senior reviews it, because the project is "finished".
Write the Arabic inside the project instead. A native Arabic copywriter works from the same brief as the English writer — same facts, same offer, same evidence — and writes for Arabic readers, not from the English sentences. Headlines, calls to action and service descriptions get their own drafting and sign-off. Translation still suits factual documents, but pages that sell the firm must originate in the language they sell in. Machine translation output is a draft input — never the published text.
Typography, numerals and forms: the bilingual details buyers judge you by
Buyers decide whether the Arabic site is real in the details. Arabic typography needs a typeface chosen for Arabic screen reading, with line height that gives the script room; Latin display fonts with an Arabic afterthought produce cramped, tiring pages. Load the Arabic font properly and test it on real devices, because fallback fonts quietly wreck sound design.
Numerals need an explicit house rule: Western or Arabic-Indic digits in phone numbers, dates, figures and forms — chosen per context and applied consistently, not mixed at random. Forms need the most care: labels, error messages, date fields and phone formats must work in Arabic, mixed-direction entries such as email addresses must not break the layout, and the confirmation must exist in the visitor's language. An enquiry form that replies in English to an Arabic enquiry tells that buyer exactly where they rank.
Protecting both rankings: hreflang, URLs and redirects through the redesign
A redesign already puts rankings at risk; a bilingual redesign doubles the surface. Google's multilingual documentation is clear on the mechanics: hreflang annotations must be mutual — if the English page points to its Arabic counterpart, the Arabic page must point back — and hreflang URLs must be fully qualified. Keep the URL structure consistent, map every changed URL in both languages, and verify the language switcher lands visitors on the equivalent page, not the homepage.
Inventory the Arabic equity before anything moves: which Arabic pages rank, for what, and where each goes in the new structure. Our guide to SEO for bilingual Arabic-English websites covers the ongoing mechanics, and the website redesign SEO migration checklist covers the migration steps. Ranking protection is a risk to manage here, not the subject — the subject is parity.
The CMS workflow that keeps the pair in parity after launch
Most bilingual sites drift apart after launch, not during the build. The English page gets updated because updating it is easy; the Arabic twin waits, then diverges. Prevent that in the CMS.
Set the workflow so a page pair publishes together: versions are created as linked drafts, neither goes live alone without an explicit override, and the dashboard shows unpaired or out-of-date pages at a glance. Assign a named Arabic content owner with the same authority as the English owner. Approvals handle both languages in one pass, so a service change cannot be signed off in one language and forgotten in the other.
Bilingual QA before launch: the checks neither language team can skip
Test both languages as separate products sharing a system:
- Every page pair exists and matches the parity map - RTL layout checked on real screens: navigation, tables, galleries, icons - Arabic type renders in the intended font, at readable sizes - Forms submit, validate and confirm in the language of the visitor - Language switcher lands on the equivalent page from every template - hreflang pairs are mutual, and redirects resolve in both languages - Phone numbers, dates and numerals follow the house rule
Have native readers do the Arabic pass — not the developers who built it. Read the Arabic aloud; stilted sentences that survive silent reading rarely survive being spoken.
Launch sequencing: never ship one finished language and one draft
The classic bilingual launch failure is a deadline decision: the English site is ready, the Arabic is "a week behind", and someone senior says launch anyway. That week becomes a quarter, and Arabic-speaking buyers meet the unfinished version of the company — again.
Sequence launch as a single event with a single gate: both languages pass QA together, or the launch moves. If phasing is unavoidable, phase by section, not by language: services in both languages, then company pages in both. Keep the old site live in both languages until the gate is passed; a half-migrated Arabic site is worse than a dated but complete one.
Scoping the work: what a bilingual redesign proposal must itemise
A credible proposal itemises the bilingual work explicitly: the parity audit; design-system work covering both directions; native Arabic copywriting as its own line, with its own sign-off; Arabic typography and font licensing; hreflang, URL mapping and redirects per language; CMS paired-publishing configuration; bilingual QA with native review; and the paired launch plan. One unexplained total with "bilingual included" is how the old site got built.
Note what this scope is not. It is a single corporate site: structuring several brands or branches of a group is a group-architecture project, covered separately by our companion guide to a website for a Qatari family business group. A sector example sits outside this scope too: our guide to a school admissions enquiry portal in Qatar covers enquiry-led builds for schools. It carries no invented price bands — the honest comparison is between itemised scopes. WebStackRank provides an itemised proposal within 24 business hours, and our Arabic presence for Qatar exists for the same reason this article does. Our Qatar country guide sets the wider context.
FAQ
Can we redesign the English site now and add Arabic later?
You can, but later rarely comes, and the Arabic version then has to be retrofitted onto a design system never built for it. If budget forces a choice, launch a smaller site finished in both languages, phased by section rather than by language.
Is mirroring the layout enough for the Arabic version?
No. Mirroring reverses geometry but keeps English reading logic. Arabic pages need their own reading path — navigation order, hierarchy, icon direction, typography and form behaviour designed for right-to-left reading, built with direction-aware components and checked by native readers.
Will a bilingual redesign hurt our Arabic rankings?
It can, if Arabic URLs change without redirects or hreflang pairs break. Inventory which Arabic pages rank before anything moves, map every changed URL in both languages, keep hreflang mutual and fully qualified, and monitor Arabic pages after launch.
Should Arabic content be translated from the English?
Not for pages that sell the firm. Give a native Arabic copywriter the same brief as the English writer and let the Arabic originate in Arabic, with its own sign-off. Translation suits factual documents; machine translation is a draft input at most.
How do we keep the two versions equal after launch?
In the CMS workflow: paired drafts that publish together, a dashboard view of unpaired or stale pages, a named Arabic content owner, and approvals that sign off both languages in one pass. Parity survives when the system enforces it.
Planning a bilingual redesign for your Doha firm? Get it scoped as one project (CTA)
Bring us the current site as it really is — both languages, including the pages you would rather not show us. We will map the parity gap and scope the redesign as one bilingual project through our web development in Qatar team, itemising the Arabic work line by line. Start from our Qatar page and tell us which language buyers complain about.
