Bilingual Arabic and English Website SEO in the UAE

What Google says about multilingual and multi-regional sites

This guide is based on two pages from Google Search Central that we read for this article: the documentation on localized versions of your pages, and the guide to managing multi-regional and multilingual sites. Where we go beyond them, such as practical advice on design and process, we say so. Google can change its documentation, so verify the current versions before you build.

The main points from those pages are these. Each language version should have its own URL. Google uses its own algorithms to detect a page's language from the visible content, not from the lang attribute or hreflang. Hreflang annotations tell Google which version belongs to which audience, and they must be reciprocal. Avoid automatic redirects based on guessed language or location, and avoid showing different content on the same URL depending on cookies or IP address, because Googlebot mostly crawls from the US and does not send Accept-Language headers.

Choosing a URL structure

For most service businesses in the UAE, subdirectories on one domain are a practical default, because the authority of one domain supports both languages and there is only one site to maintain. This is our practical view, not a Google ranking rule. If you operate in the UAE and in other countries, you may later add region-specific versions, and the same hreflang principles apply.

Do not use a single URL that changes language based on a cookie or a language selector without a URL change. Visitors may like it, but crawlers cannot see both versions.

Hreflang step by step

1. List the page pairs. For each Arabic page, identify the English page with the same intent. If one page has no equivalent, leave it without hreflang rather than pointing to an unrelated page.
2. Use fully qualified URLs. Google's documentation asks for the protocol and domain, for example https://www.example.com/en/page/, not a relative path.
3. Add every version to every page. Each page lists itself and all alternates. If page A points to B, B must point back to A, or the annotation may be ignored.
4. Choose language codes carefully. Use ISO 639-1 language codes, optionally with an ISO 3166-1 region, such as ar, en, or en-AE. A region code alone is not valid.
5. Consider x-default. It marks the fallback page for users whose language does not match any version, often a language selector or home page.
6. Pick one method. HTML link elements, HTTP headers or XML sitemap entries are equivalent; using several adds no benefit.
7. Test and monitor. After launch, spot-check pages and watch for crawling or indexing problems in Search Console.

A simplified example of the HTML method on an English page, with the Arabic alternate and x-default: link rel="alternate" hreflang="en" href="https://www.example.com/en/page/", the same for hreflang="ar" with the /ar/ address, and hreflang="x-default" pointing to the chosen fallback. The same three lines appear on the Arabic page.

Language and region: ar, en, en-AE or ar-AE?

If you serve one country and one language pair, plain ar and en are usually enough and easier to keep consistent. Region codes help when you have several versions of the same language for different countries, for example an English page for the UAE and another for Saudi Arabia with different currency, phone numbers or legal wording. In that case, Google recommends providing a generic catch-all for the language. Do not add region variants unless the content really differs. Duplicated pages with only a region code can create maintenance work without benefit.

Right-to-left design that works

Google's pages we reviewed do not discuss right-to-left layout, so the following is practical advice from website building, not a search requirement. Set the document direction to right-to-left on Arabic pages, and let the layout mirror properly: navigation order, icons with direction, breadcrumbs, form labels and table alignment. Choose Arabic fonts with proper weights and line height, since Latin fonts rarely have Arabic glyphs and fallback fonts often look uneven. Check numerals, phone numbers and mixed English brand names inside Arabic sentences, which can break direction when not handled.

• Direction set per page: Arabic pages are right-to-left, English pages left-to-right.
• Mirrored components: menus, sliders, arrows, steps and progress bars.
• Tap targets and forms: labels, placeholders and validation messages in Arabic.
• Typography: a real Arabic font, comfortable line height, no clipped diacritics.
• Mixed text: phone numbers, prices and English names display in the right order.
• Images with text: use separate Arabic versions, not English banners.

Write natively, do not auto-translate

Machine translation is a useful first draft for a human, but publishing it unreviewed is risky. Google's multi-regional guidance warns against translating only the boilerplate while the main content stays in one language, and Arabic copy translated word for word often reads unnaturally. Native writing also lets you adapt search terms: people search in Arabic and English using different words and different modifiers, such as area names, so do keyword research per language. See our Dubai local SEO guide for how local intent works.

Localized versions of a page are not treated as duplicates when the main content is translated. This gives you the freedom to make the Arabic version shorter, longer or structured differently, as long as it serves the same intent.

Titles, descriptions and on-page elements per language

Each language page needs its own title, meta description, headings, image alt text, schema text and internal link anchors in that language. Keep the navigation and footer in the page language too. Google's guidance is to use a single language for content and navigation on each page. An Arabic page with an English menu, or the reverse, sends mixed signals and a poor user experience. If you are weighing how much search work the whole site needs, the SEO cost guide covers scope.

Language switcher and redirects

Put a visible link to the other language on every page, ideally to the equivalent page rather than the home page. Google advises hyperlinks to alternate versions. Do not force a redirect based on the visitor's browser or location; suggest the other language with a banner that can be closed and let people choose. If you must redirect at the home page, keep all language versions directly reachable and crawlable, and test with a crawler that does not send language headers.

Sitemaps, canonicals and indexing

Each language page should canonicalise to itself, not to the other language, otherwise you tell Google to ignore a version. Include both language versions in the XML sitemap, with hreflang entries if you use the sitemap method. Sitemaps must only list URLs under the directory where the sitemap is hosted, so a root sitemap works for subdirectories. Submit the sitemap in Search Console and review which URLs are indexed for each language. If one language lags, look at internal links and content quality before blaming hreflang.

Common mistakes on bilingual sites

Launch checklist for a bilingual site

1. Map the pages. Decide which pages exist in both languages.
2. Set the URL pattern. Lock it before design to avoid redirects later.
3. Write native content. Brief the writers on keywords per language.
4. Add hreflang and canonicals. Check reciprocity page by page.
5. Test RTL and mobile. Review forms, menus and buttons in both languages.
6. Set up tracking. Track calls and WhatsApp clicks per language; see conversion tracking for calls and WhatsApp.
7. Submit sitemaps. Monitor coverage in Search Console.

If you are still choosing a provider for the build, our web design agency scorecard includes a question about Arabic handling. If you are redesigning an existing site, protect rankings with the steps in the redesign checklist. Because AI search features also read your pages, AI search optimization in the UAE is worth reading after launch.

Content planning across two languages

Decide early which pages truly need both languages. A service business usually wants the home page, service pages, contact page and a few trust pages in both, while an older blog archive might be kept in one language until there is capacity to write the other natively. Publishing a thin duplicate just to have both languages adds maintenance with little benefit. Set a rule for new content: either publish in both languages together or note which one comes first and when the second follows, and add hreflang only when the pair exists.

Assign owners for each language, including a reviewer who reads the Arabic output as a customer would. Keep a shared glossary of service names, area names and the way your brand is written in each script, so that titles, buttons and schema stay consistent across pages and over time.

How we work at ZED

ZED Marketing works on eight services: Google Ads, SEO, website design, social media management, content videos, conversion tracking, medical marketing and real-estate marketing. You send a short description of your business through WhatsApp or the contact page, and ZED replies with an initial plan and notes. Learn more about our website service and SEO service.