Arabic SEO for GCC Websites: Why "ar" Alone Isn't Enough

One Arabic page tagged "ar" can't serve the UAE and Saudi Arabia. Learn GCC hreflang setup, Arabic keyword research by dialect, RTL technical SEO and AI search tips.

Most GCC websites that "do Arabic SEO" have one Arabic version, tag it hreflang="ar", and assume the whole region is covered. It isn't. A buyer in Riyadh and a buyer in Dubai both read Arabic, but they search with different words, pay in different currencies, trust different signals and often land on different competitors in the results.

The ar tag tells Google a page is in Arabic. It says nothing about which market it serves. On a regional site, that gap shows up as the wrong country version ranking, Saudi pages competing with UAE pages for the same queries, and Arabic content that is technically indexed but never converts.

This article covers how to build Arabic SEO for the GCC properly: market-level hreflang, Arabic keyword research by dialect, localization that goes beyond translation, the technical layer of right-to-left sites, and how Arabic pages get picked up by AI search.

Why One Arabic Version Fails Across the GCC #

Arabic is one written language but not one search market. Formal Modern Standard Arabic (MSA) is what most websites publish. Searchers type something closer to how they speak, and Gulf usage differs from Levantine and Egyptian Arabic, and even between Saudi Arabia and the UAE.

Four things change from one GCC market to the next:

The result is predictable. When one Arabic page serves every country, Google has to guess which market it belongs to. It usually picks the stronger domain or the page with more links, not the one that fits the searcher. A Saudi user sees AED prices, a UAE phone number and a delivery promise that doesn't apply, and leaves.

There is also the competition problem. Arabic search results are often dominated by Egyptian and Levantine publishers because they produce the most Arabic content. A generic MSA page competes with all of them. A page clearly built for ar-SA or ar-AE competes in a much smaller, more relevant set.

Setting Up Hreflang for GCC Markets #

Hreflang values use an ISO 639-1 language code, optionally followed by an ISO 3166-1 alpha-2 country code. For the GCC, that means ar-AE, ar-SA, ar-KW, ar-QA, ar-OM and ar-BH, plus the English equivalents such as en-AE and en-SA. A country code on its own is never valid.

1. Decide the structure first #

Pick one architecture and keep it consistent:

• Subfolders on one domain: example.com/ae-ar/, example.com/sa-ar/. Easiest to maintain, and all versions share one domain's authority.
• ccTLDs: example.ae and example.sa (or example.com/sa/). Strongest local signal, but each domain builds authority separately and hreflang must work across domains.

Whichever you choose, every market should have its own URLs. Showing different prices or phone numbers on the same URL based on IP is invisible to Googlebot, which crawls mostly from the US.

2. Build the full cluster #

A typical regional business with English and Arabic for the UAE and Saudi Arabia has four versions. Each page in the cluster lists all four, plus itself:

3. Use x-default deliberately #

x-default is the page for everyone who matches nothing else. For most GCC businesses that is either the main English page or a country/language selector. Don't point it at an Arabic page unless your audience outside the GCC is mostly Arabic speaking.

4. Keep canonicals and hreflang aligned #

5. Prefer sitemaps on large or multi-domain sites #

For catalogues with thousands of product pages, or a setup split across .ae and .sa, put hreflang in XML sitemaps. Return links are easier to keep complete, and you avoid relying on templates or JavaScript to inject tags correctly on every page.

Arabic Keyword Research: Research Each Market Separately #

Translating an English keyword list into Arabic is the fastest way to target words nobody searches. Arabic keyword research has to start in Arabic, per country.

Dialect and vocabulary #

The same product often has a formal name, a Gulf name and a borrowed English name. Take a forklift: the formal term is رافعة شوكية, but many buyers simply type فوركلفت. A machine can be آلة in formal writing and مكينة or ماكينة in everyday search. Your page should be built around the term the market actually uses, with the formal term supporting it.

Spelling variants #

Arabic has several common spelling variations that change the exact query:

• Alef forms: أ / إ / آ / ا (people often type the bare ا)
• Taa marbuta vs haa at the end of a word: ة / ه
• Final yaa vs alef maqsura: ي / ى

Google normalizes many of these, but not always. Check the variants separately in Keyword Planner and in the live results before deciding which spelling goes in the title and H1.

Mixed-language queries and Arabizi #

GCC users mix languages constantly: سعر forklift, "excavator للبيع", or a brand name in English followed by Arabic. Some users, especially younger ones, type Arabic in Latin letters and numbers (Arabizi), such as "7aflat" for buses. These queries rarely show large volumes, but together they represent real demand that monolingual keyword maps miss.

Research per location #

Set Keyword Planner, Semrush or Ahrefs to the UAE and Saudi Arabia separately, and review the actual results page from each country. The intent behind the same Arabic query can differ: one market may show suppliers, the other classifieds or government pages. If the results differ, the pages should differ.

A useful practice is to build one keyword map per market with three columns per topic: the main Arabic term, its dialect and spelling variants, and the English or mixed version. That map then drives the titles, headings and internal anchor text of each country version.

Localize, Don't Just Translate #

If ar-AE and ar-SA pages carry identical text, Google may treat them as duplicates and choose one canonical, even with correct hreflang. Each market version needs content that actually differs where the market differs.

At minimum, localize these elements per country:

• Prices and currency: AED on UAE pages, SAR on Saudi pages, in both the visible price and the priceCurrency in Product schema.
• Contact details: a local phone number, WhatsApp number and address for each market, matching the Google Business Profile for that location.
• Delivery, warranty and service terms: cities served, lead times and after-sales support specific to the country.
• Local proof: projects, clients, certifications and case studies from that market. A Saudi buyer wants to see Saudi references.
• Working week and dates: the UAE works Monday to Friday, Saudi Arabia Sunday to Thursday, so business hours and response-time promises differ. Saudi audiences also meet Hijri dates often, so consider showing both where dates matter.
• Titles and meta descriptions: written per market, using that market's main keyword, not a copy of the other version.

Machine translation is a starting point, not a page #

Auto-translated Arabic is easy to spot: literal phrasing, English word order, and technical terms that nobody in the region uses. It reads poorly to users and adds little value for Google. Use translation tools for a first draft if needed, then have a native Gulf Arabic writer rewrite it for the market. Product specs, CTAs and headings deserve the most attention, because that is where buyers decide whether to call.

Also check consistency across the site. Navigation, forms, error messages, cookie banners and PDF brochures are often left in English on "Arabic" pages. To a user, a half-translated page looks unfinished, and it weakens the language signal Google reads from the page.

The Technical Layer of Arabic SEO #

Most Arabic SEO problems I see in audits are not keyword problems. They are technical issues that only appear on right-to-left (RTL) pages.

Set language and direction correctly #

Every Arabic page should declare both its language and its direction in the tag:

Google says it detects language from the visible content rather than the lang attribute, but Bing uses language signals such as lang and the content-language meta tag. Bing also feeds several AI search products, so getting this right matters more than it used to.

Handle mixed-direction text #

Arabic pages are full of left-to-right content: model numbers, phone numbers, prices, email addresses and English brand names. Without proper handling, "+971 4 123 4567" or "CAT 320D" renders in the wrong order. Wrap these in or a so they display correctly.

Build RTL layouts with logical CSS #

Use CSS logical properties such as margin-inline-start and padding-inline-end instead of left and right. Mirror directional icons like arrows and breadcrumbs, but not logos, media controls or product images. A broken mirrored layout causes layout shift and hurts engagement on mobile, where most GCC traffic comes from.

Choose a URL approach and stay consistent #

Arabic slugs (/sa-ar/رافعة-شوكية/) can help relevance and look natural in results, but they become long percent-encoded strings when shared or copied. Transliterated or English slugs are cleaner to manage. Either works. What breaks things is mixing both, or listing Arabic URLs unencoded in sitemaps, canonicals or hreflang. Always use the same UTF-8 percent-encoded form everywhere.

Optimize Arabic fonts #

Arabic web fonts are heavy because of the number of glyph forms. Self-host them, subset to the characters and weights you need, preload the main font, and use font-display: swap. Unoptimized Arabic fonts are a frequent cause of poor LCP on Arabic versions of sites whose English versions pass Core Web Vitals.

Watch JavaScript-rendered content #

If the Arabic version is loaded through a language switcher or client-side translation, check what Googlebot actually sees with the URL Inspection tool. Hreflang tags, titles and main content should be in the initial HTML, not injected after rendering.

Arabic Content and AI Search #

AI Overviews, ChatGPT, Perplexity and Gemini answer Arabic questions in Arabic, and they need Arabic sources to cite. Compared with English, there is far less well-structured, market-specific Arabic content in most B2B and service niches. That gap is an opportunity for brands that publish properly localized pages.

A few practices make Arabic pages easier for AI systems to retrieve and cite:

1. Answer first. Open key sections with a direct one or two sentence answer in clear Arabic, then expand. AI systems extract passages, not whole pages.
2. Keep the brand entity consistent across languages. Use the same Organization schema @id on English and Arabic pages, add the Arabic brand name as an alternateName, and link the same profiles in sameAs. The goal is that "YourBrand" and its Arabic name resolve to one entity, not two.
3. Mark the language and market in schema. Use inLanguage (ar-SA, ar-AE) on WebPage and Article, areaServed on Organization or Service, and the local currency in every Offer.
4. Write Arabic FAQs from real questions. Use the questions customers ask your sales team on WhatsApp and calls, in the words they use, not translated English FAQs.
5. Earn Arabic mentions. AI answers lean on third-party sources. Coverage in Arabic regional media, industry directories and local associations builds the corroboration that gets a brand named in Arabic answers.

Finally, test it. Ask the same buying question in Arabic and English, from the UAE and from Saudi Arabia, across the main AI tools. Note which brand and which country version gets cited. That gives you a baseline for Arabic AI visibility that most competitors don't have.

Common Arabic SEO Mistakes on GCC Sites #

Run a crawl of all language versions together in Screaming Frog with hreflang extraction enabled, and check Google-selected canonicals for each country version with URL Inspection in Search Console after every major release. Most of these problems come back quietly when templates change.

Frequently Asked Questions #

Is hreflang="ar" wrong? No. It is valid and useful as a fallback for Arabic speakers in countries you don't target separately. It is only a problem when it is the sole Arabic tag on a site that serves several GCC markets with different prices, contacts or offers.

Do I need separate pages for the UAE and Saudi Arabia if the content is similar? If price, contact, delivery or legal details differ, yes. If nothing differs, one Arabic page tagged ar is more honest than two near-identical pages.

Should Arabic URLs use Arabic characters? Either approach works. Pick one, keep it consistent, and use the encoded form everywhere it is referenced.

Does Google use the lang attribute? Google detects language from the visible content, but other search engines and AI tools use it. Always set lang and dir correctly.

Conclusion #

Arabic SEO in the GCC is not a translation project. It is market targeting. The ar tag answers "what language is this?" but GCC buyers also need "is this for my country?" Google can only answer that if the site tells it clearly through country-level hreflang, self-canonical market pages, and content that actually reflects each market's vocabulary, prices and trust signals.

Get the structure right first, research keywords per country in Arabic, localize beyond the words, and fix the RTL technical layer. Brands that do this compete in a much smaller and more relevant set of results, in classic search and increasingly in Arabic AI answers.