Many Arabic sites in Lebanon and the Gulf follow the same pattern. The English site came first. A few months later a translator produced Arabic pages. Those pages have underperformed ever since. The words are correct—but they target phrases nobody searches, miss common spellings, and read like translations rather than content written for an Arabic speaker.

Arabic SEO is not English SEO with the text swapped. Spelling variants change matching. Formal written Arabic and the dialects people actually type sit far apart. Loanwords compete with Arabic terms. Right-to-left layouts affect both usability and technical setup.

Why Arabic Is Different?

Three features drive almost every decision.

Diglossia — Modern Standard Arabic (MSA) for formal writing; spoken dialects for everyday search. People increasingly type in dialect, especially in Lebanon and the Gulf, while most sites write only in MSA. A Lebanese user might search “قديش سعر تصميم موقع”; a page optimised only for “كم تكلفة تصميم موقع إلكتروني” misses them.

Spelling variation — The same word can appear in several valid or common forms: hamza (أ، إ، آ، ا), final taa marbuta (ة or ه), final alef maqsura (ى or ي). On a phone keyboard, people often type the simplest version.

Mixed vocabulary — Marketing and tech terms often have both an Arabic form and a widely used loanword: “تحسين محركات البحث” and “سيو,” “أونلاين” alongside Arabic equivalents. Some users search in Arabizi (Arabic in Latin letters). Keyword targeting needs more research, not less.

Keyword Research That Matches Real Search

Start from behaviour, not translated English lists. Literal translation is the single biggest cause of weak Arabic pages.

Write down the intent, then find every way people express it—MSA, Lebanese dialect, Gulf phrasing, loanword-heavy versions. Search each phrasing in Google with the target country selected. Note autocomplete, who ranks, and what Google associates with that intent.

Tools help, but Arabic data for smaller markets like Lebanon can be thin, and dialect or spelling variants are often missing or merged. Combine tools with autocomplete, “People also ask,” related searches, and your own Search Console data.

Check spelling variants in the results. Google often treats them as the same word—but not always. If results differ, mention important variants naturally in body text or FAQs rather than stuffing every form into the title.

Use MSA as the backbone so pages stay readable across Arabic markets. Add common dialect phrasings where they fit—FAQs, question-style headings, local service pages. Everyday words differ by market: a mobile phone is often “خلوي” or “تلفون” in Lebanon, “جوال” in Saudi Arabia.

On-Page Basics

Titles and metas — Primary phrase near the start. Arabic letters vary in width; Google truncates by display width, so keep titles concise and check the preview. Skip diacritics (tashkeel) in titles and descriptions—they rarely help matching and clutter snippets. Write metas in natural, persuasive Arabic with a clear benefit.

Headings and body — One H1 with the primary phrase. H2s and H3s that echo real questions. Write natively: local examples, currencies, cities, payment habits. A Lebanese page should feel Lebanese; a Saudi page should feel Saudi. Thin translated pages are a common reason Arabic content fails to index or rank.

Markup — lang="ar" and dir="rtl" on Arabic pages. Use hreflang to connect Arabic with English and French versions (ar for all markets, or ar-LB / ar-SA only when you truly have country-specific versions). Add inLanguage in structured data where relevant.

URLs: Arabic, English, or Neither

Three options, all valid if applied consistently:

• Arabic-script slugs — Look natural in Arabic results and when shared. Can become long percent-encoded strings; some CMS cut them mid-word. Keep them short (about four or five words) and test truncation.
• English slugs on Arabic pages — Short, stable, easy to manage. Work fine for ranking.
• Transliterated slugs — Weakest option: neither readable Arabic nor meaningful English.

Don’t change existing URLs without a clear reason—and redirect properly when you do.

Technical and Local Details

RTL affects SEO through usability and speed. Layouts, navigation, breadcrumbs, and icons should mirror correctly. Mixed-direction content (phone numbers, prices, English brand names) must display cleanly inside Arabic text.

Arabic web fonts can be large. Multiple weights slow pages and hurt Core Web Vitals on mobile. Limit weights, use modern formats, and test Arabic pages separately from English ones.

For local businesses: Arabic details on Google Business Profile where appropriate, consistent business name, reviews and replies in the customer’s language, Arabic citations and media coverage where they fit.

Authority comes from links and mentions on relevant Arabic-language sites—industry publications, associations, local news, partners. Useful Arabic content (guides, data, local insight) is the sustainable path. Avoid low-quality link networks.

Measuring Separately

Track Arabic results apart from English. In Search Console, filter by the /ar/ folder (or Arabic subdomain). Review queries for phrasing and spelling variants. Use regex to group variants and separate Arabic-script, Arabizi, and English queries landing on Arabic pages. Compare by country—the same page can perform very differently in Lebanon, the UAE, and Saudi Arabia.

Mistakes That Keep Showing Up

• Literal translation of English pages and keyword lists
• MSA only, ignoring dialect for price and service questions
• One-market terms used for another (Lebanese language for Saudi audiences, or the reverse)
• Long Arabic slugs that get truncated, or URL changes without redirects
• Missing or broken language markup (dir="rtl", lang, hreflang)

Fixing these often unlocks more value than writing new content.

Bottom Line

Arabic SEO works when pages match how people actually search—not how a translator rendered an English brief. Research real phrasing (including dialect and spelling variants), write natively, set language and direction correctly, keep pages fast, and measure Arabic traffic on its own. Done well, Arabic content reaches audiences English pages never will—precisely because so many competitors still treat it as a translation task.