Every business we build a website for in the UAE asks some version of the same question: does the site really need to work in both Arabic and English, or is English enough since "everyone here speaks English anyway"? It's a fair question. It's also the wrong one, because it treats language as a formality instead of what it actually is: the first signal a visitor uses to decide whether a business was built for them.
The audience isn't who the question assumes it is
The UAE's population is overwhelmingly expatriate, and English genuinely is the working language of most business here. That part is true. But "most people can read English" and "most people prefer to transact in English" are different claims, and the gap between them is where conversions get lost. A landing page in English-only doesn't fail because visitors can't read it - it fails quietly, because a meaningful share of them close the tab and go find a competitor whose site greeted them in the language they'd actually choose to fill out a form, read a contract, or message a business in.
That's true for Emirati customers first, but it's also true for a large part of the expatriate population - the UAE has one of the most linguistically diverse resident populations anywhere, and Arabic isn't the only "other" language worth thinking about depending on the industry. The point isn't "translate everything into every language." It's that English-by-default is itself a choice, and it's worth knowing what that choice costs.
What actually moves the needle on conversion
In practice, three things matter more than raw translation coverage:
- The first screen, not the whole site. A visitor decides whether a business "gets" them within seconds of landing - the hero headline, the trust signals, the CTA. If that first screen is in a language that doesn't match what they'd choose, everything below it has to work harder to earn trust back.
- Forms and contracts, not just marketing copy. A beautifully translated homepage sitting in front of an English-only contact form or quotation document is a worse experience than a plainer site that's consistent end to end. Businesses lose more trust at the point of commitment than at the point of browsing.
- Speed of switching, not presence of a toggle. Having a language button is not the same as having a fast one. If switching languages reloads the whole page, loses the visitor's scroll position, or takes a visible beat to update, it reads as an afterthought bolted onto an English site rather than a real bilingual product.
The SEO case is separate from the UX case
Even businesses that are confident their customers read English fine still have a reason to build real Arabic content: search behavior doesn't match reading ability. People search in the language they think in, not necessarily the language they'll transact in - which means an English-only site is invisible to a meaningful share of the searches that would have found it, regardless of whether those searchers could have read the English page just fine once they landed on it. This is a distinct problem from on-page UX, and it needs distinct content - not a machine-translated layer bolted on top of English copy, but real Arabic sentences written to answer real Arabic search queries.
Toggle vs. separate URLs - the technical decision nobody explains
There are two honest ways to build a bilingual site, and most businesses never get told the tradeoff:
A client-side toggle (one URL, JavaScript swaps the visible language) is faster to build and keeps a single page's design perfectly in sync across both languages - but search engines primarily index whichever language state renders by default, so the "other" language gets little to no independent search visibility of its own.
Separate URLs per language (with proper hreflang tags connecting them) means real, independently-indexable pages in both languages - genuinely better for search - but it roughly doubles the content and maintenance work, since every future change has to land twice, correctly, in both places.
Neither is wrong. What's wrong is picking one without knowing which problem it solves - a toggle is a UX decision, separate URLs are an SEO decision, and a site that needs both often ends up needing a genuine hybrid: real per-language URLs for anything meant to be found in search, with fast client-side switching for the browsing experience once someone's already on the site.
What we'd actually recommend
If a business's growth depends on being found - not just browsed once someone already has the link - real per-language pages for anything with search intent behind it (product pages, service pages, high-value landing pages) are worth the extra build time. A fast toggle is still the right call for the parts of a site people navigate rather than search for. Building a UAE-facing site as English-only "by default" isn't really a decision at all - it's just not making one, and leaving the actual decision to whichever visitor gives up first.