How to Do SEO for a Bilingual Arabic English Website Dubai

If you want to know how to do SEO for a bilingual Arabic English website in Dubai, the honest answer is that most guides give you half the picture. They show you hreflang syntax and call it done. The two things that actually determine whether your Arabic pages rank in Google.ae are almost never discussed: Arabic keywords must be researched from scratch, not translated from English, and machine-translated Arabic copy with hreflang tags attached makes your whole domain weaker, not stronger. This guide covers the full implementation path, written from the perspective of a Dubai agency that builds and optimises bilingual websites for UAE businesses.

The direct answer: set hreflang en-AE and ar-AE tags on every page pair, write a separate XML sitemap for each language, do native Arabic keyword research rather than translating your English list, write real Arabic copy, build RTL layout at the theme level rather than with a plugin, and monitor Arabic and English performance separately in Google Search Console. Skip any of these steps and your Arabic pages will not rank independently.

Why Arabic Keyword Research for Bilingual Websites in Dubai Cannot Be Translated from English

The first mistake Dubai bilingual websites make is treating keyword research as a translation task. A clinic ranking for 'dentist in Dubai' would logically translate that phrase to Arabic and call the research done. That phrase exists and has volume, but the actual searches coming from Arabic-speaking residents in Dubai include colloquial Gulf Arabic terms, hybrid Arabic-English phrases, and service descriptions that never appear in an English keyword list. Indian SEO agencies and generic multilingual guides skip this entirely because they have no data on how UAE Arabic speakers actually search.

This matters technically because hreflang tells Google which page serves which language and region, but hreflang does not create demand. If your Arabic pages target zero-volume or mis-phrased keywords, Google will find the content, understand it is in Arabic, and still not rank it because nothing signals relevance to real Arabic search queries from the UAE.

• Start with Google Keyword Planner set to Arabic language and United Arab Emirates country, not with a translation of your English seed list
• Look for Gulf dialect variants: terms like عيادة versus مستوصف have different search volumes in Dubai even though both mean clinic
• Check Google Suggest and People Also Ask when searching from a UAE IP or VPN connection, as these surface real local query patterns in Arabic
• Use Ahrefs or SEMrush to pull organic Arabic keywords from UAE competitor domains, not from Egyptian Arabic or international Arabic sources
• Identify hybrid queries that mix Arabic text with English brand names or category terms, as these are common in UAE search behaviour across all industries

How to Do SEO for a Bilingual Arabic English Website Dubai: Hreflang en-AE and ar-AE

Hreflang for a Dubai bilingual site should use en-AE and ar-AE, not generic en and ar. The AE suffix tells Google the target region is the United Arab Emirates, which matters because Arabic is spoken across many countries and English content exists globally. Without the region code, your pages compete against international results rather than being prioritised for UAE searchers.

Every page in both languages needs a hreflang annotation pointing to its counterpart, plus a self-referencing tag. Missing the self-reference is the most common implementation error and causes Google to ignore the entire hreflang set for that page. If your site runs on Next.js, the alternateLanguages field in the metadata API generates these tags automatically when your i18n config is correctly set up.

1. Add a link rel=alternate hreflang=en-AE tag on every English page pointing to its Arabic counterpart URL
2. Add a link rel=alternate hreflang=ar-AE tag on every Arabic page pointing to its English counterpart URL
3. Add a self-referencing hreflang tag on each page, pointing to itself with its own language and region code
4. Build a separate XML sitemap for each language and submit both to Google Search Console under your property
5. Confirm implementation using Search Console's URL Inspection tool or the Hreflang Tags Testing Tool by Aleyda Solis
6. Check that Arabic URLs use consistent path prefixes such as /ar/ or /ar-ae/ and that no Arabic page is blocked by robots.txt or a noindex tag

RTL Website SEO in Dubai: What Gets Your Arabic Pages Penalised

RTL layout is not just a visual preference. If your Arabic pages load with left-to-right layout and a plugin or JavaScript flips the direction after the page renders, Google may index the page before the direction switch happens. This means the Arabic content appears visually correct to users but is misrepresented to Googlebot. For SEO purposes, dir=rtl must be set on the html element in the server-rendered source, not applied after the fact by client-side scripts.

Beyond crawlability, poor RTL implementation signals to users that the Arabic experience was an afterthought. High bounce rates on Arabic pages compound the SEO damage because engagement signals feed back into ranking. A structurally broken Arabic page that users abandon in seconds will underperform even with correct hreflang and good keyword targeting.

• Set dir=rtl on the html element for Arabic pages in the server-rendered HTML, not via JavaScript or a third-party plugin
• Use CSS logical properties such as padding-inline-start and margin-inline-end instead of left and right, so layout mirrors correctly without additional overrides
• Test Arabic page rendering with Googlebot by using the URL Inspection tool in Search Console and reviewing the rendered HTML screenshot
• Confirm Arabic fonts load correctly at small screen sizes, since mobile-first indexing means Google evaluates your mobile Arabic rendering first

Tracking Bilingual SEO Performance in Google Search Console

Most Dubai businesses track their bilingual site as a single property and cannot tell whether the Arabic or English pages are driving performance. Without separating the data, you cannot identify which language is underperforming or where ranking opportunities exist. The fix is straightforward: use Search Console's page-level filters to isolate Arabic URLs.

Under the Performance report, filter by page URL to isolate your Arabic page paths such as /ar/ or /ar-ae/. Compare impressions, clicks, and average position separately for each language. High impressions with low clicks on Arabic pages means the meta titles and descriptions need native Arabic copywriting. Near-zero impressions on Arabic pages means a technical problem: hreflang is misconfigured, Arabic URLs are blocked from indexing, or the content has not been crawled yet.

• Impressions and clicks for Arabic URLs versus English URLs, filtered by page path in the Search Console Performance report
• Average position for target Arabic keywords to confirm ranking progress over time
• Index coverage for Arabic pages to catch noindex tags or robots.txt rules that block Arabic content from being indexed
• Core Web Vitals separately for Arabic pages, as RTL layout and Arabic font loading can produce different performance scores from English pages
• Click-through rate for Arabic meta titles, since a low CTR on a well-ranked Arabic page usually means the meta copy does not match how UAE users phrase their actual queries

Getting bilingual SEO right in Dubai means treating the Arabic side of your site as a separate SEO project with its own keyword strategy, its own copywriting brief, and its own performance benchmarks. If you want to see what a properly structured bilingual website looks like before committing to a build, Antox offers a free website preview for Dubai businesses.