Arabic SEO: what changes when customers search in Arabic
Arabic SEO is not translated English SEO. Dialect, diacritics, transliteration and right-to-left rendering each change what ranks, and most sites get all four wrong.
Key takeaways
- Build the Arabic keyword set from country-filtered Search Console query data, not by translating the English list.
- Prefer undiacritised forms in titles and headings, since that is how most people type.
- Hreflang must be reciprocal in both directions, plus an x-default; one-way declarations are ignored.
- Test right-to-left layouts with real mixed-direction content containing Latin names, URLs and numbers.
Arabic SEO differs from English SEO in four specific ways: search intent is often expressed in dialect rather than Modern Standard Arabic, the same word appears with and without diacritics, brand and technical terms are searched in both Arabic script and Latin transliteration, and right-to-left rendering breaks layouts that were never tested for it. Translating an English keyword list will miss most of the demand.
Dialect against Modern Standard Arabic
Formal written Arabic is what your content is likely written in. It is frequently not what people type. A user in Baghdad, one in Riyadh and one in Dubai may use three different words for the same everyday product, and none of them may be the dictionary term. The practical method is to build the keyword set from real query data for each market separately, then write content that uses the dialect term naturally in headings and body copy while keeping the standard term present for breadth.
This is one of the few areas where Search Console is more useful than any keyword tool, because it shows the actual strings that produced impressions for your site in each country. Filter by country, export the queries, and read them. The vocabulary gap between what you published and what people typed is usually visible within ten minutes.
Diacritics, hamza and spelling variants
- Most users type without diacritics. Content that only exists in a fully diacritised form can miss the undiacritised query, so prefer the plain form in titles and headings.
- Alef variants and the taa marbuta against haa are the two most common spelling inconsistencies. Pick one convention, apply it consistently, and let the search engine handle the normalisation rather than hedging across both.
- Brand names are searched in both scripts. If your company is known by a Latin name, you need both the Arabic transliteration and the Latin string to appear on the page and in structured data.
- Numbers appear as both Western and Eastern Arabic numerals. Prices and phone numbers should be readable either way, and marked up so machines parse them unambiguously.
The technical layer
Serve Arabic pages on their own URLs with a language prefix, declare the language and direction on the html element, and pair each page with its English counterpart using reciprocal hreflang. A one-directional hreflang declaration is ignored, which is the most common error we find on bilingual sites in the region. Add an x-default pointing at the version you want served to users whose language you cannot determine.
Right-to-left rendering deserves a genuine test rather than a CSS flag. Mixed-direction content, where an Arabic sentence contains a Latin product name, a URL or a number, is where layouts break. Test with real content, not lorem ipsum, and check that punctuation lands on the correct side of the line.
Content that ranks against content that reads as translated
Machine-translated Arabic is recognisable to a reader within a sentence, and readers leave. It also tends to lose the dialect vocabulary that was the point of the exercise. Have Arabic content written or substantially rewritten by someone who works in the market rather than post-edited from English. The cost difference is smaller than the ranking difference.
Translating the page is a formality. Rebuilding the keyword set for how people actually type is the work.
Sources