Arabic readers do not all type the same words for the same need. One person searches in formal Modern Standard Arabic, another uses a dialect word, a third drops the hamza, and a fourth writes in Latin letters. This guide shows how to find the words your readers actually use, starting from your own Search Console data rather than from a translated English keyword list.
Why Arabic keyword research is its own problem
Three things make Arabic harder than English here. The first is the gap between MSA and spoken dialects: the word a Gulf reader uses for a phone may differ from what an Egyptian or Moroccan reader uses. The second is spelling: many people type without hamza, swap ة and ه at the end of a word, or write ي where ى belongs. The third is mixing: Arabic nouns next to English brand names, and Arabizi written in Latin script.
Google acknowledges that misspelling is common in general. In a March 2021 post, Pandu Nayak wrote that “one out of 10 search queries is misspelled” every day, and that Google’s language models look at a query in context. That post is about spelling in general. Google has not documented how its systems handle specific Arabic variants such as hamza forms, so do not assume two spellings are treated as identical. Treat each variant as something to check in your data.
The concept: start from the reader’s words
Google’s SEO starter guide gives simple advice: think about the words a user might search for to find a piece of your content. It also points out that different people use different words for the same thing, using the example of “charcuterie” versus “cheese board”. Arabic has this at a much larger scale. Your job is to learn which of those words your readers use, then write naturally around the most common ones.
Step by step
- Write down the reader’s task in plain words. Not “keywords”, but the problem: “fix a phone that won’t charge” or “open a bank account online”.
- List the MSA and dialect terms for that task. This is an editorial method, not a Google rule. Ask colleagues from different countries how they would search.
- Add the spelling variants you expect. Cover hamza forms (أ ا إ), taa marbuta and haa (ة ه), alif maqsura and yaa (ى ي), common English loanwords, and Arabizi.
- Open the Performance report in Search Console. Google describes Search Console as showing which search terms bring people to your site. Filter by page and read the real queries. This is where you see which variants people actually type.
- Group queries by intent, not by spelling. Variants of the same need belong to one page.
- Choose the main phrasing for the title and headings. Use the form that appears most in your own data and reads naturally. Let other variants appear only where they fit the sentence.
- Handle bilingual queries. When people search an English product name with an Arabic noun, keep the product name in Latin script as readers write it. If most queries for a topic are fully in English, an English page may serve those readers better.
- Review queries every quarter and update titles or add a short section when new wording appears.
An illustrative Arabic example
Suppose you run a phone repair shop in Jeddah and write a guide about a phone that stops charging. The list below is invented to show the method, not taken from any tool:
- MSA: إصلاح شحن الهاتف
- Common everyday terms: تصليح شحن الجوال, الجوال لا يشحن
- Loanword: تصليح شاحن الموبايل
- Spelling variant: اصلاح (without hamza)
- Arabizi: tasleeh shahn jawal
After a few weeks, your Performance report might show that most impressions come from one or two of these forms. That becomes your title. The other forms can appear once each where they read naturally, for example in a sentence that says the problem is also known as “الجوال لا يشحن”. One page, one intent, natural language.
A note on language detection: Google says it uses the visible content of a page to determine its language, not code-level language information. So an Arabic page with a few English terms is still an Arabic page, and the Arabic body text is what counts.
Checklist
| Check | How | Tool |
|---|---|---|
| Reader task is defined | Write one sentence describing the need | Notebook or content brief |
| MSA and dialect terms listed | Ask readers or colleagues from several countries | Spreadsheet |
| Spelling variants noted | Add hamza, ة ه and ى ي forms to the list | Spreadsheet |
| Real queries reviewed | Filter queries by page | Search Console Performance report |
| One page per intent | Merge variant lists into one topic | Your content plan |
| Title uses the leading form | Match the most frequent natural phrasing | Your CMS title field |
| No stuffing | Read the page aloud and cut repeated variants | Your own judgement |
| Quarterly review booked | Compare new queries with the previous quarter | Search Console Performance report |
Common mistakes
- Writing only in formal MSA, or only in dialect, without checking data. Your readers decide the vocabulary. Look at their queries first.
- Repeating every spelling variant in the text. Google’s starter guide states that keyword stuffing is against its spam policies. A paragraph with five spellings of one word also reads badly.
- Filling the keywords meta tag. Google says Search does not use it.
- Translating English keyword lists literally. An English list tells you the topic, not the Arabic words people type.
- Creating a separate page for each spelling. Variants of one need belong on one useful page.
- Assuming Google treats Arabic variants as the same word. It is not documented. Check your own query data instead.
What I like about this method is that it keeps you honest: you stop arguing about which word is “correct” and start reading what your readers actually typed.
Sources
- Google Search Central, SEO starter guide, documentation page consulted 10 October 2025, https://developers.google.com/search/docs/fundamentals/seo-starter-guide
- Google (The Keyword blog), Pandu Nayak on how Google Search handles spelling, 29 March 2021, https://blog.google/products-and-platforms/products/search/abcs-spelling-google-search/
- Google Search Central, using Google Analytics and Search Console together, documentation page consulted 10 October 2025, https://developers.google.com/search/docs/monitor-debug/google-analytics-search-console
- Google Search Central, managing multi-regional and multilingual sites, documentation page consulted 10 October 2025, https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites