Arabic and English Website SEO in the UAE: A Checklist Beyond Translation

Good bilingual SEO gives an Arabic reader and an English reader the same quality of experience, each in their own language, on pages a search engine can find and tell apart. That is the short answer. Translation is only one part of it. The bigger job is making two complete, equivalent versions of your site, linking them correctly, and checking that the Arabic version actually reads and works the way an Arabic speaker expects.

If you only translate the words and leave the structure, layout and links as they were, you tend to get thin Arabic pages, confused navigation, and search engines that cannot decide which version to show to whom. This guide walks through what to do instead, with a page-pair checklist you can run before anything goes live.

Translation is one task; equivalence is the goal

A translated page copies the sentences. An equivalent page delivers the same value: the same service explained clearly, the same proof, the same prices and scope, the same ways to enquire, all expressed naturally in the second language.

The difference shows up quickly. A machine-translated English service page might render an Arabic form with its labels in the wrong reading order, leave button text in English, keep an English-only PDF, or translate a marketing phrase so literally that it reads oddly. None of that is "wrong translation" exactly. It is an incomplete experience, and both readers and search engines notice.

Aim for parity on these points for every page you publish in two languages:

• The same core information is present in both versions, not a shortened Arabic stub.
• Enquiry routes work in both: the form, the WhatsApp handoff, the phone link.
• Prices, packages and service scope match across languages so nobody gets a different answer by switching.
• Images that contain text, such as a price graphic, have a version a reader of that language can understand.
• The tone reads as if written in that language, which is why Arabic copy needs a native review, not just a pass through a translation tool.

Give each language a stable, separate URL

Search engines handle two languages best when each version lives at its own consistent address and stays there. The common patterns are a subdirectory (/ar/ and /en/), a subdomain, or a separate domain. For most UAE small and medium businesses a subdirectory on one domain is the simplest to run and keep tidy.

Whatever you choose, keep three rules:

1. Each language version has its own URL that does not change every time someone switches language.
2. The URL for a page stays the same over time, so links and search results keep working.
3. A language switch takes the reader to the matching page, not back to the homepage every time.

That last point matters more than people expect. If a reader is on your Arabic air-conditioning service page and taps "English", they should land on the English air-conditioning service page, not the English homepage. Sending every switch to the homepage quietly tells readers and crawlers that the two versions are not really paired.

Self-canonical, not cross-language canonical

A canonical tag tells a search engine which URL is the preferred version of a page. A frequent and damaging mistake is pointing the Arabic page's canonical at the English page. That asks the search engine to treat the English URL as the real one and can keep the Arabic page out of results entirely.

The correct setup is simple: each language version canonicalises to itself. The Arabic page is its own canonical; the English page is its own canonical. They are different pages for different readers, so each is preferred for its own audience.

Link the versions to each other correctly

Once each page has a stable self-canonical URL, you connect the pair so search engines understand they are language alternates of one another. Google's own documentation describes using language annotations where each version lists all the versions, including itself, as reciprocal alternates. Reciprocal means every page in the set points to every other page in the set, and back to itself.

Here is a small, correct example for one page that exists in UAE English and Arabic. The values are illustrative and the Arabic wording needs native review before use.

The important property is symmetry. If the English page claims the Arabic page as its Arabic alternate, the Arabic page must claim the English page back. One-directional links are a common reason these annotations are ignored.

A note on expectations: this markup helps a search engine serve the right language version to the right person. It is not a ranking boost, and it does not tell Google what language a page is written in. Google determines language from the visible content. Correct content in the intended language comes first; the annotation just helps pair and serve the versions.

Right-to-left is a usability job, not a stylesheet flip

Arabic reads right to left, and real RTL support is more than reversing the text direction. If the Arabic version is an afterthought, readers hit small, awkward problems that make the page feel untrustworthy even when the translation is fine.

Walk an actual Arabic page on a phone and check each of these:

• Layout direction: the page uses a right-to-left layout so headings, lists and navigation sit where an Arabic reader expects, not mirrored oddly.
• Forms: field labels, placeholders and the submit button read correctly, and typing Arabic into the fields behaves normally.
• Numbers and dates: you decide consistently how numerals, phone numbers and prices appear, and they stay readable and correct.
• Mixed content: an English brand name or product code inside Arabic text does not break the line flow.
• Fonts: the Arabic typeface is legible at real sizes, with sensible line height; a font chosen for Latin text alone often looks cramped in Arabic.
• Images with text: captions, badges and price graphics have an Arabic version rather than leftover English.
• Mobile controls: the language switch, menu and buttons are reachable and tappable with one thumb.

None of this needs a perfect rank to matter. It is the difference between a page an Arabic customer trusts and one they bounce out of.

Write for intent, not literal keyword swaps

People do not search in translated phrases. An English searcher and an Arabic searcher looking for the same service often use different words, different word order, and sometimes a mix of Arabic and Latin script for brand or technical terms.

So do not translate your English keyword list word for word and drop the results into the Arabic page. Instead, decide what the reader wants from each page, then write naturally in each language to match how that audience actually asks. A few illustrative contrasts, all of which should be confirmed by a native Arabic speaker:

• A term that is one tidy phrase in English may be expressed two or three common ways in Arabic, so the page should read naturally rather than forcing one literal string.
• Some technical or brand terms are searched in Latin script even by Arabic speakers, so the Arabic page can sensibly include them as written.
• A direct translation of a marketing slogan can read awkwardly or change meaning, which is a content decision for a reviewer, not a find-and-replace.

Do not assume an Arabic keyword is automatically less competitive or easier to rank for. Competition depends on who else is targeting that intent, which you check, not guess.

Keep offers, prices and routing consistent across languages

Because customers switch languages mid-visit, any mismatch between versions becomes a trust problem. Before publishing a pair, confirm:

• Packages and scope read the same in both languages.
• Any price shown matches, and if you prefer to confirm pricing on enquiry, both versions say so the same way.
• The enquiry destination is consistent: a form submits to the same place, and a WhatsApp link opens the same number with a sensible prefilled message in the matching language.
• Contact details, hours and service areas are identical in substance.

If the English page lists a service area and the Arabic page omits it, you have created two different promises. Equivalence closes that gap.

Finish and review before you index

A half-finished translation that search engines can crawl is worse than no translation yet. Thin, duplicated or auto-translated pages can dilute your site and give readers a poor first impression in their own language.

A safer sequence:

1. Translate and have a native speaker review the content for accuracy, tone and intent.
2. Build the page with correct RTL layout, working forms and matching offers.
3. Set the self-canonical and the reciprocal language annotations.
4. Check the page on a phone and desktop in the target language.
5. Only then allow indexing. Until a version is ready, keep it out of the index rather than bulk-enabling every machine translation at once.

This keeps you from the trap of switching on dozens of unchecked Arabic pages overnight and then wondering why they neither rank nor convert.

A quick before and after on language routing

Consider a fictional Sharjah maintenance company that added an Arabic site. In the before state, every "Arabic" button on the English site pointed to /ar/ (the Arabic homepage), the Arabic service pages canonicalised to their English equivalents, and the alternate links were only set on the English pages. Arabic pages barely appeared in results, and visitors who switched languages lost their place.

In the after state, each English service page links to its own Arabic equivalent and back, each page canonicalises to itself, and the language switch preserves the page the reader was on. The fix invents no new ranking; it simply lets each version be found, paired and trusted on its own terms.

The bilingual page-pair checklist

The lead magnet is a self-contained checklist you can tick off per page pair, with no software and no sign-up. It covers these items for each English and Arabic page you publish together:

• English URL and its Arabic equivalent recorded side by side.
• Content completeness: the Arabic version is full, not a shortened stub.
• Canonical set to each page itself, never cross-language.
• Reciprocal alternates present on both pages and pointing both ways.
• Language switch goes to the matching page, not the homepage.
• RTL layout verified on a real device.
• Forms tested in Arabic input and reading order.
• Prices and scope consistent across the pair.
• Image text has a version for each language.
• A named reviewer signed off the Arabic content.
• Indexing readiness confirmed before the page is allowed into search.

Download the Arabic-English page-pair checklist (upstream-13-bilingual-page-checklist.html)

Open it in any browser, print it if you prefer paper, and run one row per page pair before launch.

Where this fits with the rest of your site

Bilingual SEO sits on top of good website and SEO foundations, so it helps to decide your build and your search work with language in mind from the start. If you are still choosing how to build the site, our guidance on WordPress and custom builds covers how each handles multilingual work and who edits it afterwards. When you are planning search work, the piece on what an SEO package should include and the notes on how AI search features actually find content both assume clear, indexable, accurate pages, which is exactly what equivalent language versions give you.

On the services side, our website development work builds the two-language structure and RTL layout, our SEO work handles the canonical and alternate setup and the content review, and for bilingual stores the e-commerce build keeps product data, prices and checkout consistent across languages.

Questions, answered

Should an Arabic page canonicalise to the English page?

No. Each language version should canonicalise to itself. Pointing the Arabic page's canonical at the English page tells search engines the English URL is the real one, which can keep the Arabic page out of results. Set a self-canonical on each version, then pair them with reciprocal language annotations.

Is machine translation enough for a business website?

It is a starting draft, not a finished page. Machine output often misreads intent, leaves marketing phrases awkward, and does not fix layout, forms or image text. For pages that represent your services and prices, have a native Arabic speaker review the content before you publish, and build proper right-to-left usability around it.

Should every language switch go to the homepage?

No. A language switch should take the reader to the matching page they were already on. If someone is on your Arabic service page and taps English, they should land on the English version of that service page. Routing every switch to the homepage frustrates readers and weakens the pairing between versions.

Does language markup tell Google what language my page is in?

Not on its own. Google works out the language from the visible content. Reciprocal language annotations help it serve the right version to the right person, but they do not translate the page or declare its language, and they are not a ranking boost. Clear, correct content in the intended language comes first.

Sources

• Google guidance on localized versions of a page
• Google guidance on canonicalization and duplicate URLs

A sensible next step is to list your current pages, mark which already exist in both languages, and run the page-pair checklist on the first few. If you would rather we set up the URL structure, canonicals, language links and Arabic review for you, send us a brief and we will scope it against your actual pages.