A proper Arabic website is not your English site with the words swapped. Arabic reads right to left, so the whole layout has to mirror: navigation, text alignment, forms, tables and the order of columns. Each language also needs its own URL so Google can find, index and show the right version to the right person.
Get those two things right and most other details fall into place. This guide covers what that means in practice for a UAE business, the common mistakes, and what to ask your agency.
Why an Arabic version matters for UAE businesses
Arabic is the official language of the UAE. Plenty of your visitors are comfortable in English, but some will always prefer to read, search and enquire in Arabic, and audiences in sectors like healthcare and real estate often expect to find it. An Arabic version also lets you appear in Arabic searches that an English-only site cannot rank for.
The catch is that a poor Arabic version can do more harm than none. Broken layouts and machine-translated copy look careless, and in healthcare and property, careless wording can also create compliance problems.
Right-to-left (RTL) layout: the foundation
Set the direction in the HTML, not just the CSS
The W3C's internationalisation guidance is clear: add dir="rtl" to the html tag whenever the overall page direction is right to left, alongside the language (lang="ar"). It also warns: "Do not use CSS to apply base direction in HTML pages" (W3C, Structural markup and right-to-left text in HTML).
Set correctly, it does a lot of work for free: text right-aligns, table columns run right to left and form inputs start on the right. In W3C's words, "If you write the style sheet correctly, CSS will automatically mirror the layout."
Build with "start" and "end", not "left" and "right"
That "if" matters. Styles like margin-left stay stuck on the left in Arabic. Modern CSS has logical properties instead. MDN explains that they "define direction-relative equivalents to their corresponding physical properties", because "the start of a line is not always the left side of a line" (MDN, CSS logical properties and values).
The W3C recommends the same approach: use "start" and "end" rather than "left" or "right", for example margin-inline-start, padding-inline-end and text-align: start. Built this way, one stylesheet serves both languages, with no separate "RTL fixes" to drift out of date.
Mirror the right things (and only the right things)
When the layout flips, some elements should mirror and some should not. A quick checklist:
| Element | Mirror in Arabic? | Why |
|---|---|---|
| Navigation, sidebars, column order | Yes | The reading flow starts on the right |
| Back and next arrows, carousels, progress steps | Yes | They show direction of travel |
| Text alignment and form fields | Yes | Handled by dir="rtl" when built correctly |
| Logos, photos, videos | No | Flipping a photo or brand mark looks wrong |
| Phone numbers, prices, dates in digits | No | Numbers are written left to right |
| Icons with no direction (search, phone, home) | No | They mean the same thing either way |
On numbers, the W3C's Arabic layout requirements note: "Arabic script is written from right to left. Numbers, even Arabic numbers, are written from left to right" (W3C, Arabic & Persian Layout Requirements). The same document points out that the digits used across the Arab world and their formatting vary, so agree with your agency which digits you will use for prices, phone numbers and dates, and use them consistently.
Forms and mixed text
Contact and booking forms are where Arabic sites most often break, because users mix Arabic text with English email addresses and phone numbers. The W3C suggests dir="auto" on form fields and inserted text so the browser works out the direction of what the user typed. Test every form with real mixed input before launch, including any WhatsApp booking flow you link to.
Bilingual SEO: how Google sees an Arabic and English site
Give each language its own URL
Google recommends using a different URL for each language version, rather than cookies or browser settings that change the language on the same URL. It also warns that if you change content or redirect based on language settings dynamically, it "might not find and crawl all your variations", partly because Googlebot usually crawls from the USA (Google Search Central, Managing multi-regional and multilingual sites).
Google lists the main URL options with their trade-offs:
| Structure | Example | Google's notes |
|---|---|---|
| Subdirectory | example.com/ar/ | Easy to set up, low maintenance (same host) |
| Subdomain | ar.example.com | Easy to set up, allows different server locations |
| Country-code domain | example.ae | Clear geotargeting, but can only target one country and has stricter requirements |
| URL parameter | example.com?lang=ar | Marked "Not recommended" |
For most UAE businesses with one site in two languages, a subdirectory such as /ar/ is the simplest and cheapest to run, and it keeps all your SEO authority on one domain.
Don't auto-redirect visitors
Google advises against sending visitors to a language version automatically: "Avoid automatically redirecting" users between language versions, because it can stop people and search engines from reaching every version. Instead, add a clear language switcher on every page that links to the same page in the other language.
Add hreflang tags correctly
Hreflang tags tell Google that /services/ and /ar/services/ are the same page in two languages. Google accepts them in the HTML head, in HTTP headers or in your sitemap, and says "the three methods are equivalent" (Google Search Central, Tell Google about localized versions of your page).
Two rules trip people up:
- Every version must list itself and all the others. Google states: "If two pages don't both point to each other, the tags will be ignored."
- Use full URLs, including
https://.
The language code comes first in ISO 639-1 format (ar, en), optionally followed by a region. Google also suggests an x-default entry as a fallback for languages you don't list, which is useful on a language selector page.
Write real Arabic content, not translated menus
Google uses "the visible content of your page to determine its language", not the lang attribute or the URL. It also warns that translating only the menus and footer while the main content stays in English "can create a bad user experience". So an Arabic page needs Arabic body copy, Arabic headings, Arabic page titles and meta descriptions, and Arabic image alt text.
Do keyword research in Arabic too, because people rarely search with a literal translation of the English phrase. Our guide to SEO for Google AI Overviews applies to Arabic pages as well.
Common mistakes we see on Arabic websites
- A mirrored theme with English-only plugins. The page flips, but the booking widget, cookie banner or chat box stays left to right.
- Machine translation with no human review. It reads stiffly to native speakers, and in healthcare or property it can change the meaning of a claim.
- One URL for both languages. The language switches with a cookie, so Google indexes only one version.
- Missing Arabic metadata. Body text is Arabic but titles and descriptions are still English, so search results look half-finished.
- Weak Arabic fonts. A Latin-first font makes Arabic body text hard to read on phones, and extra font files can slow pages, so check Core Web Vitals on the Arabic version too.
What to ask your web agency
Before you approve a bilingual build, ask:
- Is the site built with
dir="rtl"and CSS logical properties, or with a separate RTL stylesheet bolted on? - What URL structure will each language use, and will every page have hreflang tags?
- Who translates and reviews the Arabic content, and is that person a native speaker?
- How will forms, WhatsApp buttons, maps and third-party widgets behave in Arabic?
At Mistique Designs we build bilingual Arabic and English sites for clinics, property firms and other businesses in Dubai and across the UAE. You can see how we approach it on our website development service and Dubai web design pages.
Frequently asked questions
Do I need a separate website for Arabic?
No. Most businesses are best served by one website with Arabic pages in their own folder, such as /ar/, plus hreflang tags linking each page to its English version. A separate country-code domain is an option, but it is more work to maintain.
Can I use Google Translate or an AI tool for my Arabic content?
AI tools can give a useful first draft, but have a native Arabic speaker review every page before it goes live, especially in healthcare and property where wording can carry legal weight.
Should my site detect Arabic users and switch automatically?
Google advises against automatically redirecting users between language versions. Show a clear language switcher on every page and let visitors choose, and use hreflang so search results show the right version.
Does adding Arabic help my SEO in the UAE?
It lets you appear in Arabic searches that an English-only site cannot rank for, as long as the Arabic pages have real Arabic content, their own URLs and correct hreflang tags.
The bottom line
A good Arabic website comes down to three things: a layout built for right-to-left reading from day one, a separate URL for each language linked with hreflang, and Arabic content written or reviewed by a native speaker. Get those right and your site will feel local to Arabic-speaking customers and be visible in their searches.
Planning an Arabic and English website for your UAE business? Talk to us and we will tell you exactly what your project needs.

