Arabic SEO: the complete guide for 2026
Arabic SEO is ranking pages written for Arabic searchers: research in Arabic, write natively, build a clean /ar/ section and earn Arabic links.
Arabic SEO is the work of getting pages written for Arabic speakers to rank in Arabic search results. It means researching keywords in Arabic, not translating English ones; writing natively for the dialect your buyers use; building a clean right-to-left section with correct hreflang; and earning links from Arabic sites that search engines already trust.
This guide covers each of those pieces in the order you should tackle them, with the decisions that trip up most bilingual sites. If you would rather hand the whole programme to a team that does this every week, our Arabic SEO service page explains what we ship and how it is priced.
On this page
What is Arabic SEO, and why is it not just translated SEO?
Arabic SEO uses the same search engines and the same ranking systems as SEO in any language. What changes is almost every input you feed those systems. The words people type, the way they spell them, the layout of the page and the sites that link to you all behave differently in Arabic.
Start with the words. An English keyword list translated into Arabic gives you phrases that are grammatically correct and that almost nobody searches. Arabic speakers often search in their own dialect, mix Arabic and English in the same query, or type a brand name in Latin letters and the product in Arabic. A translated list misses all of that.
Then the spelling. Arabic allows several spellings of the same word. The letter alif can be written with or without a hamza, a final taa marbuta is often typed as a plain haa, and a final yaa is often typed as alif maqsura. Search engines normalise some of these variants and not others, which is why our guide to hamza and taa marbuta spelling variants exists as its own post.
Then the page itself. Arabic reads right to left. A page that renders with the wrong direction, flipped punctuation or a mirrored layout that breaks on mobile looks broken to a native reader, and people leave broken pages. The W3C recommends setting direction with the dir attribute on the html element rather than with CSS alone [3].
Finally, the web around you. There are fewer Arabic websites than English ones, fewer Arabic publishers who link out, and fewer Arabic directories worth being listed in. Authority is harder to earn and more valuable once you have it.
How do Arabic speakers actually search?
Arabic speakers search in a mix of Modern Standard Arabic, their own dialect and English. Which one they use depends on the topic, the device and whether they are typing or speaking. Your job is to find out which mix your buyers use before you write a single page.
Modern Standard Arabic is the written standard used in news, government and formal writing. It works well for informational queries and for anything that sounds official. Dialects such as Gulf, Egyptian and Levantine Arabic show up in commercial and local queries, product names and anything conversational. Our explainer on Arabic dialects in search walks through how to tell which one a query belongs to.
English and Latin-script Arabic also appear more than most teams expect. People search brand names, software, medical and technical terms in English even when the rest of the query is Arabic. Some younger searchers type Arabic words in Latin letters with numbers standing in for sounds, often called Arabizi. You do not need to build pages for Arabizi, but you should know if your buyers use it, because it tells you they may also search in English.
Voice changes the picture again. Spoken queries are longer, more dialectal and more likely to be full questions. If your buyers use phones and smart speakers, read our piece on Arabic voice search before you set your headings, because question-shaped headings in natural Arabic are what voice answers pull from.
The practical output of this step is simple: for each topic you care about, a note that says which form of Arabic your buyers use, which English terms they keep, and which spellings you need to cover.
How do you do keyword research in Arabic?
Arabic keyword research starts in Arabic, with native speakers, and only then moves to tools. Tools give you volumes and difficulty; people give you the words. If you reverse that order, you end up with a tidy spreadsheet of phrases nobody uses.
Most mainstream keyword tools have Arabic databases, but their coverage is thinner than in English, and they often split spelling variants into separate rows with tiny volumes. Add those rows together before you judge a topic. Google Search Console is often the most honest source once you have some Arabic pages live, because it shows the exact queries that already bring you impressions. We compare the options, including free ones, in our guide to Arabic keyword research tools.
Interview three to five native speakers who buy what you sell
Ask them how they would search for it, out loud and typed. Write down every phrase exactly as they say it, including English words and dialect terms.
Expand the list with autocomplete and related searches
Type each seed phrase into Google in Arabic, on a phone and on a desktop, and record the suggestions. They reflect what people actually type.
Pull volumes and group spelling variants
Run the list through a keyword tool with an Arabic database. Merge rows that differ only by hamza, taa marbuta or alif maqsura, and add their volumes.
Tag each keyword by dialect and intent
Mark whether a phrase is Modern Standard Arabic, dialect or mixed, and whether the searcher wants to learn, compare or buy.
Map one primary keyword to one page
Group close variants onto the same page. Two pages chasing the same query in two spellings compete with each other and both lose.
A common mistake at this stage is picking the variant with the highest volume and ignoring the rest. Use the most common spelling in your title and heading, then use the other forms naturally in the body where they fit. That covers the variants without making the page read like a keyword list.
Should you translate or rewrite content for Arabic?
Rewrite it. Translation moves meaning from one language to another; transcreation rebuilds the page for a different reader, with different keywords, examples and calls to action. For search, the second approach almost always wins, because the page is built around what Arabic speakers search rather than what English speakers searched.
That does not mean you throw away the English work. Facts, product details, prices and structure can carry across. What changes is the headings, the angle, the examples, the idioms and the order of arguments. A translated page often answers a question nobody in the Arabic market is asking.
| Approach | What it does | Cost and speed | When to use it |
|---|---|---|---|
| Machine translation | Converts English text word by word with light cleanup | Cheapest and fastest | Internal drafts, support docs, never money pages |
| Human translation | Accurate Arabic version of the English page | Moderate cost, quick | Legal pages, policies, product specs |
| Transcreation | Rebuilds the page around Arabic keywords and examples | Higher cost, slower | Service pages, category pages, key blog posts |
| Native writing | Written in Arabic from an Arabic brief | Similar to transcreation | Topics with no English equivalent or strong local intent |
We go deeper into the trade-offs, including how to brief a transcreator, in translation vs transcreation. The short version: spend your transcreation budget on the pages that make money, and use human translation for the rest.
Google does not penalise translated content for being translated. Its guidance asks whether content is helpful, reliable and written for people [5]. A stiff translation that ignores how the audience searches rarely meets that bar, which is the real reason it underperforms.
How long should Arabic content be?
As long as it needs to be to answer the query well, and no longer. There is no ideal Arabic word count. Arabic also tends to use fewer words than English to say the same thing, because prepositions, pronouns and articles attach to words, so a page that looks short next to its English twin may say just as much.
Look at what already ranks for your query in Arabic. If the top results are short answers, a 3,000-word page will not win by being longer. If they are thin, a complete and well-structured page can take the spot. Our post on how long Arabic content should be explains how to size a page from the results rather than from a rule.
What matters more than length is structure. Clear question-shaped headings, a direct answer near the top, short paragraphs and tables where they help all make an Arabic page easier to scan and easier for AI answers to quote.
What technical setup does an Arabic site need?
An Arabic site needs four technical decisions made correctly: where the Arabic pages live, how their URLs are written, how hreflang connects them to other languages, and how the pages render right to left. Get these right once and they hold for years. Get them wrong and every page you publish inherits the problem.
Subfolder, subdomain or separate domain?
Google supports all three structures for language versions [2]. The choice is mostly about authority and operations. A subfolder such as example.com/ar/ shares the authority of the main domain and is the simplest to run. A subdomain such as ar.example.com is sometimes easier when the Arabic site sits on different infrastructure. A separate country domain sends a strong local signal but starts from zero authority.
| Structure | Example | Strengths | Watch out for |
|---|---|---|---|
| Subfolder | example.com/ar/ | Shares domain authority, one property, simplest to run | Needs a CMS that handles two languages and two directions |
| Subdomain | ar.example.com | Can run on separate hosting or a separate CMS | Authority is shared less directly; more setup to track |
| Country domain | example.sa or example.ae | Strong local signal to users and search engines | Starts from zero links; costs more to maintain |
For most businesses we recommend a subfolder. The full reasoning, including when a subdomain is the better call, is in subfolder vs subdomain for Arabic.
Arabic slugs or transliterated URLs?
Google recommends readable URLs and supports non-ASCII characters in them, as long as they are encoded correctly [4]. That leaves you a real choice. Arabic slugs match the language of the page and can show in results as readable Arabic, but they turn into long percent-encoded strings when copied into email or chat. Transliterated slugs stay short and portable but mean nothing to most Arabic readers.
There is also a third option: keep English slugs on both language versions so the URL structure mirrors itself. Each has a place. We lay them side by side in Arabic URLs vs transliteration. Whatever you pick, pick it once and apply it everywhere, because changing URLs later means redirects.
Hreflang for Arabic pages
Hreflang tells Google which pages are language versions of each other, so it can show the right one to the right searcher [1]. Each page lists every version, including itself. Use ar when one Arabic page serves every Arabic speaker, and add a region such as ar-SA or ar-AE only when you have genuinely different pages for different countries. Add an x-default for everyone else.
The most common errors we find are missing return links, where the English page points to the Arabic one but not the other way round, and region codes on pages that are not really regional. Our step-by-step on hreflang for Arabic shows the exact tags and how to test them.
Right-to-left rendering
Set lang="ar" and dir="rtl" on the html element of every Arabic page [3]. Then check what breaks. Common problems include icons and arrows that point the wrong way, numbers and English words that jump to the wrong side of a sentence, forms whose labels sit on the wrong edge, and carousels that scroll backwards.
Use logical CSS properties such as margin-inline-start instead of margin-left, so the layout flips on its own. Check fonts too: an Arabic page set in a Latin font with a weak Arabic fallback reads badly and looks cheap. Our RTL website checklist covers the full list we run on every Arabic launch.
Does schema markup work in Arabic?
Yes. Structured data is language-neutral: the property names stay in English and the values can be in Arabic. Google reads Arabic names, descriptions, addresses and FAQ answers in JSON-LD the same way it reads English ones.
The work is mostly about consistency. The Arabic page's Organization, Article or Product markup should describe the Arabic page, with Arabic text in the values and an inLanguage value of ar. Author names should match the names shown on the page. Prices should use the currency the page shows. Mixed markup, where the page is Arabic and the JSON-LD still describes the English twin, is the most common mistake we see.
We walk through the types that matter most and show working examples in schema markup in Arabic. Structured data will not rescue a weak page, but it helps search engines and AI assistants understand exactly what a good one is about.
How do you build E-E-A-T for Arabic content?
You show real people, real experience and real sources, in Arabic. Google's guidance asks who wrote a page, how it was made and why it exists [5]. On Arabic sites those answers are often missing, because the Arabic pages were produced as an afterthought and nobody's name is on them.
Start with authors. Give every Arabic article a named author with an Arabic bio page that explains their background. If the author does not write Arabic, name the Arabic editor or reviewer too. Link to Arabic sources where they exist, such as government portals, regulators and established Arabic publishers, and cite English sources where the best evidence is in English.
Trust signals on the page matter as much. An Arabic contact page, local phone numbers, prices in the local currency, Arabic policies and reviews from Arabic-speaking customers all tell a reader, and a search engine, that the Arabic site is maintained by people who serve that market. Our guide to E-E-A-T for Arabic sites covers author pages, reviewer credits and the page-level signals in detail.
Where do Arabic backlinks come from?
From the same kinds of places as English links, but fewer of them. Arabic news sites, industry publications, universities, chambers of commerce, trade associations, event listings and quality directories are the core sources. The pool is smaller, so each good link counts for more and takes longer to get.
The fastest start is usually the relationships you already have. Partners, suppliers, customers and associations in Arabic-speaking markets may already have Arabic sites that could mention you. After that, original data and useful Arabic resources earn links that pitching alone cannot, because Arabic journalists and bloggers have less to cite than their English peers.
Avoid bought link packages sold as Arabic SEO. Many are networks of thin sites with auto-translated content, and they carry the same risk as any paid link scheme. We list the sources we actually use, and how we approach them, in Arabic link building sources.
How do Arabic pages get cited by AI assistants?
The same way they get cited in English: by being clear, specific, well-structured and easy to trust. AI assistants such as ChatGPT, Gemini and Perplexity answer Arabic questions, and they pull from Arabic pages when good ones exist. Because fewer good Arabic pages exist, a well-built one has a real chance of becoming the source they quote.
Put a direct answer under each question-shaped heading. Use tables for comparisons and steps for processes. Keep facts, prices and names consistent across your Arabic pages, your English pages and your business listings. Structured data, named authors and cited sources all help an assistant decide your page is safe to quote.
What are the most common Arabic SEO mistakes?
Most Arabic sites that underperform make the same handful of mistakes, and nearly all of them come from treating Arabic as a copy of the English site. The fixes are rarely expensive. They just need someone to look.
The first is translating the keyword list instead of researching it. The pages end up targeting phrases that read well and that nobody types. The second is launching the Arabic section without hreflang, or with hreflang on one side only, so Google keeps showing English pages to Arabic searchers.
The third is a canonical tag on every Arabic page that points to its English twin. That tells Google the Arabic page is a duplicate and should not be shown, which quietly removes the whole section from results. The fourth is leaving the Arabic pages without authors, sources or local contact details, so they look abandoned next to the English ones.
The fifth is publishing the Arabic section and then never updating it. Prices, offers and product names drift out of step with the English site, and readers notice before search engines do. Put the Arabic pages on the same update schedule as the English ones, with a named owner, and most of these problems never come back.
What does Arabic SEO cost, and how long does it take?
It costs more per page than English SEO, and it takes about as long. The extra cost comes from native research and writing, RTL QA and the slower pace of Arabic link building. The timeline depends on competition: many Arabic topics have so few good pages that new content moves in two to four months, while competitive commercial terms take six to twelve.
Expect three phases. The first month or two is setup: research, structure, hreflang, RTL fixes and a content plan. The next few months are publishing: the pages that match buying intent first, then the supporting guides. Link building starts early and runs throughout, because it is the slowest piece.
Ask any provider to show you Arabic work they have written, not translated, and to name the native speakers on the team. You can see how we scope and price this on our pricing page. We are an agency that sells this service, so weigh our advice with that in mind; the checks above apply to us as much as to anyone.
How do you know Arabic SEO is working?
Track Arabic pages separately from English ones. In Google Search Console, filter by the /ar/ folder or the Arabic property and watch impressions first, then clicks, then the queries driving them. Impressions rising on Arabic queries you did not target is a sign the research was thin and the market is telling you what to write next.
In analytics, segment conversions by page language. A bilingual site often finds that Arabic visitors convert at a different rate, on different pages, through different contact methods such as WhatsApp or phone. If you only report blended numbers, the Arabic programme can be working and look flat.
Check the indexing basics every month: Arabic pages indexed, hreflang errors, and the right language version showing for Arabic queries. When the wrong version shows, the problem is almost always a hreflang tag or a canonical pointing at the English page [1].
What this guide covers next
Each part of this guide has a detailed companion post. Start with the one that matches your biggest gap:
- Arabic dialects in search explains how Gulf, Egyptian, Levantine and Modern Standard Arabic change the words people type.
- Arabic keyword research tools compares the tools and shows a repeatable research process.
- The RTL website checklist lists every right-to-left issue we test before an Arabic launch.
- Hreflang for Arabic shows the exact tags for ar, ar-SA and x-default and how to test them.
- Translation vs transcreation helps you decide which pages to translate and which to rebuild.
- Hamza and taa marbuta variants covers spelling variants and how to target them without duplicate pages.
- Arabic URLs vs transliteration weighs Arabic slugs against Latin ones.
- How long Arabic content should be shows how to size a page from the search results.
- Arabic link building sources lists where Arabic backlinks actually come from.
- Subfolder vs subdomain for Arabic settles where your Arabic pages should live.
- Schema markup in Arabic gives working JSON-LD examples with Arabic values.
- Arabic voice search explains how spoken Arabic queries differ from typed ones.
- E-E-A-T for Arabic sites covers author pages, reviewers and trust signals in Arabic.
None of this replaces off-page trust. A page that reads well in Arabic still benefits from being mentioned somewhere a reader already trusts, and pitching regional publications for coverage is one concrete way to earn that outside your own domain.
Questions people also ask
Is Arabic SEO different from English SEO?
The ranking system is the same, but the inputs differ. Arabic has several spellings for many words, strong dialect differences, right-to-left layout and a thinner pool of linking sites, so research, writing and technical setup all need Arabic-specific decisions.
Can I just machine-translate my English pages into Arabic?
You can, but it rarely ranks. Translated pages target the words English speakers use, not the words Arabic speakers type. Use translation for the facts and have a native writer rebuild the headings, examples and keywords around real Arabic queries.
Should my Arabic site use a subfolder or a subdomain?
For most businesses a subfolder such as /ar/ is the simpler choice, because it shares the authority of the main domain and needs one property to manage. A subdomain or separate domain makes sense when the Arabic site is run by a different team or on different infrastructure.
How long does Arabic SEO take to show results?
On topics with little Arabic competition, new pages can move in two to four months. Competitive commercial terms usually take six to twelve months, mostly because Arabic links take time to earn.
Do I need hreflang if I only have English and Arabic?
Yes. Hreflang tells Google that the two pages are versions of each other, so it can show the Arabic one to Arabic searchers. Each page lists itself and the other, and you add an x-default for everyone else.
Sources
- Tell Google about localized versions of your page — Google Search Central (checked 22 September 2026)
- Managing multi-regional and multilingual sites — Google Search Central (checked 22 September 2026)
- Structural markup and right-to-left text in HTML — W3C Internationalization (checked 22 September 2026)
- URL structure best practices for Google — Google Search Central (checked 22 September 2026)
- Creating helpful, reliable, people-first content — Google Search Central (checked 22 September 2026)
Find out what your Arabic pages are missing
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Ibrahem HelalCo-founder
Leads strategy and delivery.
Works on: SEO, GEO
Reviewed before publishing by Jeremy Zava, Co-founder.
- Arabic Keyword Research: Tools and MethodMost keyword tools were built for English first. Here's how to research Arabic keywords properly, and which tools actually hold up once you do.
- Hreflang for Arabic: The Exact Tags to UseHow to set hreflang for Arabic pages: which language and region codes to use, where the tags go, and the mistakes that break them most often.
- Translation vs Transcreation for Arabic SEOTranslation and transcreation are different products with different prices. Here's when a straight translation is fine, and when Arabic pages need a rewrite.
- Subfolder vs Subdomain for Arabic: Which to UseA subfolder like /ar/ shares your domain's authority; a subdomain runs independently. Here is how to choose for an Arabic section of your site.