Multilingual Website SEO — hreflang, Arabic SEO and Global Strategy
Separate URLs per language, correct hreflang tags, native-language content, Arabic RTL optimisation and common multilingual SEO mistakes. For GCC and global businesses.
Multilingual SEO requires separate URLs per language, correct hreflang tags, native-language content (not translated), and proper language targeting in Search Console. An estimated 75% of multilingual sites get hreflang wrong, which means their content competes against itself instead of serving the right audience. For Arabic content, add RTL layout, Arabic-optimised fonts and language-specific keyword research.
URL structure: subdirectory, subdomain or ccTLD
The first decision in multilingual SEO is how to structure your URLs. Each option has trade-offs between ease of management, geo-targeting signals and authority distribution. For most businesses in Bahrain serving both Arabic and English audiences, subdirectories like /en/ and /ar/ strike the best balance.
| Structure | Example | Best for | Downside |
|---|---|---|---|
| Subdirectory | /en/, /ar/ | Single-domain strategy, most GCC businesses | No geo-targeting by domain |
| Subdomain | en.bahrainserver.net | Large sites with separate teams per language | Dilutes domain authority across subdomains |
| ccTLD | .com, .sa, .ae | Targeting specific countries strongly | Expensive, complex, needs separate hosting per domain |
Google’s guidance is clear: any of these structures can work, provided you implement hreflang correctly and do not serve the same content on multiple URLs without proper annotation.
hreflang implementation
Hreflang tags tell Google which language version of a page to show in search results. They are placed in the <head> as <link rel="alternate" hreflang="x" href="y"> tags or in the HTTP header for non-HTML content. Every language version must link to every other version, including itself. This creates a bidirectional annotation that Google validates before applying.
A common mistake is omitting the x-default tag. This tells Google which version to show when no language matches the user’s settings. For a bilingual Bahrain site, set x-default to English as the most widely understood fallback.
Arabic SEO
Arabic SEO is not English SEO in another script. Google treats Arabic with distinct stemming rules — the root-based morphology means a single root word can generate dozens of variants, and Google understands these relationships. Keyword research must be conducted in Arabic by native speakers, not translated from English, because search behaviour differs significantly between languages.
Technical requirements for Arabic content include: dir="rtl" and lang="ar" on the <html> element, Arabic-optimised web fonts (Cairo, Noto Kufi Arabic, Tajawal), proper handling of Arabic numerals and date formats, and bidirectional text management for mixed English-Arabic content. Test with screen readers like NVDA with the Arabic language pack.
Content strategy: native writing, not translation
The biggest mistake companies make with multilingual SEO is translating content from their primary language. Translation produces grammatically correct text that reads like a translation — stilted, culturally flat and often missing the local search terms that users actually type. Native content writers produce text that flows naturally and includes the colloquial phrases and search patterns of their audience.
This is especially important for Arabic, where Modern Standard Arabic (used in translation) differs noticeably from the Arabic used in everyday search queries. Users searching in Arabic use a mix of MSA and dialectal terms. A native writer knows which register fits your topic and audience.
Common multilingual SEO errors
The most frequent errors in multilingual SEO are: missing self-referencing hreflang tags (every page must link to itself), inconsistent hreflang across pages in the same language cluster, using language codes instead of locale codes (e.g., ar when you need ar-bh), serving auto-translated content without manual review, and blocking language versions in robots.txt.
Another common issue is content duplication. When the same English page is served to the US, UK and Australia without hreflang, Google treats them as duplicates and may consolidate rankings on one version. Always annotate regional variations separately, even when the language is the same.
Tools to validate your multilingual setup
Google Search Console’s International Targeting report shows which countries and languages Google has detected for your site and flags hreflang errors. The hreflang validator at merkle.com and the ‘Hreflang Tags’ feature in Screaming Frog both check your annotations for consistency and completeness.
For Arabic-specific validation, test your site with a screen reader configured for Arabic and verify that the reading order, pronunciation and script rendering are correct. Google’s Mobile-Friendly Test also checks whether your RTL layout renders correctly on mobile devices.
Frequently asked questions
Yes. Google strongly recommends using different URLs per language — subdirectories (/en/, /ar/), subdomains (en.example.com, ar.example.com), or ccTLDs (example.com, example.ae). Separate URLs allow each language version to build its own authority and make hreflang implementation straightforward.
Hreflang is an HTML attribute that tells search engines which language a page is in and which regional variation to show. Without it, Google may serve the wrong language version to users, diluting your rankings in both markets. Proper hreflang implementation is the single most important technical requirement for multilingual SEO.
No. Machine translation is a quick fix for understanding but produces content that reads unnaturally and often misses cultural context. Google can detect machine-translated content and may treat it as low quality. Invest in native-language writers who understand both the language and your industry.
Arabic SEO requires RTL layout, Arabic-optimised typography, correct use of Arabic Unicode characters (not Urdu or Persian variants), and keyword research conducted in Arabic (not translated from English). Google treats Arabic searches with distinct stemming and morphology rules that affect how keywords match.
Yes, but you need country-specific hreflang annotations. For example, en-bh for Bahrain, en-sa for Saudi Arabia, en-ae for the UAE. Even though the language is the same, country targeting helps Google serve the right content based on the user’s location.