Pricing · 7 min read
How Much Does a Bilingual Arabic-English Website Cost in the UAE? (Why It’s Not a Translation Add-On)
Already have a website? Get a free technical audit:
Search for the cost of a bilingual Arabic-English website in Dubai and you will find the same answer repeated across dozens of pricing guides: add 15–30% to the English-only price. It is not exactly wrong. It is just useless until you know what that percentage is supposed to buy — and on the cheaper quotes, what it buys is often a translate plugin and a prayer. Here is what bilingual actually costs in the UAE, and what the number should include.
The one-line answer everyone gives — and why it misleads
Published UAE pricing guides mostly converge on the same figure: a bilingual build costs 15–30% more than an English-only one, or somewhere between AED 2,000 and 8,000 on top of the project price. The range itself is broadly honest. The problem is that it averages across two completely different products. At one end, ‘Arabic version’ means machine-translated strings injected into a left-to-right layout. At the other, it means a site designed, written, and engineered for Arabic readers from the first wireframe. Both get quoted as ‘+20%’. Only one of them survives contact with a customer who actually reads Arabic.
What ‘bilingual’ actually means technically
An Arabic version of a website is not the English site with different words in it. Arabic is written right to left, and that flips far more than text alignment: navigation order, carousels, breadcrumbs, directional icons, form layouts, even which side a drawer slides in from. Arabic typography is its own discipline — the script connects, has no italics, and needs different typefaces, sizes, and line heights than whatever the English design uses. And a serious build serves Arabic on its own routes — a real /ar tree rather than a ?lang=ar parameter — with per-language metadata, hreflang annotations, and an Arabic sitemap, because search engines treat each language version as a page in its own right. None of this comes from a translation plugin. A plugin swaps strings; it does not re-engineer a layout.
The four real cost drivers
When a serious quote itemizes its bilingual uplift, the money is going to four places:
- Design mirroring — every component reviewed and QA’d in both directions, not auto-flipped and shipped
- Native Arabic copy — business Arabic written by someone who writes in it, not translated word-for-word from English
- Per-language SEO — Arabic keyword research, metadata, and content structure as a separate exercise
- CMS structure — localized fields and editorial workflows so both languages can be maintained without calling a developer
What the UAE market actually charges
Across published offers from established Dubai agencies, bilingual EN/AR corporate sites are typically priced between AED 12,000 and 55,000, with the Arabic side accounting for that 15–30% uplift — AED 2,000–8,000 on a typical build. The uplift is not always visible as one line, though. It hides in per-page translation fees, ‘RTL adjustment’ charges, CMS localization modules billed separately, and Arabic content marked ‘client to provide’ — a phrase that quietly moves the hardest part of the job back onto you. When comparing quotes, add up everything Arabic touches, not just the row labelled bilingual.
How we build it — and what it costs
Every FATHOM build ships in English and Arabic. Not as an option, not as an uplift — included. Architecturally, the Arabic site is a parallel /ar route tree mirroring the English one, rendered by the same shared components with direction-aware CSS, so the mirroring is structural rather than patched page by page. The site you are reading works exactly this way: switch to fathom.ae/ar and you are looking at the proof, not a demo. Our Growth-track projects range from AED 8,000 to 45,000, and the 95+ PageSpeed score we commit to contractually applies to both language versions. Languages beyond English and Arabic are AED 1,400 each — engineering only: routing, layout, and typography QA — with the translation itself provided by you or quoted separately.
Our full rate card — including exactly what the bilingual scope covers — is public, generated from the same engine as our live estimator.
See the rate card →Bilingual SEO is a second campaign, not a checkbox
Arabic keywords are not translations of English keywords. Search volumes, phrasings, and intent all differ — Gulf users mix Arabic and English in a single query, move between dialect and Modern Standard Arabic, and see different results pages than English searchers do. That is why published UAE rates price Arabic or bilingual SEO at a 30–40% premium over English-only work, or as a dedicated programme at AED 3,000–8,000 per month. Budget for it as its own campaign, with its own keyword research and content plan. A site can be flawlessly engineered for RTL and still be invisible in Arabic search, because nobody ever asked what Arabic speakers actually type.
Red flags in cheap bilingual quotes
- Machine-translated copy — stilted Arabic that a native reader clocks in one sentence, and search engines increasingly clock too
- Layouts that break in RTL: numbers and punctuation jumping out of place, icons pointing the wrong way, text overflowing mirrored components
- Arabic living behind ?lang=ar or a bolted-on subfolder that still carries English metadata
- One hreflang tag and nothing else — no Arabic titles, descriptions, or sitemap
- ‘Arabic content by client’ buried in the exclusions
Arabic first, English first, or both at launch?
English first makes sense when your buyers are mostly international and the budget is tight — but architect for Arabic from day one, because retrofitting RTL onto a finished English site is where the horror-story budgets come from. Arabic first fits businesses selling to local, Arabic-preferring customers, with English following later on the same architecture. Both at launch is the right call whenever credibility in the UAE market matters — and for most businesses here, that means now. With the right architecture, the marginal cost of the second language is small, which is exactly why we stopped charging for it. So the honest question is not whether you can afford Arabic. It is whether the content will be ready — because the engineering, at least with us, is already in the price.