Mixed Arabic and English queries
Arabic and English inside one search. Common for products, brands and areas. Usually invisible to anyone building the list from an English source.
SEO Specialisms · Arabic
Arabic search behaviour, spelling variants, dialect against Modern Standard Arabic, right to left rendering, hreflang for ar-AE, and why translated English pages consistently underperform.
Arabic SEO in Dubai is the work of ranking for searches made in Arabic, and it is genuinely a separate discipline rather than the English programme with translation added. The keyword research differs, the writing differs, the technical declarations differ, and the competitive field is usually far less crowded, which is the opportunity.
Most bilingual UAE websites have Arabic pages and very little Arabic search visibility. The reason is almost always the same: the Arabic pages were translated from English rather than written in Arabic, so they contain the dictionary equivalents of English phrases rather than the words Arabic speakers type. The pages exist, they are indexed, and they match very few real queries.
This page covers what Arabic SEO in Dubai actually involves: how Arabic search behaves, the spelling and dialect questions, the technical side of declaring a bilingual site, and how to judge whether the Arabic half of your site is working.
Behaviour
Four patterns that make translated keyword lists close to useless.
Code switching. Arabic SEO in Dubai has to account for this first: Arabic speakers here mix languages inside a single query routinely. A search may carry an Arabic verb with an English product name, or an Arabic service term with an English area name, because the English word is simply the one in common use. A keyword list produced by translating English terms contains none of these, and they are frequently the highest volume variants.
Transliteration. Brand names, place names and technical terms are often typed in Arabic letters approximating the English sound, and there is rarely one accepted spelling. The same district or company can be written several ways, each with real search volume, and the research has to find them rather than assume one.
Spelling variation. Arabic has genuine orthographic variation that people use inconsistently: the forms of alif, the ending ta marbuta against ha, and the final ya against alif maqsura. Search engines normalise some of this some of the time. Relying on that is a risk, and the practical approach is to know which variants your audience uses.
Diacritics. Short vowel marks are almost never typed in everyday search, so content written with full diacritics can mismatch the way people actually query. Arabic SEO in Dubai generally means writing undiacritised prose, with marks used only where a word would otherwise be ambiguous.
The consequence of all four is that Arabic keyword research has to be done in Arabic, by someone who searches in Arabic, looking at what actually returns results. There is no shortcut through a translation tool.
Arabic and English inside one search. Common for products, brands and areas. Usually invisible to anyone building the list from an English source.
Transliterated names with no single agreed form. Each spelling is a separate query with its own volume, and ignoring the ones you did not think of costs traffic.
Alif forms, ta marbuta against ha, ya against alif maqsura. Partially normalised by search engines, inconsistently enough to matter for competitive terms.
The Gulf term and the Levantine or Egyptian term for the same thing can differ. A UAE audience searches differently from a wider Arabic speaking one.
Register
This question comes up in every Arabic SEO conversation in Dubai and the answer is less complicated than it sounds. Written business content is Modern Standard Arabic. It is the register of formal writing, it is what readers expect on a company website, and it is what most commercial searches are phrased in.
Dialect has its place and it is mostly not on service pages. Conversational and voice searches drift toward spoken forms, social content often reads better in dialect, and customer support conversations certainly do. Where dialect matters for search is in the research: the spoken term for a service is sometimes what people type, and standard Arabic prose can still incorporate it naturally where it is the word in use.
There is a specific UAE consideration. A significant portion of the Arabic speaking audience here is not Emirati, and Gulf, Levantine, Egyptian and North African usage differ in ordinary vocabulary. Writing for the widest plausible reader, in standard Arabic, with terms chosen because research shows they are searched, holds up better than writing in one dialect.
The failure mode to avoid is inconsistency: a page that switches register between sections, or that reads as though parts were written by different people with different assumptions. That is a common symptom of Arabic content assembled from mixed sources, and it reads as carelessness to a native speaker.
Writing
The single biggest determinant of whether Arabic SEO in Dubai works at all.
Arabic SEO in Dubai fails at this point more than any other. Translation converts sentences. What a page needs is the argument made again, in Arabic, for a reader whose expectations are not identical to the English reader’s. Those are different jobs and they produce visibly different pages.
Mechanically, translation carries English sentence structure into Arabic, which produces prose that is grammatical and slightly wrong. It also carries English keyword choices, so the page targets the translated term rather than the searched one. And it carries English content decisions: the sections an English reader expects, in the order an English reader expects them, which is not always what an Arabic reader wants first.
The workable method in Arabic SEO for Dubai is briefing rather than translating. The brief states what the page must achieve, who it is for, what it must cover, which Arabic terms research identified, and which claims are permitted. An Arabic writer then writes the page. The result is not a mirror of the English version and it should not be, though both must carry the same facts and the same offer.
This costs more than translation and it is the difference between Arabic pages that exist and Arabic pages that work. Where budget forces a choice, fewer pages written properly beats a full site translated, because a translated site that matches no queries generates nothing regardless of its size. Google’s helpful content guidance is explicit that content produced primarily for search engines, including automated translation without human review, is the pattern to avoid.
Machine translation followed by light editing sits in an awkward middle. It is faster, and a reviewer who is genuinely rewriting rather than tidying can produce acceptable results. A reviewer who only corrects grammar leaves all the structural and keyword problems in place.
An Arabic writer works from a brief stating the purpose, the audience, the researched terms and the permitted claims. Produces pages that match real queries and read naturally.
Workable when the reviewer genuinely rewrites, including restructuring and replacing keyword choices. Not workable when the review is a grammar pass.
Produces indexed pages that match few searches and read as translated. The commonest reason a UAE site has Arabic pages and no Arabic traffic.
Declaring it
Once both versions exist, Arabic SEO in Dubai requires telling Google they are alternates of one another. Hreflang annotations do this, and getting them wrong means they are ignored entirely rather than partially applied.
The rules are strict and simple. Every page in a set lists every other version, including itself. The relationship must be reciprocal: if the English page names the Arabic page, the Arabic page must name the English page back, or the declaration is discarded. The set should carry an x-default for readers none of the entries fit.
Language and region are separate. The tag ar means Arabic for any Arabic speaker; ar-AE means Arabic for the United Arab Emirates. Choosing between them is a real decision. If your business serves only the UAE, the regional tag targets more precisely. If you want reach across the Gulf and beyond, the broader tag serves better, and using the narrow one unnecessarily limits you.
Canonical tags must agree with the hreflang set. A common and damaging error is every language version carrying a canonical pointing at the English page, which tells Google the Arabic pages are duplicates that should not be indexed. Each version should be canonical to itself.
The URL structure is a separate choice: a subdirectory, a subdomain or a separate domain. For most Dubai businesses a subdirectory such as /ar/ is the practical answer, because it keeps everything on one domain and one authority profile. The implementation detail belongs with technical SEO.
Rendering
Arabic pages are not English pages mirrored, and the difference shows in the details nobody tests.
Setting the direction attribute is the start of Arabic SEO rendering work in Dubai rather than the whole job. The W3C guidance covers it properly, and the recurring problems are predictable.
Mixed direction text is the main one. An Arabic sentence containing an English brand name, a phone number or a URL involves the bidirectional algorithm deciding how to lay out the run, and the result is sometimes wrong in ways that are obvious to an Arabic reader and invisible to everyone else. Punctuation at the boundary between scripts is where it usually shows.
Forms are the second. Labels, placeholders, validation messages and error states all need translating and all need to sit correctly. Phone number fields are a frequent failure, because the field is often forced left to right while its label sits right to left, producing something that looks broken at the exact moment someone is trying to make an enquiry.
Layout elements that carry direction need flipping rather than translating: breadcrumb separators, carousel arrows, progress indicators, icons that imply forward motion. A back arrow pointing the wrong way is a small thing that signals the Arabic version was an afterthought.
Typography matters more than teams expect. Arabic needs a font with proper Arabic support, adequate line height for the script, and a size that reads comfortably, since Arabic set at the English size often reads small. Text in images is worse in Arabic than in English, because it cannot be indexed and frequently renders incorrectly.
The practical test is to have a native Arabic reader use the site on a phone, complete a form and submit it. Ten minutes of that finds more than any checklist.
English names, numbers and URLs inside Arabic sentences. Check the punctuation at every boundary, because that is where the bidirectional layout usually goes wrong.
Labels, placeholders, validation text, error states and the confirmation. Phone fields especially. Test by actually submitting, not by looking at the page.
Breadcrumbs, arrows, carousels, progress bars and any icon implying direction. These need mirroring, and they are the last thing anyone checks.
A proper Arabic font, generous line height, and a size that reads well. Never text inside images, which cannot be indexed and often renders badly.
Addresses
Arabic SEO in Dubai can use Arabic URLs, and they work. A URL containing Arabic characters is stored percent encoded, so it looks unreadable when copied into a document and displays correctly in the browser address bar. Both facts are true simultaneously and both matter.
The practical choice for most Dubai sites is transliterated Latin slugs under an Arabic directory, which keeps URLs portable and readable everywhere while the content and the directory make the language obvious. Arabic slugs are defensible where the audience is exclusively Arabic reading. What is not defensible is mixing the two approaches across one site.
Titles and descriptions have to be written in Arabic rather than converted, for the same reason the body does, and they need separate length testing. Arabic text occupies different width from English at the same character count, so a title that fits in English may truncate in Arabic and the reverse also happens.
Numerals deserve a decision. Arabic-Indic numerals and Western numerals are both used across the region, and the UAE commonly uses Western ones. Whichever you choose, apply it consistently, including inside prices, dates, phone numbers and any structured data.
Dates are a related trap. Where a page shows a publication or update date, consider whether the Hijri calendar is relevant to your audience, and at minimum make sure the Gregorian date is formatted in a way an Arabic reader expects rather than inheriting an English format.
Beyond the site
Search visibility in Arabic is not only a website question.
Arabic SEO in Dubai extends to your Google Business Profile, which can carry Arabic content, and for a business whose customers search in Arabic that is worth doing properly. The business description, the services and the replies to reviews can all be in Arabic, and a profile that answers an Arabic review in Arabic signals something to every subsequent reader.
Arabic language directories, association listings and trade publications exist and are markedly less contested than their English counterparts. Most UAE businesses pursue the English versions and ignore these entirely, which makes them one of the more accessible opportunities in Arabic SEO for Dubai. The general approach is the same as any off page work, conducted in Arabic.
Arabic SEO in Dubai has a distinct advantage with answer engines. Assistants asked a question in Arabic draw on a much smaller pool of quality Arabic source material than they would for the English equivalent, so a well written, clearly sourced Arabic page has a better chance of being used. This is an unusually open position and it will not stay open indefinitely.
The same applies within ordinary search. Arabic results for many UAE commercial queries are noticeably thinner than the English results for the same intent, with older pages and more translated content among them. A business that publishes genuinely good Arabic material competes against a weaker field than its English pages face.
Measuring
Report the two languages separately or the smaller one disappears inside the larger.
The most common reporting failure in Arabic SEO for Dubai is a single organic traffic figure. English usually dominates by volume, so Arabic performance, good or bad, is invisible in the total. Filter Search Console by the Arabic directory and report it as its own line from the start.
What to watch is the same set of measures applied separately: impressions and clicks for Arabic pages, the queries producing them, the pages receiving them, and enquiries attributed to Arabic sessions. That last one frequently surprises businesses, because Arabic traffic often converts at a different rate from English, sometimes considerably better, and nobody notices while the numbers are combined.
The query report is the most useful artefact here. It shows the actual Arabic phrasing bringing people to you, which is direct evidence about vocabulary and usually corrects assumptions made during research. Treat it as a continuing input to the content plan rather than a report.
One caution on expectations. Arabic pages typically take longer to establish than English equivalents on the same site, because there are fewer internal and external links pointing at them and the section is newer. Judging Arabic SEO in Dubai at three months, against an English section built over years, produces the wrong conclusion.
Filter by the Arabic directory. A combined organic figure hides everything that matters about the smaller language, in both directions.
The phrasing people actually use, which routinely differs from the research. The most valuable ongoing input to what gets written next.
Arabic traffic often converts differently from English. Without separating them you cannot tell, and the investment case stays a guess.
Working with us
We begin Arabic SEO in Dubai with research conducted in Arabic rather than translated from an English list. That produces the terms, the spelling variants and the mixed language queries that matter, and it usually reveals that the Arabic opportunity differs in shape from the English one rather than mirroring it.
From there we decide which pages genuinely warrant an Arabic version. Translating everything is rarely the right answer. The pages where Arabic searchers have real intent, typically the core services and the practical guidance, are worth writing properly, with the same page level discipline as the English versions; deep English material with no Arabic demand behind it is not.
Pages are written in Arabic by an Arabic writer from a brief, not translated. Where a brief requires an Arabic writer we do not currently have available, we say so rather than converting English copy and hoping. The facts, the offer and the claims stay identical across both languages; the structure and phrasing do not have to.
The technical work runs alongside: hreflang declared reciprocally, canonicals pointing correctly, direction and typography checked on real devices, forms tested end to end in Arabic. Then reporting is split by language from the first month so the Arabic investment can actually be judged.
Arabic SEO in Dubai works as a defined project for a set of pages, or inside an optional monthly retainer where content is continuous. You get a fixed written quote within 45 minutes during business hours, and everything produced is yours.
Research method
The tools are weaker than their English equivalents, so the method has to compensate.
Arabic SEO in Dubai runs into a practical problem early: keyword tools report Arabic volumes less reliably than English ones, spelling variants are often reported as separate terms with fragmented data, and mixed language queries frequently do not appear at all. The research therefore leans harder on direct observation than on exports.
Start from the autocomplete. Typing a root term in Arabic and reading the suggestions shows real query patterns, including the variants and mixed forms a tool will miss. Doing this from a UAE location matters, because suggestions are regional.
Read the results, not just the terms. For each candidate term, look at what actually ranks. If the Arabic results for a term are dominated by pages from other countries, or by content that clearly does not match commercial intent, that tells you the term is either low volume here or means something different from what you assumed.
Collect the variants deliberately. For every important term, write out the spelling variants, the transliterations and the mixed language forms, and check each. Volumes that look small individually often aggregate into something substantial, and a page can naturally accommodate several variants.
Mine your own data. If you already have any Arabic traffic, the Search Console query report is the most honest source available, because every row is a real search by a real person that already reached you. The same applies to the search terms report from any Arabic paid campaigns you have run.
Ask your team. Arabic speaking colleagues who deal with customers know the words customers use, including the ones nobody would find in a tool. This is unglamorous and it consistently produces terms the research missed.
Real query patterns including variants and mixed forms, observed from a UAE location. The most reliable starting point when tool data is thin.
If foreign pages or mismatched intent dominate the Arabic results, the term is not what you assumed. This check prevents writing pages nobody wanted.
Spellings, transliterations and mixed forms listed and checked individually. Small volumes that add up, and a single page can serve several of them.
Arabic speaking colleagues who talk to customers daily. They supply vocabulary no tool reports, and the check costs one conversation.
Scope
Translating an entire site is the default assumption and it is usually wrong. Arabic SEO in Dubai works better as a deliberate selection, because each Arabic page carries an ongoing maintenance cost and a page with no Arabic demand behind it earns nothing while still needing to be kept current.
The pages that almost always warrant Arabic are the core commercial ones: your main services, your contact and about pages, and anything a customer reads immediately before enquiring. These carry the intent, and an Arabic speaker who reaches an English only enquiry form is a lost enquiry.
Practical guidance content is the next tier and often the best performing, because Arabic results for genuinely useful explanatory material are thin across most UAE sectors. A clear Arabic explanation of a process your customers find confusing frequently outranks far larger competitors.
What rarely warrants Arabic is deep English material written for a specific English audience, technical documentation, and archive content. Translating these produces pages that are maintained forever and read by nobody.
One structural warning. Whatever you choose, the Arabic section must be navigable in Arabic. A partial translation where Arabic pages link into English ones, or where the menu reverts to English, breaks the experience and confuses the hreflang relationships. If a page is in the Arabic section, its internal links should point within it.
Common faults
The same handful of problems appear on almost every bilingual UAE site we audit.
Arabic SEO in Dubai is rarely a blank page. Most businesses already have an Arabic section, built at some point by someone, and the audit usually finds the same faults. Listing them is useful because several are quick to correct and produce movement without any new content at all.
Canonical tags pointing at the English page. This tells Google the Arabic pages are duplicates and should not be indexed, which is exactly what then happens. It is a single line fix per template and it is the most damaging fault on this list.
Hreflang declared in one direction only. English pages naming Arabic alternates, Arabic pages naming nothing. The annotation is discarded entirely, so the work of adding it was wasted.
An Arabic section that is partially English. The menu, the footer, the form labels or the error messages still in English. Common when the translation covered page bodies and nothing else, and it undermines the section at the point of enquiry.
Contact details out of date on the Arabic side only. The English pages get updated when a number changes and the Arabic ones are forgotten. Worth checking first because it costs enquiries directly.
Arabic pages orphaned. No internal links pointing at them from anywhere except a language switcher. They are technically present and effectively invisible, and fixing the internal linking within the Arabic section often produces the fastest result available.
Text inside images. Arabic headings and calls to action set as graphics because the original build could not render the font. Not indexable, not selectable, and usually not responsive either.
Canonicals pointing to self, reciprocal hreflang, corrected contact details, and internal links within the Arabic section. Template level changes with immediate effect.
Interface text, form labels, validation and error messages translated properly. Then titles and descriptions rewritten in Arabic rather than converted.
Text baked into images, layouts that mirror badly, and typography set at English sizes. These usually wait for a template change rather than being patched.
The opportunity
The competitive argument, which is usually stronger than businesses expect.
The case for investing here is not sentiment about serving the local language. It is that the field is thinner. For a great many UAE commercial queries, the English results are contested by well resourced national and international competitors, while the Arabic results for the same intent are fought over by a fraction of them.
The reason is structural. Most agencies operating here are stronger in English, most content budgets are spent in English first, and Arabic gets handled by translation at the end of a project when money is short. That produces a large volume of Arabic pages that match few queries, which is a weak field to enter.
The practical consequence is that the cost of a first page position in Arabic is frequently lower than the cost of the same position in English for the same service. A business that writes twenty genuinely good Arabic pages can find itself competing against translated content from much larger competitors, and winning.
Two things temper this. The Arabic query volume for any given term is usually smaller than the English volume, so a strong Arabic position may still deliver less traffic than a mediocre English one. And the audience differs: Arabic search skews toward different segments depending on the sector, so the enquiries arriving may not resemble the English ones in size or type.
Both are reasons to measure the two separately rather than reasons to skip Arabic. The businesses that do well here are generally the ones that treated Arabic as a distinct market with its own plan rather than as a translation line in a budget, and the window for that advantage is open now precisely because so few do.
There is a second order effect worth noting. Arabic SEO in Dubai tends to improve the English side as well, because doing the research properly in Arabic usually surfaces questions and phrasings that the English research missed. Customers asking something in Arabic are frequently asking it in English too, and the English page that answers it did not exist because nobody had looked. Several of the better performing English pages we have worked on started as an observation from Arabic query data.
The reverse is rarely true. English research translated into Arabic surfaces nothing new, which is another way of describing why the translation approach underperforms.
One last practical note on sequencing. If you are going to do this, start with a small set of pages and measure properly for a quarter before committing to a full Arabic section. That gives you real data about Arabic demand in your specific sector rather than a general argument, and it costs a fraction of a full translation programme. If the numbers support it, expand from evidence. If they do not, you have learned that for the price of a handful of pages rather than the price of a site.
Fewer competitors writing genuinely good Arabic content, because most budgets go to English first and Arabic is handled by translation at the end.
A well written Arabic page frequently outranks translated content from much larger competitors, which is rarely true of its English counterpart.
Arabic query volume is usually below the English equivalent, so judge the return on enquiries rather than on position or traffic alone.
Arabic searchers may differ from English ones in segment, budget and intent. Worth understanding rather than assuming the two behave identically.
If your customers do not search in Arabic, Arabic SEO in Dubai will not earn its cost. Some sectors in the UAE are conducted almost entirely in English, particularly in business to business technology and parts of professional services. Check the Arabic search volume for your core terms before committing, because the honest answer is sometimes that there is very little.
If nobody in your business reads Arabic, publishing Arabic content creates an unmanageable position. Someone has to approve copy, answer Arabic enquiries and reply to Arabic reviews. A site that attracts Arabic enquiries nobody can answer is worse than one that never attracted them.
If your English site has significant unresolved problems, fix those first. Arabic pages built on a site with unresolved technical faults inherit every one of them, and you will have doubled the content on a broken foundation.
And if the budget only covers translation, consider fewer pages written properly instead. Ten Arabic pages that match real queries outperform eighty translated ones that match none, and they cost less to maintain.
If you are unsure whether there is genuine Arabic demand for what you do, tell us your core services and we will look at the Arabic search landscape and tell you plainly, including when the answer is that it is not worth it yet. Our team works in Arabic and English with businesses across Dubai and the wider UAE, and a fixed written proposal follows within 45 minutes during business hours with no obligation.
Straight answers
You can, and it usually underperforms. Translation gives you the dictionary equivalent of English phrasing rather than the words Arabic speakers actually search, and a native reader can tell within a paragraph that a page was translated. Pages written in Arabic from a brief, by an Arabic writer, perform differently.
Written content is generally Modern Standard Arabic, because that is what people read and what most formal search queries use. Dialect appears in conversational searches and in social content. The practical answer for most UAE sites is standard Arabic prose that accounts for dialect terms in the keyword research.
Yes, always. Translating an English keyword list produces terms with little or no search volume. Arabic searchers also mix Arabic and English in one query and use transliterated brand and place names, and none of that appears in a translated list.
Partly, and not reliably enough to ignore. Common variants such as the different forms of alif and the ending letters ta marbuta and ha are often treated as equivalent, but coverage varies by query. Research should look at the variants your audience actually types rather than assuming they are normalised.
Hreflang tells Google that your Arabic and English pages are alternate versions of each other and which audience each serves. Without it the versions can compete or the wrong one can be shown. If you publish in both languages you need it, and it must be reciprocal on every page.
Sources
Fixed price, in writing
Got it. Your quote is being written now.
In business hours you will have it within 45 minutes. Check your inbox for the confirmation.