Arabic SEO for UAE Businesses: How to Build Content That Works in Arabic and English
Arabic SEO for UAE businesses: when Arabic pages pay off, Arabic keyword research, hreflang, URLs, metadata, schema and a bilingual content framework.
Quick answer
Arabic SEO for UAE businesses means publishing Arabic pages that Arabic-speaking searchers can find and trust, alongside English pages, with keyword research done in Arabic, correct hreflang and canonicals, Arabic metadata and schema, right-to-left layouts and separate measurement. It is a content and technical discipline in its own right, not English pages with Arabic keywords added.
Not every UAE search needs an Arabic page. English is the everyday business language for a large share of residents, so the right question is which audiences, pages and queries justify Arabic. This guide sets out how to decide, how to research Arabic queries properly, how to structure a bilingual site for search, and how to measure each language on its own terms.
Figures in this guide are sourced and dated. Everything else is our recommendation and is labelled as such. Industry examples are hypothetical. For the development and right-to-left build work behind a bilingual site, see our companion guide to multilingual website development in the UAE.
Key takeaways
- Arabic pages pay off for specific audiences: government and semi-government buyers, Emirati consumers, Arabic-speaking residents and Saudi or wider GCC expansion.
- Arabic is the UAE's official language (Constitution, Article 7), and UAE-registered ecommerce businesses must provide product information and consumer invoices in Arabic. We found no general legal requirement for business websites to be in Arabic.
- Seed keyword research in Arabic, then check spelling variants (alef, taa marbuta, yaa), diacritics, Gulf versus Modern Standard Arabic terms and, occasionally, Arabizi.
- Give each language its own URL, a self-referencing canonical and reciprocal hreflang (ar-AE, en-AE and x-default). Never canonicalise Arabic to English.
- Write Arabic titles, descriptions and structured data from the Arabic page. Schema must match the visible Arabic text.
- Bulk machine-translated pages with little value fall under Google's scaled content abuse policy. Use fluent human review.
- AI Overviews have supported Arabic since 20 May 2025 and AI Mode since 8 October 2025, so useful Arabic content now feeds AI answers too.
- Measure Arabic and English separately in Search Console and analytics, by page language.
Does every UAE business need Arabic SEO?
The answer first: no. Arabic SEO is commercially justified when Arabic-speaking buyers are a meaningful part of your market, when the buying process is conducted in Arabic, or when regulation requires Arabic content. Many UAE businesses can rank and sell well in English and add Arabic selectively.
UAE facts. The UAE population is overwhelmingly expatriate: the latest official breakdown we could verify, from 2011, counted about 88.5% expatriates and 11.5% UAE nationals (National Bureau of Statistics, reported by Khaleej Times). More recent estimates of about 89% circulate only on secondary sites, so treat the exact share as dated. We found no source that measures the split between English and Arabic search queries in the UAE.
Two cautions follow. First, 'expatriate' does not mean 'English speaker': many residents come from other Arab countries and may search in Arabic. Second, a small share of the population can still be a large share of a market. Emirati households, government entities and semi-government companies often carry high purchasing power and contract value.
Search supply also matters. W3Techs estimates that Arabic is the content language of 0.6% of websites whose language it can identify, against 49.5% for English (W3Techs, 8 October 2026). That measures websites, not demand, but it suggests that a well-made Arabic page often competes in a thinner field than its English equivalent. Our recommendation is to test this in your own niche rather than assume it.
| Audience | Why Arabic matters | Typical Arabic scope |
|---|---|---|
| Government and semi-government buyers | Arabic is the official language of federal authorities; tenders and decision-makers often work in Arabic | Service pages, capability statements, case studies, contact and procurement pages |
| Emirati consumers | Language preference, trust and cultural fit, especially in premium and family purchases | Product or service pages, FAQs, checkout and support content |
| Arabic-speaking residents | Many search in Arabic for everyday services, health, education and property | High-intent pages and local landing pages |
| Saudi and GCC expansion | Larger Arabic-first markets; see our UAE to Saudi expansion guide | Full parity, often with market-specific pages |
| UAE-registered ecommerce | Arabic product information and invoices are legal requirements | Product information, invoices and the purchase path at minimum |
| Expatriate-focused B2B services | Buyers usually search and buy in English | English first; Arabic summaries for key pages may be enough |
The Arabic language context in UAE law
UAE facts. Article 7 of the UAE Constitution states that 'the official language of the UAE is Arabic' (Constitute Project). Under Federal Law No. 15 of 2020 on consumer protection, as amended by Decree-Law No. 5 of 2023, consumer invoices must be in Arabic (other languages are optional), and ecommerce businesses registered in the UAE must provide information about their products and services in Arabic (u.ae consumer protection).
A draft federal Arabic Language Law is in progress. Khaleej Times reported on 30 April 2026 that the Ministry of Culture had received approval to draft the law, that the Federal National Council had discussed it, and that it would require Arabic in public-facing advertising and promotional campaigns, with penalties and incentives. Officials also spoke about integrating Arabic into AI systems and digital platforms. The report did not describe specific obligations for business websites (Khaleej Times). As far as we could verify, it remained a draft in October 2026.
What this means in practice: if you run a UAE-registered online store, Arabic product information is not optional, whatever your SEO plan says. If your website promotes products or services to the UAE public, watch how the final law defines advertising. Neither point is legal advice; confirm your obligations with the relevant authority or a UAE-qualified adviser.
Worth noting
We found no general legal requirement that a UAE business website must be published in Arabic. The firm obligations we could verify are Arabic consumer invoices and Arabic product information for UAE-registered ecommerce businesses.
A bilingual content strategy framework: three tiers
The answer first: decide Arabic coverage page by page, not site by site. Most UAE businesses fit one of three tiers, and many mix them: full parity for the pages that sell, key pages in Arabic for the pages that build trust, and English-only pages with an Arabic summary for long-tail content.
Tier 1, full parity. Every customer-facing page exists in both languages with equivalent depth. This suits Arabic-first audiences, government-facing businesses, UAE-registered ecommerce and GCC expansion. It costs the most to maintain, because every update must ship in both languages.
Tier 2, key pages. Home, core service or category pages, top products, about, contact, pricing guidance and the main FAQs exist in Arabic. Blog and resource content stays in English. This suits most UAE SMEs that sell to a mixed audience.
Tier 3, English with Arabic summaries. English pages carry the depth, and a short, fully Arabic page per service or topic answers the main questions and routes to Arabic-speaking staff. Keep each page in one language: Google advises against side-by-side translations on the same page. This suits expatriate-focused B2B businesses that still want to be found by Arabic searchers.
| Decision question | If yes | If no |
|---|---|---|
| Are you a UAE-registered ecommerce business? | Arabic product information is required; plan Tier 1 for the product and purchase path | Continue |
| Do government or semi-government buyers make up a meaningful share of revenue? | Tier 1 for services and capability pages | Continue |
| Do Arabic queries appear in Search Console, ads data or enquiries already? | Tier 2 at least, starting with the pages those queries reach | Test with Tier 3 summaries |
| Are you expanding to Saudi Arabia or the wider GCC? | Tier 1, possibly with market-specific Arabic pages | Continue |
| Can you staff Arabic replies to enquiries? | Publish Arabic contact paths prominently | Do not promise Arabic support you cannot deliver |
| Can you fund fluent Arabic review for every update? | Choose the tier you can maintain | Reduce scope; a stale Arabic page is worse than none |
Pro tip
Pick the tier you can keep current. An Arabic page with last year's prices, an expired offer or a broken form damages trust more than a clear English page with an Arabic contact option.
How to do Arabic keyword research
The answer first: start from Arabic, not from translated English keywords. Ask Arabic-speaking customers and staff how they describe your service, collect the Arabic terms used by competitors and marketplaces, then expand and validate those seeds in keyword tools, Search Console and Google Trends set to Arabic.
Step 1: seed in Arabic. Translation produces the term a dictionary prefers, not the one a buyer types. Collect seeds from sales calls, WhatsApp enquiries, Arabic reviews, competitors' Arabic pages, Arabic marketplace listings and the Arabic autocomplete suggestions Google shows.
Step 2: expand per language. In Google Keyword Planner, set the language to Arabic and the location to the UAE (and separately to Saudi Arabia if relevant). Repeat in English. Do not compare Arabic and English volumes as if they measure the same thing, and treat low-volume Arabic terms with care: keyword tools often round or group small numbers. We do not quote volumes here because they change and depend on the tool.
Step 3: validate with your own data. Search Console shows the Arabic queries that already trigger impressions, even on English pages. Google Trends lets you compare the relative interest of two Arabic phrasings in the UAE. Paid search query reports, if you run Arabic ads, are the most reliable evidence of what converts.
Step 4: map one primary intent to one page per language. Group variants that share intent onto one Arabic page, just as you would in English. Avoid separate pages for each spelling variant.
Step 5: check the results page. Search each primary Arabic query yourself. Note whether Google returns Arabic pages, English pages, marketplaces, government portals, maps or an AI Overview. That tells you what kind of page can compete.
- Seeds collected from customers, staff and Arabic competitors, not from a translation tool
- Keyword Planner run separately for Arabic and English, UAE location
- Search Console filtered for Arabic-script queries
- Spelling variants and dialect terms checked (see next section)
- Each Arabic keyword group mapped to one Arabic URL
- SERP checked by an Arabic speaker for each priority query
Arabic spelling, normalisation and dialect: what to check
Arabic has several common spelling variations that a search engine may or may not treat as equivalent. Apache Lucene's ArabicNormalizer, which Elasticsearch and OpenSearch use for Arabic search, folds hamza forms of alef to bare alef, taa marbuta to haa, alef maksura to yaa, and removes diacritics and tatweel (Apache Lucene). Those are exactly the variants to check in keyword research, because users type them inconsistently.
Diacritics (harakat) are usually omitted in everyday Arabic writing; an academic survey of Arabic diacritisation describes Modern Standard Arabic as typically written without them. Write headings and metadata without diacritics unless the text genuinely needs them, such as Quranic quotations or names that would otherwise be ambiguous.
Dialect matters too. Gulf Arabic speakers may search with colloquial words where formal pages use Modern Standard Arabic (MSA). Older academic studies found that a query written in MSA may not retrieve documents written in colloquial Arabic. Those studies are dated and not UAE-specific, so treat dialect as something to test, not as a rule.
Arabizi, Arabic written in Latin letters with digits for some sounds (for example 3 for ع and 7 for ح), appears in informal chat. Research on Saudi users found it to be mainly a youth and peer register rather than a formal one, and we found no UAE-specific study. Check it once in keyword research, but do not build pages around it.
| Variant type | Illustrative example | What to do |
|---|---|---|
| Hamza on alef | للإيجار and للايجار ('for rent') | Write correctly on the page; check both forms in Search Console and Trends |
| Taa marbuta vs haa | شقة and شقه ('apartment') | Use the correct form; expect users to type both |
| Alef maksura vs yaa | مستشفى and مستشفي ('hospital') | Use the correct form; do not create pages per variant |
| Diacritics | إِيجار versus إيجار | Omit in headings and titles unless needed for meaning |
| Singular vs plural | شقة and شقق ('apartment' and 'apartments') | Check which form the results page favours; category pages often suit plurals |
| MSA vs everyday terms | جهاز تكييف and مكيف ('air conditioner') | Test both; use the term customers use, with the formal one in body text where natural |
| Arabizi | Latin-script Arabic with digits | A niche check only |
Worth noting
These examples illustrate the kinds of variation to check. They are not keyword recommendations, and we make no claim about their search volumes. Validate every term with an Arabic-speaking reviewer and your own data.
How English and Arabic search intent can differ
The answer first: the same topic can carry different intent in each language, so do not assume an Arabic page should mirror its English twin. We found no published UAE study comparing Arabic and English search intent, so the points below are hypotheses to test, not findings.
Hypothesis 1: Arabic queries may skew towards trust and process. Arabic-speaking buyers of high-value services may search for licensing, approvals, family suitability or the steps involved, where English queries focus on price and comparison. Test by reviewing Arabic Search Console queries and enquiry transcripts.
Hypothesis 2: Arabic results pages may show more government and marketplace results. For regulated topics such as visas, licences and health, Arabic results often include official portals. If so, your Arabic page should explain and link to the official process rather than compete with it.
Hypothesis 3: brand queries may switch language. Many users type a brand in Latin script and the rest of the query in Arabic, or the reverse. Check mixed-script queries in Search Console before deciding how to write brand names in Arabic titles.
Our recommendation: write an Arabic brief for each Arabic page, based on Arabic queries and the Arabic results page, then let the Arabic writer decide the structure. Translation of the English page should be one input, not the template.
URL strategy for Arabic and English
The answer first: give each language its own URL. For most UAE businesses, language subdirectories on one domain (example.ae/ar/ and example.ae/en/) are the simplest to run. Use subdomains or ccTLDs only when there is a clear organisational or market reason.
Google 'recommends using different URLs for each language version of a page' rather than switching language with cookies or browser settings, and advises against automatically redirecting users between language versions (Google Search Central). Google also says it determines a page's language from its visible content, not from the lang attribute or the URL, so the URL pattern is for users and site management rather than a language signal.
| Option | Example | Google's listed pros | Google's listed cons | Our view for UAE sites |
|---|---|---|---|---|
| Subdirectory | example.ae/ar/ | Easy to set up; low maintenance (same host) | Single server location; separation of sites harder | Default choice for most bilingual UAE sites |
| Subdomain | ar.example.com | Easy to set up; allows different server locations | Users might not recognise geotargeting from the URL alone | Useful when a separate team or platform runs the Arabic site |
| ccTLD | example.sa | Clear geotargeting; server location irrelevant | Expensive, limited availability; targets a single country | For separate country sites, such as a Saudi store |
| URL parameter | example.com?lang=ar | None listed | Not recommended; segmentation difficult | Avoid |
Pro tip
Arabic-script or transliterated slugs? Arabic slugs read naturally to Arabic users, and Google's URL structure documentation includes an Arabic example and recommends percent-encoding non-ASCII characters in links. The cost is that copied Arabic URLs appear as long percent-encoded strings in emails, spreadsheets and analytics. Short English or transliterated slugs are easier to manage. Either works; pick one convention and do not change it after launch.
hreflang for Arabic and English (ar-AE, en-AE and x-default)
The answer first: every Arabic page should point to its English equivalent and itself, every English page should do the same, and both should name an x-default. Google ignores hreflang annotations that are not reciprocal.
Google's rules. You can declare hreflang with HTML link tags, HTTP headers or an XML sitemap; one method is enough. 'Each language version must list itself as well as all other language versions.' URLs must be fully qualified. Only ISO 639-1 language codes with optional ISO 3166-1 Alpha-2 regions are supported, so ar-AE and en-AE are valid, and AE alone is not. x-default covers users whose language matches no version (Google hreflang documentation).
ar or ar-AE? Use ar-AE when the Arabic content is specific to the UAE: AED prices, UAE delivery, UAE legal pages or emirate-specific services. Use plain ar if the same Arabic page is meant for Arabic speakers everywhere. If you later launch a Saudi version with SAR prices, that becomes ar-SA, and the UAE page stays ar-AE.
Which page is x-default? Usually the English version, or a language-selection page if you have one. Do not point x-default at a page that redirects based on browser language.
The full mechanics of hreflang across many markets are covered in our international ecommerce SEO guide; for a two-language UAE site, the pattern below is enough.
<link rel="alternate" hreflang="ar-AE"
href="https://example.ae/ar/villas/" />
<link rel="alternate" hreflang="en-AE"
href="https://example.ae/en/villas/" />
<link rel="alternate" hreflang="x-default"
href="https://example.ae/en/villas/" />Canonicals and duplicate translations
The answer first: each language version gets a self-referencing canonical. Never canonicalise the Arabic page to the English page; that tells Google the Arabic URL is a duplicate and can keep it out of Arabic results.
Google treats redirects and rel=canonical as strong signals and sitemap inclusion as a weak one, and it chooses canonicals itself. When you use hreflang, Google asks you to specify a canonical in the same language, or the best substitute language if a same-language page does not exist (Google canonicalisation guidance).
Duplicate translations happen in less obvious ways. Common examples are an Arabic URL that falls back to English text because nothing was translated; two Arabic URLs for the same page (for example with and without a trailing slash, or with Arabic and transliterated slugs both live); and Arabic pages whose body is translated but whose navigation, filters and product data are still in English. Google's multilingual guidance notes that translating only boilerplate while keeping the main content in one language can create a poor experience when the same content appears several times in results.
Our recommendation: do not publish an Arabic URL until its main content is in Arabic. If a platform falls back to the default language for untranslated content, as Shopify does, check that untranslated pages are not linked or listed in the Arabic sitemap.
Arabic metadata: titles and descriptions
The answer first: write Arabic title tags and meta descriptions from the Arabic page and its target queries. Do not translate the English metadata, and never leave English metadata on an Arabic page.
Titles. Lead with the primary Arabic term as users write it, followed by the brand. Decide how to write the brand: Latin script, Arabic script, or both. Apply that decision consistently, because inconsistent brand spellings make it harder for search engines and AI systems to connect your pages.
Descriptions. Write a natural Arabic sentence that answers the query and states a concrete next step, such as viewing prices, booking a viewing or speaking to an Arabic-speaking adviser. Keep numbers, prices and phone numbers in the format your Arabic page uses.
Other metadata. Set Open Graph titles, descriptions and og:locale per language so links shared on WhatsApp and social platforms preview in the right language. Use Arabic alt text on Arabic pages and Arabic image file names only if your slug convention already uses Arabic script.
Google's generative AI guidance says reviewing AI-generated content 'also applies to metadata' (Google Search Central). If you draft Arabic metadata with AI, a fluent reviewer should check every line.
- Arabic title and description on every Arabic URL, written from Arabic queries
- No English title or description left on any Arabic page
- Brand spelling convention agreed and applied
- og:locale and Open Graph text set per language
- Alt text written in the page language
Structured data in Arabic
The answer first: structured data on an Arabic page should describe the Arabic page, in Arabic. Translate the visible content first, then generate the schema from it, and set inLanguage where the type supports it.
Google's structured data guidelines say 'Don't mark up content that is not visible to readers of the page' and that structured data 'must be a true representation of the page content' (Google structured data guidelines). English schema on an Arabic page fails that test, because the marked-up text is not what readers see.
Practical rules. Product names, descriptions, FAQ answers, service names and breadcrumbs in the schema should match the Arabic text on the page. URLs in schema should point to Arabic URLs. Organization markup belongs on one page that describes the organisation; keep the name and logo consistent across languages, and use sameAs links to the same official profiles. Prices stay numeric, with priceCurrency set to AED.
Remember that FAQ rich results have been limited to well-known government and health websites since August 2023, so FAQ markup is not a route to extra space in results for most businesses. It can still describe content accurately. For product schema depth, see product structured data for ecommerce.
Internal linking within each language
The answer first: Arabic pages should link mainly to Arabic pages, and English pages to English pages. Cross-language links belong in the language switcher, not scattered through body text.
A common failure is an Arabic page whose navigation, breadcrumbs, related products and footer all link to English URLs because those components were never localised. Search engines then see a thin Arabic island, and users are thrown back into English after one click.
Our recommendation: localise navigation, breadcrumbs, related-content modules and footers as components, so every link they output follows the current language. Make the language switcher point to the equivalent page, not the home page. Build Arabic hub pages that link to Arabic service, category or product pages, mirroring the structure you would build in English. Our ecommerce internal linking guide covers the patterns in more depth.
Right-to-left basics that affect SEO and user experience
Arabic pages must render right to left. The W3C advises adding dir="rtl" to the html element 'any time the overall document direction is right-to-left' and never using CSS to set the base direction (W3C). It also advises always declaring the page language with a lang attribute on the html element.
Google does not use the lang attribute to detect language, but browsers, screen readers, translation tools and font selection do. A page with lang="en" and Arabic content is mispronounced by screen readers and may get the wrong fonts. Broken RTL layouts, mirrored logos, scrambled phone numbers and English error messages hurt engagement and trust, which is ultimately what search performance depends on.
This guide does not repeat the build details. Our companion article on multilingual website development in the UAE covers RTL CSS, typography, forms, numbers and a QA checklist, and our website accessibility guide covers the accessibility side.
Machine translation: where the real risk is
The answer first: machine translation is a drafting tool, not a publishing process. Use it to speed up a fluent translator, not to replace one.
Google's spam policies list, under scaled content abuse, 'Scraping feeds, search results, or other content to generate many pages (including through automated transformations like synonymizing, translating, or other obfuscation techniques), where little value is provided to users' (Google spam policies). Search Engine Journal has reported Google staff saying that machine translation reviewed by a human is acceptable, and that review by a native speaker is advisable. The policy text itself focuses on value to users rather than on the method.
The commercial risk is often larger than the policy risk. Unreviewed Arabic can choose formal terms customers never search for, mistranslate product attributes, or produce text that reads as foreign. Missing diacritics make Arabic more ambiguous for machines, so automated output needs a human check for meaning, not only grammar.
Our recommendation: keep a glossary of approved Arabic terms for your products and services, have a fluent reviewer sign off every page and every metadata field, and record who approved what. Translate fewer pages well rather than every page poorly.
Arabic in AI Overviews, AI Mode and AI assistants
UAE and Arabic facts. Google added Arabic to AI Overviews on 20 May 2025, as part of an expansion to more than 40 languages (Google). AI Mode began rolling out in English across MENA, including the UAE, in August 2025 (Gulf News), and Google's MENA blog announced AI Mode in Arabic on 8 October 2025, rolling out gradually (Google MENA). StatCounter puts Google's share of UAE search referrals at 93.47% in September 2026 (StatCounter).
Google says there are 'no additional requirements to appear in AI Overviews or AI Mode' and that you do not need special machine-readable files or markup; a page needs to be indexed and eligible to show with a snippet (Google AI features documentation). For Arabic content, that means the same fundamentals: indexable Arabic pages, clear headings, direct answers in Arabic, accurate schema that matches the visible text, and facts stated plainly.
Our recommendation: write Arabic pages that answer the questions Arabic speakers actually ask, in the first paragraph under each heading. Keep important facts such as prices, service areas, licensing and hours in Arabic text, not only in images or PDFs. AI search treats your Arabic and English pages as separate sources, so the Arabic page needs to stand on its own. For the wider picture, see generative engine optimisation for UAE businesses and how to make a UAE website AI-search ready.
Measuring Arabic and English separately
The answer first: report each language as its own channel. Aggregated numbers hide whether Arabic pages are earning their cost.
Search Console. With language subdirectories, filter the Performance report by page path containing /ar/ and compare queries, impressions, clicks and positions with /en/. Filter queries by Arabic script to see Arabic searches landing on English pages, which signals a missing Arabic page. Google includes AI Overviews and AI Mode traffic in the overall Performance report under the Web search type; there is no separate AI report.
Analytics. Record page language as a custom dimension or content group from the html lang attribute or URL path. The browser-language setting is a different thing: many Arabic speakers use English-language devices. Then report enquiries, WhatsApp clicks, bookings and sales by page language.
Business outcomes. Tag CRM leads with the language of the page or form they came from, and the language they asked to be served in. That is the evidence you need to move a section from Tier 3 to Tier 2, or the reverse.
| Metric | Where | What it tells you |
|---|---|---|
| Impressions and clicks for /ar/ pages | Search Console, page filter | Whether Arabic pages are visible and chosen |
| Arabic-script queries landing on English pages | Search Console, query filter | Gaps where an Arabic page is missing |
| Engagement and conversions by page language | Analytics custom dimension or content group | Whether Arabic visitors complete actions |
| Leads by language | CRM field | Commercial value of Arabic content |
| Indexing status of Arabic URLs | Search Console page indexing report | Canonical or hreflang problems |
Sector examples (hypothetical)
The examples below are hypothetical and illustrate how the three tiers apply. They are not client work and contain no performance data.
| Sector | Hypothetical business | Suggested tier | Arabic SEO focus |
|---|---|---|---|
| Ecommerce | A UAE-registered home appliances store | Tier 1 for products and checkout | Arabic product names and attributes customers search for; Arabic invoices and product information as required; Arabic site search. See UAE checkout optimisation |
| Real estate | A Dubai brokerage listing rentals and off-plan units | Tier 1 for listings and area guides | Rent and sale terms with spelling variants; community names in Arabic and Latin script; Arabic area guides. See real estate website development |
| Hospitality | An Abu Dhabi hotel with GCC family guests | Tier 2 | Arabic room, family, dining and booking pages; Arabic answers to policy questions |
| Professional services | A Dubai accounting firm serving SMEs | Tier 2 or 3 | Arabic pages for core services and regulatory topics, linking to official sources; Arabic-speaking contact path |
| Technology | A Dubai SaaS company selling to semi-government entities | Tier 1 for product and capability pages; Tier 3 for documentation | Arabic product pages, procurement and security information; consistent product naming in both scripts |
Common Arabic SEO mistakes
Translating English keywords. The dictionary term is often not the search term.
Canonicalising Arabic pages to English. This removes the Arabic pages from contention.
One-way hreflang. If the English page does not point back, Google ignores the annotation.
Switching language with cookies on one URL. Google recommends separate URLs per language.
Auto-redirecting by browser language. Users and crawlers may never reach the other version.
English metadata or schema on Arabic pages. Titles, descriptions and structured data must match the Arabic page.
Bulk machine translation without review. It risks the scaled content abuse policy and loses customers anyway.
Arabic pages with English navigation and links. Users and crawlers are pulled back into English.
Arabic in images only. Text inside banners is invisible to search and hard to update.
No Arabic-speaking follow-up. Ranking for Arabic queries and replying in English wastes the click.
Arabic SEO checklist for UAE websites
Use this checklist before launching or auditing Arabic pages. It covers the SEO layer; the build-level QA checklist is in our multilingual development guide. If you are choosing a partner for the work, our guides to choosing a web development company in Dubai and web development in Abu Dhabi may help.
- Tier decided per page section (full parity, key pages or Arabic summaries)
- Arabic keyword research seeded in Arabic and validated with Search Console and Trends
- Spelling variants, diacritics and dialect terms checked by an Arabic speaker
- One URL per language, using subdirectories unless there is a reason not to
- Slug convention chosen (Arabic script or transliterated) and documented
- Reciprocal hreflang with ar-AE (or ar), en-AE (or en) and x-default
- Self-referencing canonical on every language version
- No automatic redirects between language versions
- html lang="ar" and dir="rtl" on Arabic pages
- Arabic titles, descriptions, Open Graph text and alt text
- Structured data in Arabic, matching visible content, with Arabic URLs
- Navigation, breadcrumbs and related links stay in the current language
- Language switcher goes to the equivalent page
- Every Arabic page reviewed by a fluent reviewer, with sign-off recorded
- Arabic product information and invoices in place if you are a UAE-registered ecommerce business
- Arabic and English reported separately in Search Console, analytics and CRM
Sources
Google: Managing multi-regional and multilingual sites; Tell Google about localized versions of your page; URL structure best practices; Consolidate duplicate URLs; Spam policies; Using generative AI content; Structured data guidelines; FAQ and HowTo changes; AI features and your website; AI Overviews expansion, May 2025; AI Mode in Arabic, October 2025.
UAE: UAE Constitution, Constitute Project; u.ae consumer protection; Khaleej Times, draft Arabic Language Law; Khaleej Times, 2011 population data; Gulf News, AI Mode in MENA.
Data and standards: StatCounter UAE search engine share; W3Techs content languages; W3C, structural markup and right-to-left text; W3C, language declarations; Apache Lucene ArabicNormalizer; Search Engine Journal on machine translation review; Alghamdi and Petraki (2018) on Arabizi.
This guide is not legal advice. Confirm Arabic-language obligations with the relevant authority or a UAE-qualified adviser.
Conclusion
Arabic SEO in the UAE is a business decision before it is a technical one. Decide which audiences need Arabic and at what depth, research Arabic queries in Arabic, give each language its own canonical URL with reciprocal hreflang, write metadata and schema from the Arabic page, and measure Arabic on its own. A smaller set of well-researched, fluently reviewed Arabic pages will usually outperform a full machine-translated copy of the English site, in search, in AI answers and with customers.
Planning Arabic pages for a UAE website?
ZSpace Labs is an India-based, remote-first technology studio that works with UAE and global businesses on bilingual websites, Shopify stores and right-to-left UX. If you are deciding how much of your site to publish in Arabic, we are happy to look at your structure and data and suggest a practical scope.
Common questions.
Arabic SEO is the work of making Arabic-language pages discoverable and useful for people who search in Arabic. It covers keyword research done in Arabic, spelling and dialect variants, right-to-left page quality, Arabic metadata and structured data, hreflang between Arabic and English versions, and measurement per language. Translating English pages and adding Arabic keywords is not Arabic SEO; it usually produces pages that read poorly and match the wrong queries.