Two languages, two sets of answers
Ask an AI assistant in English for a paediatrician in Al Barsha and it draws mostly on English pages. Ask the same question in Arabic and it leans towards Arabic pages, Arabic directory listings and Arabic reviews. The two answers often name different clinics.
For a clinic in the UAE, that means an English-only website competes for one set of answers and is at a disadvantage in the other. How much that matters depends on who the clinic's patients are.
When Arabic pages are worth it
- A meaningful share of patients are Emirati or from other Arab countries.
- The clinic has Arabic-speaking doctors, which is itself something patients ask for.
- The specialty is family-oriented, such as paediatrics, obstetrics, gynaecology or family medicine, where the person searching is often a parent asking in their first language.
- The clinic is outside the most international areas, or serves patients from other emirates.
If none of these apply, Arabic pages are a lower priority than getting the English pages, doctor profiles and Google profile right first.
Which pages first
- Specialty pages for the clinic's main services.
- Doctor profiles, especially for Arabic-speaking doctors, stating that they speak Arabic.
- Insurance accepted, since insurer names are a common part of patient questions.
- Location and hours, with the area and landmarks named in Arabic as patients would say them.
- The FAQ blocks on each of the above.
A full Arabic mirror of every blog post is not necessary at the start. The pages patients act on come first.
How to do it properly
Write, do not machine-translate. Machine translation of medical content produces stiff, sometimes wrong Arabic that patients notice immediately. A native speaker with healthcare familiarity should write or at least edit every page.
Use separate pages, not a toggle that swaps text. Each Arabic page should have its own address, for example /ar/ followed by the page name, so crawlers can find and index it.
Tag the languages. Use hreflang tags so engines know the English and Arabic pages are versions of each other, and set the page language and right-to-left direction correctly.
Keep facts identical. Same prices, same doctors, same insurers, same hours. A mismatch between language versions confuses engines and patients alike.
Match the Google profile. Add the Arabic business name if the clinic uses one, and reply to Arabic reviews in Arabic.
A quick way to decide
Ask three patient questions for your specialty and area in Arabic in ChatGPT and Gemini. If competitors are named and you are not, and you serve Arabic-speaking patients, the Arabic pages are worth building now.
Want to see where your business stands?
The AI Visibility Audit tests 50 real buyer questions across ChatGPT, Claude, Gemini, Perplexity and Google AI Overviews and shows who is being recommended instead of you. AED 1,999, credited against any program within 30 days.
Order the auditFrequently asked
Do AI engines answer Arabic questions from Arabic sources?
They tend to lean on sources in the language of the question, so an English-only clinic is named less often, and with fewer details, in Arabic answers.
Which clinic pages should be translated into Arabic first?
Specialty pages, doctor profiles, insurance accepted, location and hours, and the FAQ blocks on each.
Is machine translation acceptable for clinic pages?
Not for medical content. A native Arabic speaker with healthcare familiarity should write or edit each page.
How should Arabic pages be set up technically?
As separate pages with their own addresses, hreflang tags linking language versions, correct language and right-to-left settings, and identical facts to the English versions.