Skip to content

Building an Arabic and English website the right way

Right-to-left layouts, SEO for both languages and the common mistakes that make translated sites feel like an afterthought.
Scroll
In this article

In the UAE and across the Middle East, a bilingual website is often expected rather than optional. Government entities, larger companies and many customers work comfortably in both Arabic and English, and plenty of people prefer to read, search and make decisions in Arabic. Yet many bilingual websites feel like an English site with Arabic text poured into it: layouts that break, navigation that points the wrong way and pages that nobody can find in search. This guide walks through how to plan and build a bilingual site properly, from structure to design to SEO.

Start with the structure

Before any design work, decide how the two languages will live on your domain. There are three common approaches.

  • Subdirectories, such as example.com/en/ and example.com/ar/. This keeps everything on one domain and is the simplest option for most businesses.
  • Subdomains, such as ar.example.com. This can suit organisations that run the language versions as separate operations.
  • Separate domains for each language. This is rarely necessary for a business based in one country and doubles the work of building authority.

For most businesses, subdirectories are the practical choice. Whatever you choose, give every page a clear equivalent in the other language wherever possible, and let visitors switch between them without losing their place.

Design for right-to-left from the beginning

Arabic reads from right to left, and a good Arabic layout is a mirror image of the English one, not just the same layout with translated words. Planning for this at the start is far easier than fixing it later.

What needs to mirror

  • Navigation, menus and logos typically move to the opposite side.
  • Directional icons such as arrows, back buttons and chevrons should point the other way.
  • Carousels and sliders should move in the reading direction.
  • Form labels, text alignment and icons inside fields should switch sides.

What should not mirror

  • Logos and brand marks usually stay as they are.
  • Phone numbers, prices and most numerals keep their usual order.
  • Media controls such as play buttons and progress bars generally stay the same.
  • Images of real scenes should not be flipped, or text within them will appear reversed.

On the technical side, modern CSS makes this much easier. Using logical properties, which describe spacing and alignment as start and end rather than left and right, lets one stylesheet serve both directions with far fewer overrides.

Two blank books side by side, one opened left to right and one right to left

Choose typography that works in both scripts

Arabic and Latin letters have very different shapes and proportions. A font pairing that looks balanced in English can make Arabic text look cramped, oversized or hard to read. Choose an Arabic typeface designed to sit comfortably alongside your English one, and test them together on real content.

Arabic text generally needs more generous line height, and it may need a slightly different font size to feel visually equal to English. Check headings, body text, buttons and forms in both languages rather than assuming one setting fits both.

Write, do not just translate

Machine translation has improved, but literal translation still produces copy that feels stiff or occasionally says something you did not intend. The strongest bilingual sites treat each language as its own audience.

  • Adapt messages to the reader, not just the words. A headline that works in English may need a completely different approach in Arabic.
  • Use a consistent tone. Decide whether your Arabic should be formal Modern Standard Arabic or a warmer, more conversational style, and keep it consistent.
  • Have a fluent native speaker review every page before it goes live, including buttons, error messages and form confirmations.
  • Keep both versions updated together. An Arabic page that is two versions behind the English one damages trust.

Search engines treat each language version as its own set of pages, so each one needs its own SEO work.

Research keywords in each language

People do not always search the way a direct translation would suggest. Some search in formal Arabic, some in everyday phrasing, and some mix Arabic and English words or type Arabic words in Latin letters. Research how your customers actually search in each language rather than translating your English keyword list.

Use hreflang correctly

Hreflang tags tell search engines which pages are language equivalents of each other, so they can show the right version to the right person. Every page should reference itself and its counterpart, and the tags must be reciprocal. Mistakes here are common and can cause the wrong language version to appear in results.

Localise every SEO element

  • Write separate page titles and meta descriptions in each language.
  • Decide on a URL approach for Arabic pages. Arabic-script URLs are readable for Arabic speakers but become long and encoded when shared; transliterated or English slugs are simpler to manage. Either can work if you are consistent.
  • Translate image alt text, headings and structured data.
  • Submit sitemaps that include both language versions.

Do not forget the functional details

The small details are where bilingual sites most often break.

  • Forms should accept Arabic input and handle local and international phone number formats.
  • Validation and error messages need translating too, not just labels.
  • Email notifications and confirmation messages should arrive in the language the visitor used.
  • Dates, times and currency should be formatted clearly for each audience.
  • Search on your website should work in both languages.
Hand writing right to left with a reed pen on a paper form, as Arabic forms are filled in

Choosing a platform and plugins

Most modern content management systems support multilingual websites, either natively or through well-established plugins. When choosing, check that the solution handles right-to-left layouts, lets you manage translations side by side, generates hreflang tags automatically and works with your page builder and forms. Test it on a staging site before committing, because switching multilingual setups after launch is time-consuming.

A pre-launch checklist

  1. Every key page has an equivalent in both languages, and the language switcher links them correctly.
  2. Layouts, menus and icons mirror properly in Arabic on desktop and mobile.
  3. Fonts render well in both scripts, with no missing characters.
  4. A native speaker has reviewed all Arabic content, including system messages.
  5. Forms work in both languages and send notifications correctly.
  6. Hreflang tags, titles, descriptions and sitemaps are set up for both versions.

Common mistakes to avoid

  • Launching Arabic pages with placeholder or unreviewed machine-translated text.
  • Mirroring images that contain text or recognisable scenes.
  • Letting the Arabic version fall behind when content is updated.
  • Hiding the language switcher or sending it to the homepage instead of the equivalent page.

Keeping two languages in step after launch

The hardest part of a bilingual website is often not the build but the months that follow. New services, updated prices, blog posts and seasonal offers all need to appear in both languages, and it is easy for one version to fall behind.

  • Agree who writes and who reviews Arabic content before you launch, so updates do not stall.
  • Publish changes in both languages at the same time wherever possible, rather than planning to translate later.
  • Keep a simple list of pages that exist in only one language, and a date for closing each gap.
  • Review both versions together every few months, checking that facts, contact details and offers match.

Treating both languages as equally important in your day-to-day process is what keeps a bilingual site feeling intentional rather than translated.

Build it once, build it properly

A bilingual website built with both languages in mind from day one is easier to maintain, performs better in search and feels respectful to every visitor. Retrofitting Arabic onto an English-only site usually costs more in the end. You can learn more about our team and see what our website work includes on our services page.

Planning a new bilingual website or fixing an existing one? Tell us about your project and we will talk you through the options.

People also ask

Should a bilingual website use subdirectories or subdomains?

For most businesses, subdirectories such as /en/ and /ar/ are the simpler choice. They keep all authority on one domain, are easier to manage and work well with hreflang tags. Subdomains or separate domains make sense only when each language runs as a largely separate business.

Does an Arabic website need its own SEO?

Yes. Arabic searchers use different words and phrasing, so research Arabic keywords separately rather than translating English ones. Each Arabic page needs its own title, meta description and URL, plus hreflang tags linking it to its English version.

How do you make a website right-to-left for Arabic?

Set the page direction to right-to-left with the dir attribute set to rtl and the lang attribute set to ar, then mirror the layout so navigation, icons and alignment flow from the right. Use CSS logical properties, an Arabic-ready font and test forms, numbers and mixed Arabic-English text carefully.