Bilingual SEO for Gulf Stores: Arabic + English Done Right

Gulf shoppers search in two languages: a Saudi buyer types عطر عود in the morning and "oud perfume 100ml" at night. An Emirati might compare prices in English, then read reviews in Arabic.

A bilingual store can win both searches, while one that only translates its English pages usually wins neither.

Bilingual SEO fixes that. You give each language its own URL, tell Google how the versions connect and research each language from scratch.

Here's the setup for Saudi Arabia and the UAE, with Shopify, Salla and Zid specifics. It's part of our GCC localization guides.

What is bilingual SEO?

Bilingual SEO means optimising one store to rank in two languages at once, which in the Gulf means Arabic and English.

Google treats Arabic and English searches as separate markets, with separate results pages. Your Arabic pages don't borrow rankings from your English ones, so each version competes on its own.

That's good news:

• Arabic results are thin. So little of the web is in Arabic that many Arabic shopping searches have weak competition.
• English results are crowded. Global brands and marketplaces fight hard for English terms in Dubai and Riyadh.
• You need both. Saudi shoppers lead with Arabic but type brands and models in English, while UAE shoppers lean English.

There's one more reason to act now. When good Arabic pages are scarce, Google shows machine-translated copies of English pages on a translate.goog address. A real Arabic page, linked with hreflang, takes that traffic back.

How should you split the effort? Start with about 70% Arabic for Saudi Arabia and about 60% English for the UAE, then let Search Console data adjust it.

Step 1: Choose your URL structure

Every language needs its own crawlable URL. Google works out a page's language from its visible text, not from tags, so each URL should hold one language.

You have five options:

Why is the last one so risky? Googlebot crawls mostly from the US, without cookies or a language preference, so a store that picks the language by IP or cookie shows Google only one.

Language folders or language-and-country folders?

Plain /ar/ and /en/ work when price, currency and delivery are the same everywhere you sell. For most Gulf stores they aren't: Saudi prices are in SAR with 15% VAT, and UAE prices in AED with 5% VAT.

So split into /ar-sa/, /en-sa/, /ar-ae/ and /en-ae/. Your platform builds all four from one product record.

Step 2: Set up hreflang (ar-SA, ar-AE, en-AE, x-default)

Hreflang tags tell Google which version to show to which shopper. They don't boost rankings, but they make sure the Saudi Arabic page appears in Saudi Arabic results, not the UAE English one.

Here's a full set for one product, sold in both countries:

Each row becomes one link rel="alternate" tag in the page head. All five URLs carry the same six tags, the x-default page included.

Google picks the most specific match. An Arabic searcher in Kuwait has no ar-KW page, so Google falls back to ar. An English speaker in Germany matches nothing, so they get x-default.

A few rules make or break it:

• Reciprocal sets. Every version lists the full set, including itself. If the Arabic page points to the English one but not the other way round, Google ignores the pair.
• Absolute URLs. Always use full https addresses.
• Live, canonical pages only. Point hreflang at pages that return 200 and canonicalise to themselves, never at redirects.
• One method. Use page-head tags, HTTP headers or the XML sitemap. Doing more than one adds nothing.

Need every edge case? Our hreflang guide for GCC stores covers sitemaps, headers and auditing.

Step 3: Translated slugs or English slugs?

The slug is the last part of the URL, like oud-perfume. On Arabic pages it can stay English, be written in Arabic or be transliterated, and Google accepts all three:

For most stores, English slugs on Arabic pages are the right call. A slug's keyword signal is small. Shoppers click because the title says شنطة نسائية جلد, the exact words they typed. Arabic slugs suit an Arabic-only store whose shoppers rarely share links.

Whatever you pick, decide once, because changing slugs later means a 301 redirect for every page, in every language.

Step 4: Do keyword research twice

Don't translate your English keyword list. The words people type differ between markets, so research Arabic terms natively for each country.

We pulled 12 months of Google Trends data for common product terms. Scores show relative interest, where 100 is the top term in that comparison, so compare words within one country only.

The same Arabic product can need a different title in Riyadh and Dubai. That's the strongest argument for separate /ar-sa/ and /ar-ae/ pages: جوال on one, هاتف on the other. UAE shoppers also type brand and model terms in Latin script, even when they browse in Arabic.

Worked example: a bilingual keyword map

Say you sell oud perfume and phone cases in both countries. Your keyword map has one row per page and locale:

The perfume terms match in both countries, so those pages differ mainly in price, VAT and delivery, while the phone pages differ in the words themselves.

Fill this map before you write a single Arabic title. Then pull volumes in Keyword Planner or Ahrefs, with the location set to Saudi Arabia, then the UAE.

The full method, with hamza spellings, Arabizi and marketplace mining, is in our guide to Arabic keyword research.

Step 5: Avoid duplicate content between versions

Translations are not duplicate content. Google treats an Arabic page and its English twin as alternates, not copies.

The risk is same-language regional pages, like /ar-sa/ and /ar-ae/. If they look nearly identical, Google may index one and ignore the other.

So make each regional twin genuinely local:

• Currency and VAT. SAR with 15% VAT on Saudi pages, AED with 5% VAT on UAE pages.
• Delivery promise. "Riyadh and Jeddah in 1–2 days" on one, Dubai and Abu Dhabi on the other.
• Payment options. mada on Saudi pages, local cards and wallets on UAE pages, plus your BNPL providers.

Then keep the technical signals clean:

• Self-canonical every version. Never canonicalise /ar-ae/ to /ar-sa/, which tells Google to drop the UAE page and breaks the hreflang link with it.
• No half-translated pages. An Arabic page with English specs and an English size guide reads as a weak copy. Translate everything that helps someone buy, down to the footer.
• Tame filters. Sort and filter URLs multiply fast across four locales. Keep them out of the index.

Step 6: Link internally within each language

Internal links tell Google which pages matter, and in which language. Treat each language as a complete, self-contained site:

• Stay in the language. Arabic pages link to Arabic pages, because a menu that sends Arabic shoppers to /en-sa/ leaks both rankings and trust.
• Switch to the twin, not the homepage. The language switcher on an Arabic product page should open the same product in English.
• Use Arabic anchor text and breadcrumbs. Breadcrumbs show in search results, and Arabic anchors tell Google what the target page is about.

For example, an Arabic blog post about Eid gifts should link to عطور العيد and هدايا رجالية, with those exact Arabic words, on /ar-sa/ pages.

Step 7: Set up Google Search Console per locale

A single Search Console report mixes Arabic and English data, so split it to see how each version performs.

1

Verify a Domain property

It covers every folder and subdomain at once, so it's your total view of the store.

2

Add a URL-prefix property per locale

Add store.com/ar-sa/, /en-sa/, /ar-ae/ and /en-ae/ as separate properties, each showing only that version's queries, pages and errors.

3

Submit one sitemap per language

Submit each language's sitemap in its matching property, so indexing problems show up per language.

4

Filter by country and page

In the Performance report, filter by country and by page path (/ar-sa/) to compare clicks and position for each locale.

5

Check translated pages

Look under Search appearance for Translated pages. Any searches listed there need a real Arabic page.

Shopify, Salla and Zid: what each platform does for you

Each platform handles part of the work. Here's what's automatic and what's still your job:

Still choosing a platform? Compare them in Shopify vs Salla vs Zid.

Building on Shopify? Themes, checkout and fonts are in our Arabic Shopify store guide.

Bilingual SEO checklist

Run through this before you publish Arabic, then every quarter:

Notes for UAE stores

• English-first is fine, Arabic-second isn't optional. Emiratis and Arab expats still search in Arabic. Our guide to Arabic vs English in the UAE covers when each should lead.
• Arabic product information. UAE-registered online businesses must give product information and invoices in Arabic, so the Arabic version pulls double duty.

Notes for Saudi stores

• Make Arabic the default. Saudi traffic should land on /ar-sa/, with English one tap away. Keep en-SA live for brand, model and B2B searches.
• Hire for the dialect. An Egyptian or Levantine translator will write موبايل where Saudis search جوال. The full playbook is in ecommerce SEO in Saudi Arabia.

Notes for stores selling across the GCC

• Start with two markets. Get Saudi Arabia and the UAE right first, while Kuwait, Qatar, Bahrain and Oman can use the ar fallback until they get their own prices.
• Check terms per country. Kuwaiti Arabic is closer to Emirati than Saudi: هاتف, not جوال, leads phone searches in Kuwait.
• Get help with the Arabic. An Arabic translation agency can review titles and metadata for each market.