Most GEO programmes we see in this market are English-only. The strategy deck is in English. The blog is in English. The FAQ schema is in English. Then the founder is surprised when an Arabic ChatGPT session names a local competitor and not them.
UAE search is not a monolingual habit. People switch. They ask Google in English at work and ask an AI the same question in Arabic at night. They paste a mix of both into Perplexity. If your entity only exists in one language, you have handed the other half of the conversation to whoever bothered to write Modern Standard Arabic that a model can quote.
This piece sits next to our GEO vs SEO vs AEO explainer. That one covers the three layers. This one is the GCC-specific gap: bilingual is the actual lever, not a translation afterthought.
What "Arabic GEO" is not
It is not stuffing Arabic keywords into an English page. Models are not that easily fooled, and readers bounce.
It is not a raw machine dump of your English blog. Hallucinated terminology, mixed dialect, and broken RTL are worse than staying in English. We will not publish Arabic on this site until a native reviewer has read it. That rule exists because we have seen what shipping unreviewed MSA does to trust.
It is not a separate brand. Name, services, city, and proof have to match across languages or you look like two companies. Inconsistent NAP in English and Arabic is how you become un-citable.
Why English-only leaves money on the table
Retrieval-based tools, Google's AI features included, need a page they can ground in. If the Arabic query has no Arabic page with a clear answer, the system will still answer. It will just ground in someone else, or in a generic global source that has never worked a Dubai procurement cycle.
Voice and WhatsApp add another layer. A lot of Gulf customer questions never become a Google keyword. They become a spoken or typed Arabic sentence. AEO-style pages in MSA, short direct answers, FAQ format, are how you get into that stream. English FAQs do not get read aloud in Arabic.
KSA, Qatar, and the rest of the GCC are a bonus, not the brief. The primary job is local UAE visibility. Arabic pages that already work in the UAE travel into those markets more honestly than English pages "localised" with a flag.
What to translate first (and what to leave)
Do not start with the whole archive. Start with the pages a buyer asks an AI about.
Service pages: what you do, who it is for, what it costs in rough bands, how to start. If `/services` only exists in English, that is the first hole.
The five to ten questions from your GEO list, in the wording sales actually hears in Arabic. Not the wording a keyword tool invented.
Proof: project names, cities, industries. Models look for entities they can attach to a place. "Dubai," "Abu Dhabi," a named vertical, a real artefact like a portal or an audit tool, those travel across languages if you keep the proper nouns stable.
Leave the thin posts. A mediocre English article becomes a mediocre Arabic one, and now you have twice the pages Google has to decide are commodity. Google's own generative-AI guidance still prefers unique, people-first content over scaled rewrites. That applies twice when you duplicate a language.
Practical rules we use
One URL per language, with proper `hreflang`, not a toggle that rewrites the same URL. RTL has to be real: layout, numerals, and forms, not a CSS flip that breaks the contact page.
Same `scheduledFor` on English and Arabic when both exist, so one language does not index a week before the other and confuse the pair. That is how this site's drip is built.
Entity facts copied, not paraphrased, for the things that must match: legal name, phone, city, service names you want associated with the brand. You can write the surrounding explanation like a human. You cannot have two versions of the phone number.
A native pass before publish. Always. Dialect vs MSA is a judgment call. For this site we use MSA on purpose, because search and AI citation prefer it over Gulf dialect for commercial pages. Customer support scripts are a different document.
Skip `llms.txt` as the Arabic strategy. Google has said it does not treat those files as special for AI features. A bilingual service page beats a robots poem.
How this connects to the rest of the work
GEO without SEO is still a slogan. Arabic pages have to be crawlable, fast, and internally linked like the English ones. The AI adoption and services cluster only helps if both languages point at the same offers.
If you are choosing a partner, ask to see an Arabic page they shipped, not a slide about "MENA coverage." Ask who reviewed it. If the answer is "the model," keep walking.
We will add an Arabic version of this post after that native review, not before. Until then, the honest English version is better than a fluent-looking mistake.
Frequently asked questions
Should we write Gulf dialect or Modern Standard Arabic?
For pages you want cited and ranked, MSA. Dialect belongs in support macros and ads where you are talking, not in the canonical explainer a model will quote.
Can we machine-translate and then lightly edit?
You can, as a draft. You should not publish that draft. Light edits miss terminology, legal phrasing, and the sentences that sound like a model wrote them in the wrong direction. Budget for a native reviewer as part of the page, not as a nice-to-have.
Will Arabic pages hurt our English rankings?
Not if they are proper alternates with `hreflang` and unique URLs. They hurt you when they are doorway pages or duplicate English with a few swapped words.
How do we get started?
List the ten questions buyers already ask in Arabic, even if they currently get an English answer. Write those ten properly. If you want a partner on the bilingual cluster, email team@ins.ae or WhatsApp +971 58 995 4553. Arabic copy still goes through a native reviewer before it ships.
