Search
How to rank an Arabic website in Qatar: what works
Translating your English pages into Arabic will not rank them. Arabic SEO is a different keyword set, a different page structure and a different layout — here is what it looked like on a real Doha site, with the numbers.
- Written by
- Hosam Hammad
- Published
- 2 July 2026
- Updated
- 24 September 2026
- Reading time
- 9 minutes
01 · The mistake
Translating the English site does not create Arabic SEO
The standard approach is to finish the English site, hand it to a translator, and publish the output under /ar. The result reads correctly and ranks for nothing, because the Arabic pages target the Arabic wording of English keywords, which is not what anybody types. Search intent is not a language you can convert; it is a set of questions that differ by market.
Here is the test. Take the English keyword your service page targets, translate it word for word, and put the translation into Google from a phone in Doha. Then look at the suggestions that drop down before you press enter. On almost every business CoreThree has done this for, the suggestions are not the translation. They are shorter, they name a material or a place rather than a service, and they often mix an English word into the Arabic. Those suggestions are the real keyword list. The translation is a sentence nobody searches.
That is why most bilingual sites in Qatar have an Arabic half that Google indexes and never shows: every page on it answers a question that was asked in English.
02 · The evidence
Arabic and English customers search for different things
In our own client data the Arabic queries skew heavily towards immediate, local, transactional phrasing, while the English equivalents for the same business are more comparative and research-led. Those two intents want different pages, different headings and different calls to action, not the same page in two fonts.
A real example, from a stone-cladding contractor in Doha we work with. The English buyer types "stone cladding contractors doha": a service, a role, a city. The Arabic buyer does not type the Arabic for that. The Arabic buyer types حجر سوري, حجر عماني or حجر اردني — Syrian stone, Omani stone, Jordanian stone. A material, not a service. They know what they want on the wall and are looking for who sells it. Over one month in autumn 2026, the four Syrian-stone phrasings alone put the site in front of Arabic searchers about 256 times, and "Omani stone" went from 32 impressions to 114 in the month after we wrote to it.
The English pages on the same site are service pages, and they rank for service queries. The Arabic pages that earn clicks are material guides: Syrian versus Jordanian stone, what Omani stone costs, which finish suits a facade. The single most-clicked page on that site in September 2026 was the Arabic guide comparing Syrian and Jordanian stone, with 692 impressions and 13 clicks, ahead of the English home page. Nobody would have written it by translating the English service pages, because there is no English page it corresponds to.
03 · Structure
Each language needs its own URL and hreflang tag
That means a distinct, crawlable URL per language, paired with hreflang so search engines understand they are two versions of one thing rather than duplicates competing with each other. A language switcher that swaps text on the same URL gives you one page in the index, and it will be the English one.
Three details decide whether the pairing works. First, every Arabic page declares its English twin and every English page declares its Arabic twin; a one-way link is ignored. Second, each page's canonical points at itself, not at the English version, or you have just told Google the Arabic page is a copy. Third, the titles and descriptions are written per language for that language's query, because Google shows the Arabic title to Arabic searchers and will not translate the English one for you.
When the pairing is right, the two versions stop competing and start helping each other: the Arabic page can rank for the material query and the English page for the service query, and Google treats the domain as one business with two audiences. When it is wrong, the usual symptom is that the Arabic page ranks for an English query it should never see, or not at all.
04 · Design
Right-to-left affects layout, not just text
Arabic mirrors the whole reading order: navigation, form fields, icons that imply direction, the side an image sits on. Retrofitting that onto a finished left-to-right layout produces the uncanny result most bilingual sites in the region have: technically Arabic, obviously an afterthought. Designing both directions from the first layout costs almost nothing extra; converting later costs a rebuild.
It also affects speed, which affects rankings. Arabic web fonts are heavier than Latin ones, and a site that loads its Arabic face for every visitor, or loads the wrong one and lets the browser substitute, pays for it on a phone in Doha on mobile data. The fix is a per-language font budget: one Arabic face, loaded only on Arabic pages, with a fallback that does not reflow the page when it arrives. On the contractor's site above, the Arabic pages load with the same speed score as the English ones, which is the reason they can rank at all.
And it affects the Arabic itself. Arabic is never letter-spaced tight, numbers inside Arabic sentences need care so they do not flip, and a heading that was written to fit two lines in English will run to four in Arabic unless someone writes it for Arabic. None of this is exotic. It is the difference between a site built in two languages and a site translated into one.
05 · Measuring
Report Arabic and English traffic separately
Merged reporting hides the thing you need to know: which language is actually bringing in business. Split rankings, traffic and enquiries by locale from day one. In more than one case the Arabic side turned out to be the one paying for the project.
The contractor above is one of those cases. In the month to 19 September 2026, Arabic queries held the top three positions for حجر السوري, حجر سوريا and انواع الحجر السوري, Google's Arabic AI answer for حجر سوري قطر was built from the site's own pages, and the Arabic home page drew more impressions than the English one. If the report had shown one traffic number, the owner would have credited the English site, because that is the one he reads.
Split reporting also tells you what to write next. When an Arabic term shows hundreds of impressions and a handful of clicks, the page ranks and the snippet does not persuade: fix the Arabic title. When a term shows impressions on a page that was never written for it, that is a page waiting to be written. Both are invisible in a merged view.
06 · Checklist
What to do this month, in order
Run the suggestion test on your five most important pages, in Arabic, from a phone. Write down what Google suggests; that is your list.
Check one Arabic page in Google Search Console. If it has impressions on English queries, or none at all, the hreflang pairing is wrong and nothing else matters until it is fixed.
Rewrite the Arabic title and description of your busiest service page for the query people actually type, not the translation. Titles change fastest and cost nothing.
Write one Arabic page that has no English twin: the material, the price question or the comparison your Arabic customers search for. On the site above, that page is now the most-read page on the whole site.
Split your report. Rankings, impressions and enquiries per language, side by side, every month. If you do not know which language brought last month's enquiries, you cannot decide where to spend next month.
