Most "bilingual" websites in the Gulf are English websites with Arabic text poured into an English layout. The text translates; the product does not. Real Arabic-English delivery is an engineering discipline with five layers, and skipping any of them shows immediately to the half of your market that reads Arabic first.

Why "we support Arabic" usually means "we mirror the CSS"

Flipping a layout right-to-left is one CSS property. What it does not fix: icons that still point the wrong way, numbers and dates rendering inconsistently, forms that misalign labels, truncated Arabic strings in buttons sized for English, and typography set in a font that treats Arabic as an afterthought. Users do not file bug reports about this. They just register that the company's Arabic experience is second-class, and draw the obvious conclusion about how they will be treated as customers.

The five layers of real bilingual delivery

1. Layout engineering. Logical CSS properties (start/end, not left/right) so every component genuinely reflows; directional icons and progress indicators that flip with intent; media and cards that keep visual hierarchy in both directions. This is built in from the first component, retrofitting it costs multiples. 2. Arabic typography. Arabic is not a font fallback. It needs a typeface designed for it, correct line heights (Arabic needs more vertical room), and weight pairing with the Latin face so headlines carry the same authority in both languages. Gulf-natural phrasing matters too: machine-translated marketing copy reads as foreign to a Doha or Riyadh buyer instantly. 3. URL architecture. Each language gets real, indexable URLs, ours live under /ar/, not a JavaScript toggle that shows different text at the same address. Search engines index URLs; if Arabic content has no URL of its own, it does not exist to Google, and as of 2026 it does not exist to AI search surfaces either, which only cite indexed pages. 4. hreflang pairing. Every English page declares its Arabic twin and vice versa, so Google serves the right language to the right searcher in Qatar, the UAE, and beyond. Done wrong, the languages compete against each other; done right, you hold two sets of rankings. 5. Content parity. The Arabic site is the full site, services, case studies, pricing, forms, not a brochure subset. Parity is also a trust signal: it tells Arabic-first buyers they are a primary audience, not an accommodation.

What it means commercially

Arabic-language queries (شركة تصميم مواقع قطر, تطوير برمجيات الدوحة) face dramatically thinner competition than their English equivalents, while the buyers behind them are just as real. In our own engagements, [bilingual implementation is included from the first tier](/pricing) (from $2,500 ≈ QAR 9,000) because in this market we consider it structural, not premium. Every layer above is standard in our [web development](/services/web-development) work, and our own site practices what this post preaches: every page you are reading exists at an /ar/ twin, hreflang-paired.

How to audit any "bilingual" proposal in five minutes

Ask to see a shipped bilingual project. Then: switch to Arabic and check the URL changed; resize the browser and watch the RTL layout hold; read one paragraph aloud with a native speaker; view source and look for hreflang tags; compare the Arabic sitemap to the English one. Any vendor who passes all five has done this before. Most have not, which, in a bilingual market, is exactly your opening. See how we build it across [our shipped work](/work).