Arabic SEO in the UAE: 2026 Technical Guide

Arabic SEO is the practice of making a website rank in Arabic-language search results by treating Arabic as a source language rather than a translation target. It covers Arabic keyword research, orthographic and dialect variation, hreflang and URL architecture for bilingual sites, right-to-left rendering, Arabic structured data, and measurement in Google Search Console.

A bilingual page needs Arabic content that matches its audience and search intent, as well as a URL Google can crawl. A literal translation may be grammatically correct but still miss local phrasing or context. Check actual query and page evidence instead of assuming that a translated keyword is the right target.

This guide is the technical version. It covers what actually changes when you optimise for Arabic, with the markup, the character sets, and the Search Console syntax included rather than described. It is written from how NxFold runs its own bilingual site — English at the root, Arabic under /ar, region-qualified en-AE / ar-AE / x-default hreflang, one canonical source of truth — so the examples are implementations we maintain, not diagrams.

What actually changes between English SEO and Arabic SEO#

Everything below expands one of those rows.

Arabic search behaviour in the UAE: written patterns to check#

Arabic searches can use different registers or writing systems. In UAE research, compare Modern Standard Arabic (MSA), Gulf phrasing and Arabizi where evidence suggests they are used. Wording, intent and current search results may differ; validate each candidate with Search Console and live results instead of assuming a fixed pattern.

Modern Standard Arabic (MSA) is a formal written register used in news, government and documentation. It can be a useful starting point for informational topics; check how people phrase relevant searches before choosing the register for a page.

Gulf phrasing (Khaleeji) may appear in conversational and local queries. Whether it matches commercial intent depends on the query and audience.

Arabizi writes Arabic with Latin characters and may use numerals for sounds without a direct Latin equivalent. Usage varies; check actual search queries in the category before investing in this form.

Some mappings are commonly used, but Arabizi has no single fixed spelling standard. Examples to check include:

Strings such as "7abibi", "3arabi", and "5edma" can be checked as candidate queries. Do not assume Arabizi is only informal or early-stage; inspect its search results, reported queries and business context before assigning intent.

Orthographic variants: the same word, spelled several ways#

Arabic queries can vary in spelling and character form. Check which variants appear for the words and market you are researching.

Search systems may treat some variants as related, but do not rely on that for every query. Use a consistent spelling in headings and body copy, then check real Search Console queries for useful variants. Repeating every spelling can make a paragraph harder to read.

Some queries mix scripts, for example "سيو Dubai", "SEO بالعربي", or "تصميم موقع ecommerce". Check the wording of the brand, technology or place name in the target audience’s actual queries; use Arabic or Latin script consistently with that evidence.

Arabic keyword research that survives a real SERP#

Third-party keyword-volume estimates can be sparse or inconsistent for a specific language, spelling or market. Treat them as estimates, not proof of demand or its absence; check search results and Search Console data where available.

A method that holds up:

1. Use an English page as a research input. If its Search Console rows are useful, review queries for the equivalent page and treat them as hypotheses. Validate Arabic wording and intent independently rather than transferring the English intent automatically.
2. Generate the register set. For each seed, write the MSA form, the Gulf form, and the Arabizi form if one exists in common use. Do this with a native speaker or a strong Arabic model — not a dictionary.
3. Review current search results alongside the tool. Search each candidate with the intended location and inspect the result types. Commercial pages can be evidence of commercial intent; informational results may indicate a different need. Confirm against the audience and page purpose.
4. Review autocomplete and related searches in Arabic. Treat suggestions as research prompts, not as measured search volume or proof of demand.
5. Review your Search Console data for Arabic queries the property already receives. Use the filter in the measurement section below, then check which URLs and markets those rows describe.
6. Cluster by intent, then review register. If two phrasings serve the same audience and need, one useful page may cover both. Create separate pages only when research shows a distinct intent or audience and each page can provide distinct value.

The output is a keyword set where each entry has an intent, a register, and a SERP observation attached. That is a defensible brief. A spreadsheet of translated English keywords is not.

URL architecture for bilingual UAE sites#

Google recommends distinct URLs for language versions. Subfolders, subdomains and separate domains are all options; choose based on hosting, publishing, analytics and market operations. No URL structure guarantees better rankings.

A subfolder is one operational option. NxFold uses English at the root and Arabic under /ar/; this is an implementation choice, not a ranking rule.

Should Arabic slugs be in Arabic script?#

Non-ASCII characters in a URL are percent-encoded on the wire (RFC 3986), so /ar/تصميم-مواقع transmits as /ar/%D8%AA%D8%B5%D9%85%D9%8A%D9%85-%D9%85%D9%88%D8%A7%D9%82%D8%B9. Browsers and Google display the decoded Arabic; anything that logs or shares the raw URL shows the encoded form.

Google supports localized words in URLs when properly encoded. Choose a readable, stable convention and check links, redirects, canonicals, sitemaps, analytics and hreflang. Arabic-script and transliterated slugs are both options; do not assume either has a ranking advantage.

Whichever you choose, choose once. Mixed slug strategies across a site are a migration you will pay for later.

Hreflang, done properly#

Use one URL per language and list every available version, including itself. The alternate links below are the same on both pages; set each page’s canonical separately. The English page points to the English URL, and the Arabic page to the Arabic URL. See Google’s multilingual site guidance and canonical guidance.

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

Four rules that decide whether it works:

1. Self-reference. Each page lists itself among its own alternates. The English page includes the en-AE tag pointing at itself. Omitting this is the most common failure.
2. Return tags. If A points to B, B must point back to A. Unidirectional hreflang is ignored.
3. Canonical must agree. A page's canonical points to itself, never to the other locale. A canonical that points to a different language can send conflicting signals about which URL should represent the page. Use a canonical for the preferred URL in the same language where one exists, and use reciprocal hreflang annotations to connect language versions, following Google’s multilingual site guidance and canonicalization guidance. A canonical is a signal, not a guarantee of indexing; check Google’s selected canonical in URL Inspection.
4. Absolute URLs, consistent host. Match the protocol, the www choice, and the trailing-slash convention exactly. https://www.example.com/ar/x and https://example.com/ar/x/ are different URLs to a validator.

ar or ar-AE?#

Use ar-AE when you are targeting UAE Arabic speakers specifically and your content reflects UAE context — currency, regulation, delivery, local terminology. Use bare ar when the page serves Arabic speakers across markets equally. You may also ship both, with ar as the fallback and ar-AE for the region-specific page, but only if the pages genuinely differ. Two hreflang entries pointing at one URL is noise.

We use region-qualified en-AE / ar-AE with x-default resolving to English, because the site's commercial context is explicitly UAE.

The failures worth auditing for#

• Hreflang on a page that is noindex — the annotation is discarded
• Hreflang in the sitemap and in the <head> disagreeing
• A locale in the set that returns a 404 or redirects (very common when a "planned" market page does not exist yet)
• Language codes invented rather than BCP 47 (ar-UAE is not valid; ar-AE is)
• Hreflang generated per page by hand, drifting over time

The structural fix is to derive alternates from one function rather than authoring them per page. On nxfold.com every page's alternates come from a single builder fed by one siteUrl constant, which is also the origin used for the sitemap — so a canonical can never disagree with its own sitemap entry. Making the correct thing automatic is worth more than any audit.

RTL is not dir="rtl"#

Setting the attribute is the first ten percent.

<html lang="ar" dir="rtl">

The rest:

Use CSS logical properties. margin-inline-start instead of margin-left, padding-inline-end, border-inline-start, inset-inline-start. These flip automatically with direction. A stylesheet built on physical properties requires a parallel RTL stylesheet, which then drifts.

Handle bidirectional text. Arabic paragraphs containing Latin strings — brand names, URLs, version numbers, "Next.js" — are bidirectional. The Unicode bidi algorithm mostly gets this right, but punctuation adjacent to a Latin run frequently lands on the wrong side. Where it matters, isolate the run with a bdi element or unicode-bidi: isolate.

Mirror the right things, not everything. Directional icons (arrows, chevrons, progress indicators) mirror. Logos, media playback controls, and clock faces do not. Blanket transform: scaleX(-1) on an icon set produces backwards logos.

Test Arabic typography as a first-class case. Arabic glyphs need more vertical space; line-height tuned for Latin clips descenders and diacritics. Arabic text also has no uppercase, so any design leaning on text-transform: uppercase for hierarchy loses that hierarchy entirely in Arabic and needs weight or size to carry it instead.

Watch layout shift. Arabic web fonts are large. A font swap that reflows an RTL layout is a CLS problem, and Google's threshold is CLS below 0.1 (alongside LCP under 2.5s and INP under 200ms). Subset your Arabic font, serve WOFF2, and use font-display: swap deliberately. Our Core Web Vitals guide for UAE businesses covers the measurement side.

For the design and UX half of this — layout, navigation, form patterns — see our Arabic website design and RTL guide.

Structured data in Arabic#

Emit locale-aware JSON-LD rather than one block reused across both languages.

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "@id": "https://www.example.com/ar/blog/post#article",
  "inLanguage": "ar-AE",
  "headline": "عنوان المقال بالعربية",
  "description": "وصف الصفحة بالعربية",
  "author": { "@type": "Organization", "name": "NxFold Technologies LLC" },
  "datePublished": "2026-08-02",
  "dateModified": "2026-08-02"
}

Three things to get right:

• inLanguage on every locale variant. It is the cheapest correctness signal available and it is almost universally omitted.
• Distinct @id per locale. Reusing one @id across two URLs merges two entities into one and confuses the graph.
• Localise the values, not just the wrapper. name, description, address, and areaServed should be in Arabic on the Arabic page. An Arabic page carrying an English LocalBusiness name is a mismatch signal.

Google says FAQ rich results are generally limited to well-known authoritative government and health sites; most businesses should not expect that search display. If you use FAQ markup, keep it accurate and aligned with visible content. Do not claim that it guarantees an AI-search citation or rich result.

Measuring Arabic performance in Search Console#

Separate page URLs from query language when reviewing Search Console performance. The two filters answer different questions.

This isolates Arabic URL paths, but query rows can still include Arabic, English or mixed-script searches.

Isolate Arabic-script queries. Search Console query filters support RE2 regular expressions. Select Query → Custom (regex) → Matches regex:

[\x{0600}-\x{06FF}]

This pattern matches characters in the basic Arabic Unicode block, not every Arabic-script character. Search Console may also omit queries for privacy or storage reasons, so treat the visible rows as a partial report.

Validate the rendered HTML or sitemap annotations: each language URL should identify its available alternates, including itself, and the alternate pages should link back. In Search Console, use URL Inspection to review the indexed URL, crawl status and Google-selected canonical; use the Page indexing report to investigate coverage across URLs. These reports describe Google’s observed state and do not guarantee that a valid page will be indexed.

Two habits that pay off: track Arabic and English positions separately (a page can be position 4 in English and 40 in Arabic — averaged together, it looks like 22 and tells you nothing), and check Arabic queries monthly for intents you have never targeted. That report is free keyword research from your own users.

Content quality: what machine translation costs you#

Translation tools can help prepare a draft, but translation alone does not validate local intent, terminology or accuracy.

Register. Translation output tends to land in a stiff formal register that reads as foreign to Gulf readers, or drifts inconsistently between formal and colloquial within one page.

Term choice. The translated term is frequently not the searched term. Translation optimises for accuracy; SEO needs the word your buyer actually types. These diverge constantly — and a page can be a flawless translation while targeting a phrase nobody searches.

Local specificity. The English page cites examples, regulations, and payment methods that make sense to its audience. Faithfully translated, they make an Arabic page about a market it is not addressing. Native Arabic content substitutes locally relevant equivalents instead of translating irrelevant ones.

The workable process is not "translate" and not "write twice from scratch." It is: one shared strategy and keyword map, then independent authoring per language, with each locale free to differ in structure, examples, length, and FAQ set. Our own bilingual publishing enforces this at the system level — a post cannot be published unless both language versions are genuinely complete, which makes a stub Arabic version impossible to ship by accident.

Arabic and AI search#

Search features that use AI can change. Clear, accurate, crawlable content helps readers, but no word count, table format or structured-data type guarantees citation in a generated answer.

• Lead with the entity. Arabic prose conventions favour long introductory throat-clearing; extractable content does not.
• Put a self-contained 40–60 word definition near the top, in Arabic, that reads correctly with zero surrounding context.
• Use question headings phrased the way Arabic users actually ask.
• Ship comparison tables. Tables survive extraction; prose paragraphs get paraphrased.
• Name entities precisely and consistently — including keeping technology and brand names in Latin script where that is the convention.

A note on the statistics in this market#

When using market, search-volume or conversion figures, state the source, date, geography and method. If a current primary source is unavailable, omit the number rather than presenting an estimate as a measured result.

We have not repeated any of them here. Where you need a number for a business case, pull it yourself from a primary source — DataReportal, StatCounter, W3Techs, or the UAE's own statistics authorities — and cite the date. In a market where nobody sources anything, being the page that does is a durable advantage, with AI search systems as well as with buyers.

Implementation checklist#

Architecture

• Arabic on a subfolder (/ar/), not a subdomain, unless there is a real infrastructure reason
• Slug strategy chosen once and applied site-wide
• Every English page has an Arabic counterpart, or is deliberately English-only

Hreflang and canonicals

• Self-referencing hreflang on every page
• Reciprocal return tags verified
• x-default used only when there is a suitable default page
• Canonical points to the preferred URL in the same language where available
• Language alternates are reciprocal and point to the intended URLs
• Rendered HTML or sitemap annotations match the published routes
• URL Inspection checked for the indexed URL, crawl status and Google-selected canonical
• Page indexing report reviewed for broader coverage issues

Rendering

• lang="ar" dir="rtl" on the Arabic document
• CSS logical properties throughout
• Bidi isolation on mixed-script runs
• Arabic font subset, WOFF2, CLS under 0.1
• Icon mirroring audited, not blanket-applied

Content

• Keywords researched natively, validated against live SERPs
• Register chosen per page type (MSA for evergreen, dialect where conversational)
• Arabic authored, not translated
• Titles and descriptions checked for rendered width, not character count
• 100% image ALT coverage in Arabic

Structured data and measurement

• inLanguage on every locale variant
• Distinct @id per locale
• No fabricated review or rating markup
• Search Console /ar/ page filter saved
• Arabic-script query regex filter saved
• EN and AR positions tracked separately

Frequently asked questions#

Is Arabic SEO just English SEO with translated keywords?

No. Translation converts meaning between languages; SEO targets the phrasing a specific audience types. The two diverge constantly — a perfectly accurate Arabic translation of an English keyword is frequently not the term Arabic users search. Arabic SEO requires native keyword research, its own intent mapping, and its own content, sharing only the strategy with the English version.

Should I use Modern Standard Arabic or Gulf dialect?

Choose the register from the audience, query wording and page purpose. MSA is one option for formal informational topics; Gulf phrasing may fit some local or conversational queries. Check actual query and result evidence rather than assuming one register will perform better.

Does Google Translate output hurt Arabic rankings?

Machine translation can help create a first draft, but review it with a fluent editor for intent, register, terminology and local examples. A literal translation may not match the wording people use in the target market; check query evidence and revise before publication.

Do Arabic keywords really have lower search volume?

Reported volume can vary by tool, language, spelling and market. Treat it as an estimate, compare relevant query variants, and review current results and Search Console data where available. Search-result types can help interpret intent, but they do not establish the size of demand on their own.

Should my Arabic URLs be in Arabic script?

Both Arabic-script and ASCII slugs can be used. Non-ASCII characters are percent-encoded in URL transmission; display can differ across browsers and tools, so test the systems that publish, share and measure the URL. Choose a consistent convention based on reader clarity and operational needs; do not assume a slug format will improve rankings.

What multilingual technical issue should I check on Arabic pages?

A canonical pointing to another language can be a conflicting signal, but it does not by itself guarantee that Google will exclude the Arabic URL. When language pages have distinct content, use the appropriate same-language canonical, connect versions with reciprocal hreflang and check Google’s selected canonical in URL Inspection.

Do I need ar or ar-AE in hreflang?

Use ar-AE when the content is UAE-specific — local regulation, currency, delivery, terminology. Use bare ar when it serves Arabic speakers across markets equally. Both are valid BCP 47; ar-UAE is not.

How do I see which Arabic queries I already rank for?

In Search Console, open Performance, add a Query filter set to Custom (regex) → Matches regex, and enter [\x{0600}-\x{06FF}]. That returns every query containing Arabic characters. Combine it with a Pages filter for /ar/ to separate Arabic-page performance from English.

Where this leaves you#

Arabic SEO uses the same core search principles as English SEO, with language-specific research, localization and technical checks. Prioritize the issues your routes, rendered pages and Search Console data actually show: language alternates, canonicals, RTL behavior, structured data and separate locale reporting.

Audit the actual routes, rendered language annotations, content and Search Console evidence first. Findings and timing depend on the scope; implementation does not guarantee indexing or ranking changes.

If you want this checklist applied to your site, our SEO and performance service covers bilingual technical SEO, Arabic keyword strategy and native Arabic content. The review should be scoped to your routes, rendered annotations and Search Console property; the timing and findings depend on that evidence.

Related reading: How to choose an SEO agency in Dubai · SEO pricing in Dubai · Web development services