Lorixen.
EN

Language switchers visitors can find: mistakes to avoid

Short answer: A good language switcher sits where people look for it (usually top right on English pages and top left on Arabic pages), names each language in that language ("العربية", "English"), takes visitors to the same page in the other language rather than the homepage, and remembers their choice without forcing it. Avoid country flags, avoid redirecting people automatically, and give each language its own URL. For a two-language site, a single visible link to the other language is usually all you need.

Many businesses in Dubai, Abu Dhabi, Doha and Riyadh run bilingual websites, and the switch between Arabic and English is one of the most-used controls on the site. It's also one of the most commonly fumbled. Here are the mistakes that come up again and again, and what to do instead.

Mistake 1: Using flags for languages

A UAE flag for Arabic and a UK or US flag for English is tempting, but it's confusing. W3C's internationalisation guidance recommends resisting the temptation to use country flags to identify languages: some countries have more than one language, and some languages are spoken in many countries. Flags may suit links to geographically different versions of a site (a UAE shop versus a Saudi shop), but not pages that are simply translations.

Instead: use the language's own name as text.

Mistake 2: Naming languages in the wrong language

An English page offering "Arabic" expects an Arabic speaker to read English to find their language.

Instead: write each language name in that language: "العربية" and "English". W3C's article suggests you may also show the meaning in the current page's language, such as "français (French)", for example in a tooltip. If you do, mark up the Arabic text with lang="ar" so screen readers pronounce it correctly; MDN explains that the lang attribute holds a BCP 47 language tag for the element's content.

Mistake 3: Hiding the switcher

Language toggles buried in the footer, inside a hamburger menu or behind a globe icon with no label are easy to miss, especially on mobile.

Instead: place the switcher in the header on every page, visible without opening a menu on desktop, and at the top of the mobile menu (or beside it) on phones. Keep it in the same position across the site. On a right-to-left Arabic layout, the header mirrors, so the switcher typically moves to the opposite side from the English version; test both.

Mistake 4: Sending people back to the homepage

A visitor reads your English pricing page, switches to Arabic, and lands on the Arabic homepage. Now they have to find the pricing page again, in a language they've just switched to.

Instead: link each page to its direct equivalent in the other language. If a page has no translation yet, take them to the closest relevant page and say so briefly, rather than silently dropping them on the homepage.

Mistake 5: Redirecting automatically by browser language or location

Some sites detect the browser language or IP address and force visitors to one version. Expats in the Gulf often use phones set to English while preferring Arabic for some tasks, or the reverse.

Instead: let the user choose. Google's guidance on multilingual sites advises against automatically redirecting users from one language version to another based on what you think their language may be, because such redirections can stop users and search engines seeing all versions. It recommends linking to other language versions so users can choose. A gentle banner suggesting the other language is fine; a forced redirect isn't.

Mistake 6: One URL for both languages

Sites that switch language with a cookie or script on the same URL make it impossible to share a link to the Arabic page specifically, and harder for search engines to find both versions.

Instead: give each language its own URL, for example /ar/ and /en/ folders. Google recommends different URLs for each language version rather than cookies or browser settings, with hreflang annotations to help Google show the right version.

Mistake 7: Not remembering the choice

A visitor chooses Arabic, then clicks a link in an email that opens English again, every time.

Instead: remember the choice (a cookie or account setting) and use it when someone arrives at the root of the site, while still respecting explicit links to a specific language page. Remembering must never override a link someone deliberately followed.

Mistake 8: A dropdown for two languages

A select menu with two options adds a click and hides the alternative.

Instead: for two languages, show a single link to the other one: on English pages "العربية", on Arabic pages "English". Use a menu only when you have several languages. W3C's article covers considerations for pull-down lists if you do need one.

Mistake 9: Forgetting forms, emails and checkout

The site switches language, but form error messages, confirmation emails and the payment page stay in English.

Instead: carry the chosen language through the whole journey: form labels and errors, confirmation pages, transactional emails, PDFs and invoices. Test a complete enquiry or purchase in each language.

Mistake 10: Mixing scripts and directions carelessly

Arabic text inside English pages (or the reverse) without proper direction handling can display punctuation and numbers in the wrong places.

Instead: set the page's lang and dir attributes correctly for each version, and mark up short passages in the other language with their own lang attribute. Test phone numbers, prices and dates in both layouts.

FAQ

Where should the language switcher go on an Arabic page?

In the header, consistently placed. Because Arabic layouts mirror English ones, it usually sits on the opposite side from the English version.

Should the switcher say "AR / EN"?

Abbreviations work for some audiences but are less clear than "العربية" and "English", and screen readers may read them as letters.

Can we auto-detect language just for the first visit?

Suggest, don't force. A dismissible banner offering the other language respects the visitor's choice.

Do we need separate URLs for Arabic and English?

Google recommends separate URLs per language version, which also makes pages shareable.

If visitors keep missing the switch between your Arabic and English pages, send us your site address and we'll review where the switcher sits and where it leads.

Sources

WhatsAppLet’s talk