Multilingual SEO makes sure each language version of your website is found by the people who search in that language. Translating pages is only the first step. Search engines need to see each version clearly, understand which audience it serves and choose the right one for each searcher, and your content needs to match how people actually search in Arabic, English or any other language you publish in.
Most problems on bilingual UAE sites are structural rather than editorial: translations hidden behind scripts, missing or broken hreflang, canonical tags pointing the wrong way or Arabic metadata copied from English. Search is planned as part of our web design process, alongside the multilingual UX that governs how languages are presented. This guide covers the technical setup first, then the content and measurement work that makes each language earn its visibility.
Give every language its own indexable URL
Search engines index URLs, not language toggles. If your Arabic content appears only after a visitor clicks a switcher that rewrites text with JavaScript on the same URL, it is unlikely to rank. Each language version needs a distinct, crawlable address.
- Subdirectories such as /ar/ and /en/ are the usual choice. They share one domain’s authority and are simple to manage.
- Subdomains or country domains work too, but each builds authority more independently.
- URL parameters are supported by some systems but make targeting and reporting harder.
Link the language versions to each other with normal HTML links in the switcher, so crawlers can discover them. Avoid automatic redirects based on browser language or IP address; search engine crawlers typically request pages without a language preference, and a forced redirect can stop them from ever seeing one version. A suggestion banner is a safer way to guide users.
Multilingual SEO signals: hreflang and canonicals
Hreflang annotations tell search engines that a set of pages are equivalents in different languages, so the right one appears for each searcher. They are the most error-prone part of multilingual SEO.
Rules for correct hreflang
- Self-reference: each page lists itself as well as its alternates.
- Reciprocity: if the English page points to the Arabic page, the Arabic page must point back. One-way annotations are ignored.
- Valid codes: use ISO language codes, optionally with a region, such as ar, en, ar-AE or en-AE. A region alone, such as AE, is invalid.
- x-default: point it at the page for users whose language you do not specifically serve, often the English version or a language selector.
- Indexable targets: every URL in the set must return a 200 status and be indexable, not redirected or blocked.
Hreflang can be placed in the page head, in HTTP headers or in the XML sitemap. On WordPress, translation plugins generate it automatically, but check the output on a sample of pages, especially after adding new templates or custom post types.
Canonical tags
Each language version should carry a self-referencing canonical. A common mistake is canonicalizing the Arabic page to the English one, which tells search engines to ignore the Arabic version entirely. Translations are not duplicates, and should not be treated as such.
Language declaration
Set the lang attribute in the HTML element, with dir=”rtl” on Arabic pages. Google determines language mainly from visible content, but other search engines, browsers and screen readers rely on these attributes. Keep each page in one primary language; pages mixing large blocks of two languages send unclear signals.
Research keywords in each language, not through translation
Translated keywords often miss how people really search. An English term and its literal Arabic translation may have very different search demand, and the phrase people actually use may be something else entirely.
| Consideration | What to check |
|---|---|
| Formal and everyday Arabic | Whether searchers use Modern Standard Arabic terms or more colloquial Gulf phrasing for your service |
| English loanwords | Many technical and commercial terms are searched in English or transliterated even by Arabic speakers |
| Spelling variants | Different letter forms and spellings of the same Arabic word |
| Local modifiers | City and area names in both scripts, such as Dubai, دبي, Abu Dhabi and أبوظبي |
| Search intent | Whether the results show services, guides or directories, which should shape the page type |
Use keyword tools that support Arabic and the UAE market, and look at the actual search results for each candidate term. Mapping a keyword to a page should happen separately for each language, so the Arabic services page targets the Arabic phrases people use rather than a translation of its English counterpart’s target.
Localize content and metadata
Once keywords are mapped, the content itself must satisfy searchers in each language.
- Titles and descriptions: write them fresh for each language. Arabic titles can be longer in characters but display differently in results, so review how they appear.
- Headings and body copy: adapt examples, units and references to the audience rather than translating sentence by sentence.
- Slugs: choose consistently between translated Arabic slugs and transliterated or English slugs, and keep them short.
- Images: translate alt text and file names where practical, and create language versions of images that contain text.
- Structured data: translate the text within schema markup, such as Organization, Service and FAQ content, and keep it consistent with visible content.
Content parity matters too. A thin Arabic version with half the detail of the English page will struggle to rank against competitors who give Arabic readers full information.
Internal links, sitemaps and local signals
Internal links should stay within the same language wherever possible. An Arabic article that links to English service pages sends users and signals across languages and weakens the Arabic section’s structure. Check menus, footers, related posts and breadcrumbs on every language version.
Submit an XML sitemap that includes all language versions, with hreflang in the sitemap if that is where you manage it. In Google Search Console, verify the whole domain and use page filters, such as URLs containing /ar/, to track each language separately. For local visibility, keep your business name, address and phone number consistent across both languages on the site, and make sure your Google Business Profile links to the most relevant language version for your main audience.
AI assistants and answer engines
AI assistants increasingly answer questions in the user’s language, drawing on pages they can crawl and understand. Clear, well-structured content in each language, with direct answers near the top of pages and accurate structured data, gives these systems reliable material to cite. The same fundamentals that support multilingual SEO support this visibility too.
Measure each language separately
Reporting on a bilingual site as a single total hides problems. Track organic sessions, impressions, clicks and conversions for each language folder. In Google Analytics 4, segment by page path or by a language dimension, and record form submissions and WhatsApp clicks with the page language attached. Search Console no longer offers a dedicated hreflang report, so crawl the site with a tool that validates hreflang, such as Screaming Frog, after major changes.
Frequently asked questions
Is hreflang required for a bilingual website?
It is not mandatory, but it is strongly recommended. Without hreflang, search engines may show the English page to Arabic searchers or treat the versions as competing pages. Correct, reciprocal hreflang annotations help each version appear for the right audience, and major WordPress translation plugins can generate them automatically once configured.
Should I target ar-AE or just ar in hreflang?
Use a language-only code such as ar when the content serves Arabic speakers everywhere. Add a region, such as ar-AE, only when you have genuinely different versions for different countries, for example separate UAE and Saudi pages with different pricing or services. Most UAE businesses with one Arabic version are well served by the language-only code.
Can I translate my English keywords into Arabic?
Translation is a starting point for ideas, not a keyword strategy. Arabic searchers may use different terms, English loanwords, transliterations or colloquial phrasing. Research each language independently with tools that support Arabic and check the live search results, then map the phrases people actually use to your Arabic pages.
Will automatic language redirects hurt my SEO?
They can. Crawlers often visit without a language preference, so automatic redirects based on browser settings or location may prevent some versions from being crawled and indexed. Let users choose their language, remember their choice with a cookie, and use a non-blocking banner to suggest a better match rather than forcing a redirect.
Visibility in every language you serve
Good multilingual search performance rests on clear structure, correct hreflang and canonicals, keyword research carried out in each language and content that serves each audience fully. With those in place, each language version can build its own visibility on Google, Maps and AI assistants, and bring in inquiries from audiences an English-only site would miss.
If you would like an assessment of how your multilingual site is set up for search, we would be glad to review it with you.
