Bilingual SEO in the UAE: Arabic and English Guide

Bilingual search engine optimization (SEO) is the work of making a website's Arabic and English versions each findable, correctly labeled and shown to the right searcher on Google. Bilingual SEO in the UAE comes down to one job: a clean Arabic page and a clean English page, wired together so each one reaches its own audience.

Most guides on this topic come from agencies selling bilingual websites. This one sticks to Google's own documentation.

What is bilingual SEO, and does a UAE business need it?

A UAE business needs bilingual SEO when a real share of its customers search in Arabic and it wants Arabic pages that rank on their own. It is not a legal requirement for every private website. It is a market decision, and the UAE's language mix makes the case strong.

Arabic is the official language of the UAE. The UAE Government states that all road and traffic signs and signs on commercial outlets are in Arabic and English, and that expatriates outnumber UAE nationals. Your customers read both languages every day, often on the same street.

Search in the UAE means Google. Google held 93.47% of UAE search engine market share in September 2026, according to StatCounter.

Almost everyone is reachable. 11.3 million people in the UAE used the internet in October 2025, a penetration rate of 99.0%, according to DataReportal's Digital 2026 report.

For most UAE businesses, then, bilingual SEO is Google SEO done twice, once per language, with the two versions wired together correctly. For more market data, see my SEO and AI search statistics for the UAE.

How does Google decide which language a page is in?

Google decides a page's language by reading its visible content. It does not read the HTML lang attribute or the web address (URL) for this, and it does not use hreflang to detect language either. If an Arabic page carries English menus or English product copy, Google sees a mixed page.

Google's multilingual guidance says it uses the visible content of your page to determine its language and does not use code-level information such as lang attributes.

Google's hreflang documentation, last updated in September 2026, goes further: Google doesn't use hreflang or the HTML lang attribute to detect a page's language. Google's algorithms decide that from the text.

Many UAE sites trip over language detection. A developer adds lang="ar" and dir="rtl" to a template, the Arabic copy is half finished, and the team assumes Google now sees an Arabic page.

Google gives three practical rules for the page itself:

• Use one language for both the content and the navigation on each page.
• Avoid side-by-side translations, such as Arabic and English paragraphs stacked on one page.
• Don't translate only the menu and footer while the main content stays in one language.

Keep the lang and dir attributes for browsers and right-to-left (RTL) display. Just don't count on them to tell Google anything.

Which URL structure works best for an Arabic and English site?

For most UAE businesses, the URL structure that works best is one domain with a folder per language, such as /en/ and /ar/. Google recommends a separate URL for each language version rather than switching language with cookies or browser settings, and Google lists subfolders as easy to set up and low maintenance.

Source: Google Search Central, “Managing multi-regional and multilingual sites”, last updated 10 December 2025, checked 12 October 2026.

A country-code domain such as .ae is a strong signal that a site targets the UAE. That helps if every customer is local. It also limits you, because a country domain can only target one country, so a .ae site is the wrong base for selling across the Gulf.

Google also reads local addresses, phone numbers, currency, local links and your Business Profile. A subfolder structure can add a third language later without a new domain, which makes it the practical default for multilingual SEO in Dubai.

How do you set up hreflang for Arabic and English pages?

Set up hreflang by giving every Arabic page and its English twin the same set of annotations, listing both versions, including the page itself. Use ar-AE for Arabic and en-AE for English, add an x-default fallback, and make sure each page points back to the other. Google ignores one-way annotations.

hreflang is an annotation that tells Google which URLs are language or region versions of the same content. It helps Google show the Arabic page to an Arabic searcher and the English page to an English searcher.

Here is the full hreflang Arabic English setup for one pair of pages:

<link rel="alternate" hreflang="en-AE" href="https://example.com/en/services/" />
<link rel="alternate" hreflang="ar-AE" href="https://example.com/ar/services/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/services/" />

The same three lines go in the <head> of both pages. The third line names the page Google shows when a searcher's language matches neither.

Google's rules for these annotations are strict:

• Each version lists itself and every other version.
• The pages must point to each other. Google states that if two pages don't both point to each other, the tags will be ignored.
• Use full URLs that start with https://, not relative paths.
• The first code is the language, from the ISO 639-1 standard. The optional second code is the region, from ISO 3166-1 Alpha 2. A region code on its own is invalid, so hreflang="AE" does nothing.
• x-default is the fallback for visitors whose language you don't serve. It can point to the English page or to a language selector.
• Pick one method: HTML tags, HTTP headers or the XML sitemap. Google treats the three as equal and gains nothing from using all of them.

Use ar-AE when the Arabic pages are written for UAE customers, with prices in dirhams (AED) and UAE phone numbers. Use plain ar if one Arabic page serves the whole Gulf.

Is translated content duplicate content?

No. Google says localized versions of a page count as duplicates only if the main content stays untranslated. A properly translated Arabic page is a separate page, not a copy. The real risk is elsewhere: publishing large volumes of automated translation that add little for the reader.

Google's hreflang documentation states that localized versions are only considered duplicates if the main content remains untranslated. Many agency guides still warn that translation creates duplicate content. It doesn't.

The risk Google does name sits in its spam policies. Scaled content abuse is Google's term for many pages made mainly to manipulate rankings rather than help users. Google's examples include generating pages through automated transformations such as translating, where little value is provided to users.

A plugin that machine-translates a whole site overnight, with nobody reviewing the Arabic, fits that description far better than a reviewed Arabic site does.

Google may already be translating your English pages

Google runs a feature called translated results. When someone searches in Arabic and a strong match is in English, Google may translate the title link and snippet of that result into Arabic. Arabic is one of the languages Google supports for this feature. A click opens a machine-translated view of your page.

You can see this in Google Search Console. Open the Performance report and use the Search Appearance filter to find impressions and clicks from translated results. Arabic searchers landing on a machine translation of your English page is the clearest case for building a real Arabic page.

If you'd rather not appear this way, Google's notranslate rule opts a page out of all its translation features.

Why Arabic SEO is not translated English SEO

Arabic SEO is the work of making Arabic pages rank for the words Arabic-speaking customers actually type, which are not always a literal translation of your English keywords. Treat it as its own project: separate keyword research, Arabic-first page copy, and technical settings that let Google find every Arabic URL.

Start with research in Arabic. Set the location to the UAE and the language to Arabic in your keyword tool, then have a native speaker review the list.

If you need Arabic pages written from that research rather than translated, my SEO content writing services in Dubai cover both Arabic and English.

Next, remove automatic language redirects. Google says Googlebot's default IP addresses appear to be based in the USA and that it sends requests without an Accept-Language header. A site that switches visitors to Arabic or English based on their internet protocol (IP) address or browser settings can hide one version from Google completely.

Google advises against redirecting users based on what you think their language is. It recommends visible links to the other language version on every page instead.

The same one-language rule reaches Google Maps. Google Business Profile guidelines say repeating the same business name in multiple languages is not acceptable, even when the shop sign shows both. Pick the form customers use most. I cover the other profile rules in my guide to local SEO in Dubai.

How do Arabic pages show up in Google AI Overviews and AI Mode?

Arabic pages now compete inside Google's artificial intelligence (AI) answers as well as the regular results. As of 12 October 2026, Google lists both Arabic and the UAE for Google AI Overviews, and Google AI Mode has supported Modern Standard Arabic since October 2025. Thin or machine-translated Arabic pages give either system little to work with.

Google's AI Overviews help page lists Arabic and the United Arab Emirates among supported languages and countries, checked on 12 October 2026. Arabic support arrived with the May 2025 expansion, announced by Hema Budaraju, Vice President, Product Management, Search at Google. She wrote that AI Overviews were launching “with support added for Arabic, Chinese, Malay, Urdu and more.”

On 8 October 2025, Google began rolling out AI Mode in 38 new languages, including Modern Standard Arabic. As of 12 October 2026, Google's AI Mode help page lists Arabic and the UAE as supported. Google AI Mode uses query fan-out, which Google describes as breaking a question into subtopics and running many searches at once. Google says early AI Mode users ask questions two or three times the length of traditional searches.

Longer questions pull in more specific passages. An Arabic page that answers a real question in clear Modern Standard Arabic gives Google AI Overviews and Google AI Mode something to retrieve. Writing Arabic pages for retrieval is the same discipline as Generative Engine Optimization (GEO), the work of getting pages cited inside AI answers.

What to check every month on a bilingual site

A bilingual site drifts. New English pages launch without Arabic twins, and hreflang breaks without anyone noticing. A short monthly check catches most of it:

• Every new page has a language twin, or is single-language on purpose.
• Each Arabic and English pair points to the other, with full https:// URLs.
• No page mixes Arabic and English body copy.
• No redirects depend on IP address or browser language.
• Arabic URLs show as indexed in Google Search Console.
• Translated-results impressions are reviewed in the Search Appearance filter.
• The Google Business Profile name appears in one language only.

If your Arabic pages exist but never rank, the cause is usually technical before it is editorial. As a technical SEO consultant in Dubai, I audit bilingual sites for the problems covered here. The audit covers hreflang return links, language mixing on one page, redirects that hide Arabic URLs from Googlebot, and Arabic pages that never get indexed. Each fix goes to your developers as a ticket with the affected URLs and a test.