Multilingual SEO for Arabic and English Websites

Multilingual SEO for Arabic and English websites means giving each language version its own crawlable URL, telling Google how the versions relate with hreflang annotations, keeping canonical tags pointed at each version's own URL, and writing Arabic content based on how Arabic speakers actually search rather than translating the English word for word. Get the structure right and both versions can rank in their own right; get it wrong and one version is often ignored or treated as a duplicate.

Step 1: Choose a URL structure

Each language needs distinct URLs. Google recommends against relying on cookies or browser settings to switch language on the same URL, because Googlebot will usually see only one version.

Option	Example	Pros	Cons
Subdirectories	example.ae/en/, example.ae/ar/	One domain builds authority for both; simple to manage	Needs a CMS that supports it cleanly
Subdomains	en.example.ae, ar.example.ae	Can be hosted separately	Often managed as separate sites in practice
Separate domains	example.com, example.ae	Clear separation by market	More to maintain and promote
URL parameters	example.ae/?lang=ar	Easy to bolt on	Not recommended by Google; easy to get wrong

For most UAE businesses serving both languages in the same market, subdirectories are the simplest and most robust choice.

Arabic or English slugs?

Arabic characters in URLs work, but they are percent-encoded when copied and shared, producing long strings of symbols. Many sites use English or transliterated slugs for both versions, such as /ar/services/seo, with Arabic titles and content. Either can work; choose one convention and apply it consistently.

Step 2: Implement hreflang correctly

hreflang tells Google which URLs are equivalent pages in different languages, so it can show the right one to the right searcher.

For a page with Arabic and English versions, each version includes the same set of annotations in its <head>:

<link rel="alternate" hreflang="en" href="https://example.ae/en/services/seo" />
<link rel="alternate" hreflang="ar" href="https://example.ae/ar/services/seo" />
<link rel="alternate" hreflang="x-default" href="https://example.ae/en/services/seo" />

The rules that most often trip sites up:

• Return links are required. If the English page points to the Arabic page, the Arabic page must point back. One-way annotations may be ignored.
• Include a self-reference. Each page lists itself as well as its alternates.
• Use valid codes. The language comes first in ISO 639-1 format (ar, en), optionally followed by a region in ISO 3166-1 alpha-2 format (ar-AE). There is no "uae" code, and the region alone is not valid.
• Use full, live URLs. Point to the final indexable URL, not to redirects or URLs carrying noindex.
• x-default is optional and indicates the fallback for users whose language you do not target.

hreflang can also be supplied in XML sitemaps or HTTP headers, which is often easier on large sites. Pick one method.

Step 3: Keep canonicals language-specific

Each language version should have a canonical tag pointing to itself. Pointing the Arabic page's canonical to the English page tells Google the Arabic version is a duplicate to be ignored — one of the most common mistakes on bilingual sites.

Step 4: Get the technical presentation right

• Set lang="ar" and dir="rtl" on the Arabic pages so browsers and assistive technology render and read them correctly.
• Mirror the layout for right-to-left reading: navigation, icons with direction (arrows, progress steps), and form fields.
• Choose web fonts that render Arabic well and test them on mobile; fallback fonts can look broken.
• Translate everything Google reads: title tags, meta descriptions, headings, image alt text, structured data text fields, and button labels.

Step 5: Localise the content

Research Arabic search terms separately

Arabic searchers may phrase things differently and use different terms from those a translator would choose. Run separate keyword research for UAE search intent in Arabic, ideally with a native speaker who knows your sector.

Write for the reader, not the dictionary

Machine or literal translation produces text that is technically correct but stiff. Transcreation — adapting the message, examples and calls to action for the audience — reads better and converts better. Decide on a register (Modern Standard Arabic is the usual choice for business websites) and apply it consistently.

Keep both versions equivalent

If the English service page is updated, update the Arabic one too. Mismatched versions confuse users and weaken the pairing. Our guide to bilingual marketing in the UAE covers keeping messaging aligned beyond the website.

Step 6: Help users switch, but do not force them

Provide a visible language switcher that links to the equivalent page in the other language, not the homepage. Avoid automatically redirecting visitors based on IP address or browser language: it can stop users reaching the version they want, and Googlebot — which mostly crawls from the United States — may never see the Arabic pages.

How to check it is working

• Use the URL Inspection tool in Search Console on an Arabic URL to confirm it is indexed and that Google selected its own URL as canonical.
• Crawl the site with an SEO tool that validates hreflang return links and codes.
• In the Performance report, filter by page path (/ar/) to watch Arabic clicks and impressions separately.

Key takeaways

• Give each language its own URL; subdirectories suit most UAE businesses.
• hreflang needs return links, self-references, valid codes and live URLs.
• Each version is self-canonical — never canonicalise Arabic to English.
• Handle RTL properly and translate all metadata, not just body text.
• Research and write Arabic content natively, and never force-redirect by location.

If you are planning or repairing a bilingual site, Wot Digital's multilingual SEO services cover structure, hreflang and Arabic content, with website builds available through Wot Innovation.