The verdict in three sentences
Handling Arabic on a website is not translating text: it is reversing the entire reading direction (RTL), which affects layout, icons, forms and components. As a 2026 order of magnitude in Manchester, budget a base of 6,000 to 9,000 GBP, an RTL + Arabic module of 2,000 to 3,300 GBP, and professional translation at 0.10-0.14 GBP/word. The most underestimated item is dedicated RTL QA: without it, Arabic displays but breaks visually, and you lose credibility with the Arabic-speaking market.
The trilingual budget, item by item
A well-designed next-intl architecture handles three locales with no technical debt, provided RTL is treated at design time and not as a last-minute patch.
| Item | Indicative 2026 cost (GBP) |
|---|---|
| Base EN (design system, dev) | 6,000-9,000 GBP |
| RTL module + AR locale | 2,000-3,300 GBP |
| Pro FR translation (~6,000 words) | 550-800 GBP |
| Pro AR translation (~6,000 words) | 600-900 GBP |
| Hreflang + 3-language sitemaps | 400-600 GBP |
| RTL QA + native review | 700-1,200 GBP |
| Indicative trilingual total | 9,700-15,800 GBP |
The timeline extends by about three weeks versus an English-only site: Arabic requires a full visual QA pass (alignment, numerals, punctuation, mirrored form fields).
RTL: what breaks if you ignore it
RTL is not just a CSS attribute. Several elements must be handled explicitly, or the render becomes inconsistent.
| Element | LTR behaviour | Required RTL treatment |
|---|---|---|
| Reading direction | left to right | right to left |
| Directional icons (arrows) | point right | must flip |
| Forms and labels | left-aligned | right-aligned |
| Numbers and dates | unchanged | specific rules |
| Margins and paddings | fixed left/right | logical (start/end) |
| Arabic + Latin mix | rare | bidi to manage |
Using logical properties (margin-inline-start rather than margin-left) from the start avoids a costly rework. That engineering detail separates a clean trilingual site from a shaky patch.
Mini case study
Leila, marketing director of a services firm in Manchester, targets the UK, the Gulf and Europe. She chooses EN/FR/AR. Budget: base 7,000 + RTL module 2,600 + translations 1,400 + QA 1,000 = 12,000 GBP. The Gulf market represents a potential pipeline of several contracts at 5,000-13,000 GBP. Without a polished Arabic RTL version, her local credibility is nil; the RTL investment is therefore the condition of access to the most profitable market, not a cosmetic add-on.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
FAQ
Can Arabic be added later?
Yes, but it is more expensive if RTL was not anticipated: the layout must be reworked with logical properties. Planning RTL at design time costs 2,000-3,300 GBP; adding it afterwards can double that.
Is machine translation enough for Arabic?
No for B2B. Arabic carries strong register stakes (Modern Standard vs dialect). Native translation at 0.10-0.14 GBP/word is essential for credibility.
Does RTL slow the site down?
No if done properly: it is the same technical base with a reversed direction. No performance penalty, as long as you avoid improvised CSS overrides.
How long for an EN/FR/AR site?
Add about three weeks to an English site for Arabic: translation, RTL integration, full visual QA. QA is the item you must never compress.
Do we need separate URLs per language?
Yes, with hreflang: /en/, /fr/, /ar/. This prevents Google serving the wrong version and clarifies ranking on each market. Included in the hreflang item at 400-600 GBP.
Let's scope your project. Specify your three locales, priority markets and indicative budget: we price the base, the RTL module and QA separately. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
