Skip to content
Web Designer in Dubai

· By Gagan Dutta

Building an Arabic and English website in the UAE: what a proper RTL build involves

Most bilingual websites I am asked to fix in Dubai were built in English first, with Arabic added the week before launch. It shows: text aligned to the wrong side, arrows pointing backwards, phone numbers scrambled, and an Arabic version Google has never indexed.

Arabic is not a translation layer on top of an English site. It is a second layout, a second typographic system and a second set of pages for search engines. This is how I build it in Next.js so both languages work equally well.

Give each language its own URL

Every page needs one address per language: /services for English and /ar/services for Arabic, for example. A language switch that swaps the text on the same URL, or stores the choice in a cookie, leaves search engines with only one version to index. The other language effectively does not exist in search.

In the Next.js App Router this is a locale segment in the route. Every page is still rendered ahead of time, so adding Arabic does not slow anything down.

I also avoid redirecting visitors automatically based on their location or browser language. Google's crawler does not send a language preference, so a forced redirect can hide a whole language from it. A visible language switch in the header, linking to the same page in the other language, is the reliable option.

Tell search engines which page is which

Each language version should point to the other with hreflang tags, and to itself. For a UAE business that usually means ar-AE and en-AE, plus an x-default for everyone else. The tags must be reciprocal: if the English page names the Arabic one but not the other way round, they are ignored.

Each version also keeps its own canonical URL, title and description, written in that language. A translated page with an English title tag is a common mistake and wastes the Arabic search result.

Right-to-left is a layout, not a text setting

Setting the page direction to right-to-left flips the reading order, but only a layout written for it will follow. I write CSS with logical properties: start and end instead of left and right. The same component then mirrors itself correctly in Arabic with no second stylesheet and no extra code for visitors to download.

Some things mirror and some must not:

  • Mirror: navigation order, back and next arrows, breadcrumbs, progress steps, sliders and the side a menu opens from.
  • Do not mirror: logos, photos, video controls, clocks, charts with a numeric axis, and brand icons.
  • Keep left-to-right inside Arabic text: phone numbers, email addresses, URLs, prices with Latin digits and product codes. These need explicit direction isolation or they appear with the digits and symbols in the wrong order.
  • Forms: labels and errors align to the right, but fields for email, phone and card numbers stay left-to-right.

Arabic typography needs its own decisions

Arabic letters are connected and carry marks above and below the line. At the same font size, Arabic looks smaller and tighter than Latin text. I set it slightly larger with more line height, and never apply letter spacing, which breaks the joins between letters. Uppercase styling and italics have no meaning in Arabic and should be switched off for it.

The font matters for speed as well as appearance. Arabic font files are larger than Latin ones, so I load the Arabic font only on Arabic pages, self-hosted and subset, with a fallback matched in size so the text does not jump when the font arrives. English visitors download none of it.

Translate the content, not just the words

People do not search in Arabic by translating English keywords word for word. Service names, the way an emirate or district is written and the level of formality all differ. The Arabic pages should be written or reviewed by a native speaker who knows how your customers in the UAE actually phrase things.

The same applies to structured data. The business name, address and service descriptions in the Arabic page's schema should be in Arabic and match your Google Business Profile in that language.

Checks before a bilingual site goes live

  • Every English page has an Arabic counterpart at its own URL, and the language switch lands on the same page, not the homepage.
  • The html element carries the correct lang and dir on every page.
  • hreflang tags are reciprocal and both versions are in the sitemap.
  • Titles, descriptions, image alt text and social share images are translated.
  • Phone numbers, prices and dates read correctly inside Arabic sentences.
  • The Arabic pages are tested on a real phone, not only a resized desktop browser.
  • Mobile speed is measured separately for each language, since the fonts and text length differ.

When to plan for it

Adding Arabic to a finished English site usually means reworking every component. Deciding on it at the wireframe stage costs very little: the layout is built direction-neutral from the first line of code.

If Arabic speakers are part of your market, tell me before design starts. If you already have a bilingual site that is not performing in Arabic, send me the link and I will tell you what is holding it back.

Start a project

Tell me what your website needs to do

Send me a few lines about your business and goals. I reply personally with next steps, and you get a fixed quote after a short call.

Refer a friend

Know someone who needs a website? Send them a quick recommendation.

WhatsApp me