A well-built bilingual English and Arabic website needs more than translated text. It needs separate crawlable URLs for each language, correct right-to-left layout, hreflang annotations linking equivalent pages, carefully reviewed Arabic content and consistent technical SEO across both versions. For UAE audiences, doing this properly improves usability and gives each language version a fair chance to appear in search results.
Choose a clear URL structure
Google recommends separate URLs for each language version, so that each can be crawled and indexed. Common patterns include language folders such as example.com/en/ and example.com/ar/, or subdomains. Folders are often simpler to manage on one domain. Avoid relying on cookies, browser settings or JavaScript to switch language on the same URL, since search engines may not see the alternate version. Keep URL structure consistent across languages and decide whether Arabic slugs use Arabic or transliterated words, then apply that rule everywhere.
Implement hreflang correctly
Hreflang annotations tell search engines which pages are equivalent versions for different languages or regions. Each page should reference itself and all alternates, and the references must be reciprocal. You can add them in the HTML head, HTTP headers or XML sitemap. Google Search Central documents the supported methods in its guide to localized versions.
- Use valid language codes such as en and ar, with region codes only when needed.
- Include a self-referencing hreflang on each page.
- Make annotations reciprocal across all language versions.
- Link only to pages that actually exist.
- Consider an x-default page for visitors who match no listed language.
Build proper right-to-left design
Arabic reads right to left, so layouts, navigation, icons and forms need to be mirrored, not just translated. Set the dir attribute and language attribute on the HTML element, use logical CSS properties such as margin-inline-start instead of left and right, and check that sliders, breadcrumbs and progress bars behave correctly. Test fonts for Arabic legibility and line height, and make sure numbers, phone numbers and mixed English-Arabic text display in the right order.
Invest in translation quality and local relevance
Direct translation often reads awkwardly. Use professional or native reviewers who understand your industry, and keep terminology consistent through a glossary. Research Arabic search terms separately, because people may phrase queries differently from English speakers, and Arabic titles, descriptions and headings should be written for those searches. Google Search Central recommends content that is helpful and written for people, which applies equally to Arabic pages.
- Audit which pages matter most for Arabic-speaking customers.
- Research Arabic keywords and common search phrases.
- Translate and adapt content with native review.
- Localise metadata, image alt text and structured data.
- Add a visible language switcher linking to the equivalent page.
- Submit separate sitemaps or sitemap entries and monitor both versions in Search Console.
A UAE example and a launch checklist
A Dubai dental clinic wants Arabic and English pages for treatments, doctors and booking. The team translates the English pages quickly, keeps one URL and uses a script to switch language, then wonders why Arabic pages never appear in search results. A better plan gives each language its own URL, writes Arabic page titles and descriptions for how patients actually search, mirrors the layout for right-to-left reading, and ensures the booking form works with Arabic names and local phone formats. The example is illustrative, but each of these mistakes appears regularly in bilingual projects.
Run through this list before launching a bilingual site:
- Every Arabic page has its own crawlable URL and a matching English page, where one exists.
- Hreflang annotations are reciprocal and point only to live pages.
- The html element carries the correct lang and dir attributes on each version.
- Navigation, icons, forms and sliders have been tested in right-to-left mode on mobile.
- Arabic titles, descriptions, headings and image alt text have been written, not just translated.
- Forms accept Arabic and English input, and notification emails display correctly.
- Each language version appears in the sitemap and is monitored in Search Console.
- A native Arabic reader has reviewed the final pages.
Conclusion: treat each language as a first-class site
A bilingual website succeeds when each language has its own URLs, correct RTL design, reviewed content and clean hreflang signals. Plan the structure before design, test with real Arabic speakers and monitor both versions after launch. If you are building or upgrading a bilingual site, Myrran can help with architecture, design and SEO setup so both audiences get a first-class experience.
Frequently asked questions
Should Arabic and English pages use separate URLs?
Yes. Google recommends giving each language version its own URL rather than switching language dynamically on the same address, so each version can be crawled, indexed and shared separately.
Is machine translation good enough for Arabic pages?
It can help with drafts, but quality varies. Have a fluent Arabic speaker review all customer-facing content for tone, terminology and local usage before publishing.
Do we need to mirror every English page in Arabic?
Not necessarily. Prioritise pages that matter to Arabic-speaking customers. If a page exists in only one language, link only to versions that really exist and avoid empty or auto-generated placeholders.
Sources
Plan your bilingual website
Myrran helps UAE businesses build software, automate operations, and manage digital systems.




