Multilingual CMS Setup for UAE: Arabic, English, and Beyond
Why Multilingual Matters in the UAE Market
Dubai is one of the most linguistically diverse cities on Earth. With a population of approximately 9.9 million, the UAE is home to:
- 15% Emirati citizens (Arabic native speakers)
- 85% expatriates from 200+ countries
- Major language groups: English, Hindi, Urdu, Malayalam, Tagalog, French, Russian, Chinese
In this environment, a monolingual website isn’t just limiting — it’s exclusionary. Consider these statistics:
- 72% of consumers spend most of their time on websites in their native language
- 56% of consumers say language is more important than price
- 40% of consumers won’t buy from websites not in their language
- Multilingual sites have 2x the engagement of monolingual sites
For Dubai businesses, multilingual optimization isn’t a luxury. It’s a competitive necessity. And yet, less than 30% of Dubai business websites offer Arabic content — the official language of the UAE.
This guide covers multilingual CMS setup across major platforms, with specific focus on Arabic (RTL) implementation, SEO optimization, and cultural localization.
RTL (Right-to-Left) Design Considerations
The Arabic Script Challenge
Arabic is written right-to-left (RTL), which fundamentally changes web layout, typography, and user interaction. Implementing RTL isn’t just about flipping text direction — it’s about redesigning the entire interface.
RTL Impact Areas
| Element | LTR (English) | RTL (Arabic) | Implementation |
|---|---|---|---|
| Text direction | Left to right | Right to left | direction: rtl |
| Text alignment | Left-aligned | Right-aligned | text-align: right |
| Margins | Left margin for indentation | Right margin for indentation | |
| Padding | Left padding | Right padding | Logical properties |
| Navigation | Left-aligned menu | Right-aligned menu | CSS flex-direction |
| Icons with text | Icon → Text | Text ← Icon | CSS order |
| Progress bars | Fill left to right | Fill right to left | CSS transform |
| Carousels | Slide left to right | Slide right to left | JavaScript direction |
| Form labels | Label left of input | Label right of input | CSS flex/grid |
| Number alignment | Left | Left (numbers are LTR) | direction: ltr for numbers |
CSS Implementation for RTL
Method 1: Direction Attribute
<html dir="rtl" lang="ar">
/* Global RTL styles */
[dir="rtl"] {
direction: rtl;
text-align: right;
}
[dir="rtl"] .nav-menu {
flex-direction: row-reverse;
}
[dir="rtl"] .icon-before-text {
margin-right: 0;
margin-left: 8px;
}
[dir="rtl"] .progress-bar {
transform: scaleX(-1);
}Method 2: Logical Properties (Modern Approach)
/* Logical properties adapt to text direction automatically */
.container {
padding-inline-start: 24px; /* Left in LTR, Right in RTL */
padding-inline-end: 24px; /* Right in LTR, Left in RTL */
margin-block-start: 16px; /* Top in both */
margin-block-end: 16px; /* Bottom in both */
}
.element {
border-inline-start: 2px solid; /* Left in LTR, Right in RTL */
text-align: start; /* Left in LTR, Right in RTL */
float: inline-start; /* Left in LTR, Right in RTL */
}Logical Properties Browser Support: 95%+ of modern browsers support logical properties. For older browsers, fall back to traditional properties with [dir=”rtl”] selectors.
RTL Testing Checklist
| Element | LTR Check | RTL Check | Pass/Fail |
|---|---|---|---|
| Text alignment | Left | Right | |
| Navigation order | Left to right | Right to left | |
| Form labels | Left of input | Right of input | |
| Button icons | Icon left of text | Icon right of text | |
| Modal close button | Top-right | Top-left | |
| Pagination arrows | ← Previous / Next → | → ffffffffffff / ffffffffffff ← | |
| Calendar widget | Sun-Sat | ffffffffffff-ffffffffff | |
| Charts/graphs | Y-axis left | Y-axis right | |
| Video player controls | Left-aligned | Right-aligned | |
| Search icon | Left of input | Right of input |
WordPress Multilingual: WPML vs. Polylang
WPML (WordPress Multilingual Plugin)
WPML is the most comprehensive multilingual solution for WordPress:
WPML Features
| Feature | WPML | Best For |
|---|---|---|
| Translation management | Built-in workflow | Teams with translators |
| String translation | Complete Theme/plugin text | |
| URL structure | Flexible (subdirectory, subdomain, domain) | SEO-focused sites |
| E-commerce | WooCommerce Multilingual | Multilingual stores |
| RTL support | Full Arabic, Hebrew, Urdu | |
| Translation memory | Yes | Consistent terminology |
| Professional translation | Integrated service | Outsourced translation |
WPML Pricing
- Multilingual Blog: $39/year
- Multilingual CMS: $99/year
- Multilingual Agency: $199/year
WPML Strengths
- Mature, well-supported plugin
- Comprehensive feature set
- Strong RTL support
- Professional translation integration
- Active development and updates
WPML Weaknesses
- Performance impact (adds database queries)
- Can conflict with other plugins
- Learning curve for translation workflow
- Annual subscription cost
Polylang (Free Alternative)
Polylang is the most popular free multilingual plugin for WordPress:
Polylang Features
| Feature | Polylang | Polylang Pro | Best For |
|---|---|---|---|
| Basic multilingual | Free | $99/year | Simple sites |
| URL structure | Subdirectory only | Subdirectory/subdomain | SEO-focused |
| String translation | Limited | Full Theme/plugin text | |
| E-commerce | Not supported | WooCommerce support | Multilingual stores |
| RTL support | Basic | Full | Arabic sites |
| Translation sharing | No | Yes | Similar content across languages |
Polylang Strengths
- Free version available
- Lightweight (less performance impact than WPML)
- Simple interface
- Good for basic multilingual needs
Polylang Weaknesses
- Limited features in free version
- No professional translation integration
- WooCommerce support requires Pro
- Less comprehensive than WPML
WPML vs. Polylang Decision Matrix
| Factor | Choose WPML | Choose Polylang |
|---|---|---|
| Budget | $99/year is acceptable | Free or low cost preferred |
| Complexity | Need translation workflow, teams | Simple bilingual site |
| E-commerce | WooCommerce multilingual store | No e-commerce |
| Professional translation | Need integrated service | In-house translation |
| Performance priority | Acceptable trade-off | Maximum performance |
| Support needs | Want dedicated support | Community support sufficient |
| RTL requirements | Full Arabic support needed | Basic RTL sufficient |
Shopify Markets: Multi-Currency and Multi-Language
Shopify Markets Overview
Shopify Markets, launched in 2022 and significantly expanded by 2026, is Shopify’s native solution for international selling:
Shopify Markets Capabilities
| Feature | Availability | Notes |
|---|---|---|
| Multi-language | All plans | Up to 20 languages per store |
| Multi-currency | All plans | Local currency pricing |
| Local domains | Shopify plan+ | hellopixels.ae, hellopixels.sa |
| Local payment methods | All plans | Region-specific gateways |
| Duty and tax | Advanced+ | Automatic calculation |
| Localized shipping | All plans | Regional shipping rates |
| Content translation | All plans | AI + manual translation |
Shopify Markets Arabic Setup
Step 1: Enable Languages
Shopify Admin → Settings → Languages → Add Language → Arabic
Step 2: Configure Markets
Shopify Admin → Settings → Markets → Add Market → Middle East
Step 3: Set Local Currency
Market Settings → Currency → AED (UAE), SAR (Saudi), etc.
Step 4: Translate Content
- Shopify’s AI translation (auto-translates basic content)
- Manual review and refinement
- Professional translation for critical content (product descriptions, legal)
Step 5: Configure Local Domains
Settings → Domains → Connect Domain → hellopixels.ae
Shopify Markets Limitations
- URL Structure
- Languages use subdirectories: /ar, /en
- No subdomain option for languages
- Limited hreflang control
- Arabic SEO
- Basic Arabic SEO support
- No custom Arabic URL slugs
- Limited schema markup control for Arabic
- RTL Support
- Theme-dependent RTL support
- Not all Shopify themes support RTL
- Custom CSS required for proper RTL layout
- Translation Quality
- AI translation is acceptable for basic content
- Product descriptions and marketing content need human review
- Legal content must be professionally translated
Shopify Markets Pricing
| Feature | Basic Shopify | Shopify | Advanced | Shopify Plus |
|---|---|---|---|---|
| Multi-language | 2 languages | 5 languages | 10 languages | 20 languages |
| Multi-currency | Included | Included | Included | Included |
| Local domains | Not available | Included | Included | Included |
| Currency conversion fee | 2% | 1.5% | 1% | Custom |
Headless CMS for Multi-Language Content
Headless Multilingual Architecture
Headless CMS platforms offer the most flexible multilingual architecture:
┌─────────────────────────────────────────┐
│ Headless CMS (Contentful) │
│ ┌─────────┐ ┌─────────┐ ┌────────┐ │
│ │ English │ │ Arabic │ │ French │ │
│ │ Content │ │ Content │ │ Content│ │
│ └────┬────┘ └────┬────┘ └───┬────┘ │
│ └─────────────┴───────────┘ │
│ API │
└────────────────────┬────────────────────┘
│
┌──────┼──────┐
▼ ▼ ▼
┌────────┐ ┌────────┐ ┌────────┐
│ Next.js│ │ Next.js│ │ Next.js│
│ /en │ │ /ar │ │ /fr │
└────────┘ └────────┘ └────────┘Headless Multilingual Advantages
- Content structure is language-agnostic
- Translation workflow is built into the CMS
- Front-end can be optimized per language
- Full control over URL structure, hreflang, and SEO
- RTL support is front-end dependent, not CMS limited
Contentful Multilingual Setup
Contentful Localization Features
| Feature | Implementation |
|---|---|
| Locales | Define locales (en-AE, ar-AE, fr-AE) |
| Field-level translation | Each field can have multiple translations |
| Fallback locales | Default to English if Arabic translation missing |
| Translation workflow | Built-in review and approval |
| API delivery | Content delivered by locale parameter |
Contentful Arabic Content Model
// Fetch Arabic content
const entry = await client.getEntry('entryId', {
locale: 'ar-AE'
});
// Content structure
{
"fields": {
"title": {
"en-AE": "HelloPixels Digital Agency",
"ar-AE": " "
},
"description": {
"en-AE": "Dubai's leading digital agency...",
"ar-AE": " "...
}
}
}Sanity Multilingual Setup
Sanity uses a document-level translation approach:
// English document
{
_id: 'about-page-en',
_type: 'page',
language: 'en',
title: 'About Us',
content: '...'
}
// Arabic document (linked to English)
{
_id: 'about-page-ar',
_type: 'page',
language: 'ar',
title: ' ',
content: '...',
translationOf: {
_type: 'reference',
_ref: 'about-page-en'
}
}Sanity Translation Plugin:
- @sanity/document-internationalization for document-level translation
- @sanity/language-filter for field-level translation
hreflang Tags and SEO for Multilingual Sites
The hreflang Implementation
hreflang tags tell Google which language/region version of a page to show to which user. They’re essential for multilingual SEO.
hreflang Structure
<link rel="alternate" hreflang="en-ae" href="https://www.hellopixels.com/en/" />
<link rel="alternate" hreflang="ar-ae" href="https://www.hellopixels.com/ar/" />
<link rel="alternate" hreflang="en-sa" href="https://www.hellopixels.com/sa/en/" />
<link rel="alternate" hreflang="ar-sa" href="https://www.hellopixels.com/sa/ar/" />
<link rel="alternate" hreflang="x-default" href="https://www.hellopixels.com/en/" />hreflang Best Practices
- Use Correct Language-Region Codes
- en-ae (English, UAE)
- ar-ae (Arabic, UAE)
- en-sa (English, Saudi Arabia)
- ar-sa (Arabic, Saudi Arabia)
- Not: en-dubai, arabic, uae
- Include Self-Referencing hreflang Every page must reference itself in its hreflang set.
- Use x-default for Language Selectors The x-default page should be a language/region selector or your global default.
- Ensure Bidirectional Links If Page A links to Page B with hreflang, Page B must link back to Page A.
- Validate Before Publishing Use Google’s hreflang testing tool or SEMrush hreflang checker.
Common hreflang Mistakes
| Mistake | Impact | Fix |
|---|---|---|
| Using “ar” without region | Loses regional targeting | Use ar-ae, ar-sa, etc. |
| Missing self-reference hreflang | Confuses Google | Add self-referencing hreflang |
| Broken alternate URLs | hreflang points to 404 | Validate all alternate URLs |
| Conflicting canonicals | Canonical contradicts hreflang | Ensure canonical matches hreflang |
| Only implementing on homepage | Misses internal pages | Implement site-wide |
Content Translation: Human vs. AI-Powered
The Translation Quality Spectrum
| Method | Quality | Cost | Speed | Best For |
|---|---|---|---|---|
| Professional human translation | Excellent | High ($0.10–$0.25/word) | Slow | Marketing, legal, brand content |
| AI translation + human review | Very Good | Medium ($0.03–$0.08/word) | Fast | Product descriptions, blog posts |
| AI translation only | Good | Low ($0.01–$0.03/word) | Instant | Basic content, internal docs |
| Machine translation (Google/DeepL) | Fair | Very Low (free–$20/month) | Instant | Drafts, understanding |
AI Translation Tools for Arabic
| Tool | Arabic Quality | Cost | Integration |
|---|---|---|---|
| Google Translate | Good | Free API | API, plugins |
| DeepL | Very Good | $6.99–$33.49/month | API, limited Arabic |
| Microsoft Translator | Good | Free tier + paid | Azure API |
| Tarjama | Excellent | Custom | Professional service |
| Smartling | Very Good | Custom | Enterprise platform |
| Lokalise | Good | $120–$750/month | Developer-focused |
Arabic Translation Challenges
- Dialect variation: Gulf Arabic (UAE, Saudi) differs from Egyptian, Levantine, and Maghrebi Arabic
- Formal vs. colloquial: Business content uses Modern Standard Arabic (MSA), not dialect
- Cultural nuance: Direct translation often misses cultural context
- RTL formatting: Arabic text requires proper RTL handling in all systems
The Hybrid Translation Workflow
- AI Translation (Instant)
- Human Review (1–2 days)
- Cultural Localization (1–2 days)
- SEO Optimization (0.5–1 day)
- Final Review & Publish (0.5 day)
Total time per page: 3–6 days Total cost: 30–50% of pure human translation
Localizing for Cultural Context, Not Just Language
Beyond Translation: Cultural Localization
Localization is more than translating words. It’s adapting content for cultural context:
| Element | English (Global) | Arabic (UAE) | Why It Matters |
|---|---|---|---|
| Images | Diverse, Western-focused | Regional, culturally appropriate | Builds trust and relevance |
| Colors | Blue (trust), green (growth) | Green (Islamic association), gold (luxury) | Cultural color psychology |
| Currency | USD | AED (UAE), SAR (Saudi) | Local pricing builds trust |
| Phone format | +1-XXX-XXX-XXXX | +971-4-XXX-XXXX | Local format familiarity |
| Date format | MM/DD/YYYY | DD/MM/YYYY | Regional standard |
| Holidays | Christmas, Thanksgiving | Eid, Ramadan, UAE National Day | Cultural relevance |
| Business hours | 9 AM–5 PM | 9 AM–1 PM, 4 PM–8 PM (Ramadan) | Local business culture |
| Social proof | Western testimonials | Regional testimonials, Arabic names | Local trust signals |
| Legal content | GDPR-focused | UAE Data Protection Law | Regulatory compliance |
| Payment methods | Credit cards, PayPal | Credit cards, Telr, PayFort, COD | Local payment preferences |
The UAE Localization Checklist
| Element | Status | Notes |
|---|---|---|
| Arabic content reviewed by native speaker | Not just translated —localized | |
| Currency displayed in AED | For UAE market | |
| Local phone number format | +971-4-XXX-XXXX | |
| UAE business address | Physical address in Dubai/UAE | |
| Local payment options | Telr, PayFort, COD | |
| Arabic-friendly imagery | Culturally appropriate photos | |
| Ramadan/holiday content | Seasonal relevance | |
| Arabic social media links | Local platform presence | |
| UAE legal compliance | Terms, privacy, data protection | |
| Local customer support | Arabic-speaking support |
FAQ: Multilingual CMS Setup for UAE
WordPress with WPML or Polylang offers the best Arabic support for small-medium sites. For enterprise, headless CMS (Contentful, Sanity) with custom Arabic front-end provides maximum flexibility. Shopify Markets is improving but still limited for Arabic SEO.
Professional translation: $0.10–$0.25/word. AI + human review: $0.03–$0.08/word. A typical 10-page business website (5,000 words) costs $500–$1,250 for professional translation.
Subdirectories (/ar/) are recommended for SEO. They consolidate domain authority and are easier to manage. Subdomains (ar.site.com) split authority and are harder to maintain. ccTLDs (site.ae) are best for strong regional targeting but require separate SEO efforts.
No. One GBP listing can include both English and Arabic information. Add Arabic business description, posts, and Q&A to your existing profile.
Use dir=”auto” for user-generated content (detects direction automatically). For structured content, wrap Arabic sections in <div dir=”rtl” lang=”ar”>. Ensure fonts support both scripts.
Not recommended for public-facing content. Google Translate produces grammatical errors and cultural inaccuracies. Use it for internal drafts only. Professional translation is essential for business credibility.
High. Arabic SEO has far less competition than English. A Dubai business with quality Arabic content can dominate Arabic search results with lower investment. Additionally, Arabic content builds trust with local Emirati and Arab expatriate customers.
Use Chrome DevTools (Rendering tab → Emulate CSS direction: rtl). Test on real Arabic devices (iPhone, Samsung with Arabic locale). Use BrowserStack for cross-device testing. Always test with native Arabic speakers.
Start with key pages: homepage, about, services, contact, and top product pages. Expand gradually based on traffic and conversion data. A partially translated site is better than no Arabic content at all.
Technical setup: 1–2 weeks. Content translation: 2–8 weeks depending on volume. SEO optimization: 1–2 weeks. Total: 4–12 weeks for a small-medium site. Enterprise: 3–6 months.
Conclusion: Speak Your Customer’s Language — Literally
In Dubai’s multilingual market, language isn’t a barrier to overcome. It’s an opportunity to capture. The businesses that invest in Arabic content, proper RTL implementation, and cultural localization will dominate a market segment that most competitors ignore.
The technical implementation is straightforward. The translation investment is modest. The competitive advantage is enormous.
For Dubai businesses, the question isn’t whether to go multilingual. It’s why you haven’t already.
HelloPixels builds multilingual websites for Dubai businesses with proper Arabic RTL support, cultural localization, and SEO optimization. We don’t just translate — we localize for the UAE market.
Sustainable Web Design: Building Eco-Friendly Websites That Perform
The internet consumes more electricity than the entire country of Germany — and it’s growing. By
The 80/20 Rule of Modern Web Dev: Where You’re Overbuilding
Web development in 2025 finds itself at an unusual crossroads. We have more tools, frameworks, and l
How to Start a Web Design and Web Development Company
When you are launching your web design firm or web development company – it could also be a web de
