A multilingual WordPress website serves each audience in its own language from one managed installation, with separate URLs, translated navigation and content that search engines can index language by language. For UAE businesses, that usually means Arabic and English, sometimes with a third language for a specific market. WordPress does not do this on its own, but with the right architecture it handles multiple languages very well.
The difference between a bilingual site that works and one that frustrates everyone lies in early decisions: URL structure, the translation approach and a publishing workflow the team can maintain. As part of our web design projects, and specifically our WordPress development, we follow the sequence below. It is written as a practical build order you can use to plan your own project or to check an agency’s approach.
Step 1: Plan languages, markets and content scope
Start with a short written plan before installing anything.
- Languages and default: decide which language is the default and which are secondary. Many UAE sites use English as default with Arabic as a full equivalent, while government-facing and some consumer brands lead with Arabic.
- Scope per language: decide whether every page, post, product and form will exist in every language, or whether some sections stay in one language.
- Who translates: in-house staff, a translation agency, machine translation with human review, or a mix.
- Who approves: name the person responsible for signing off each language, especially Arabic.
This plan drives every later choice. A site with full parity across languages needs a different workflow from one where Arabic covers core pages only.
Step 2: Choose the architecture for a multilingual WordPress website
There are three main ways to build a multilingual WordPress website. Each stores translations differently, which affects editing, performance and long-term flexibility.
| Approach | How it works | Suits |
|---|---|---|
| Translation plugin with linked posts (for example WPML, Polylang) | Each translation is a separate post linked to the original, all in one site | Most business sites, including WooCommerce stores |
| Front-end translation plugin (for example TranslatePress) | Translate by clicking on the live page; translations stored in dedicated database tables | Teams that prefer visual editing and near-identical pages across languages |
| Cloud translation service (for example Weglot) | Translations stored and served through an external service on a subscription | Teams wanting quick setup and managed machine translation |
| WordPress Multisite | One site per language in a network, connected by a plugin such as MultilingualPress | Organizations with very different content or separate teams per language |
For most UAE business sites we favor a single installation with a translation plugin. Each tool has different licensing, pricing models and add-ons, so check current plans with the vendor before deciding. Avoid switching later: moving between translation systems is possible, but it is a real migration project.
Step 3: Set the URL structure
Each language needs its own crawlable URL. The main options are:
- Subdirectories: example.ae/en/ and example.ae/ar/. Simple to manage, share one domain’s authority and suit most businesses.
- Subdomains: en.example.ae and ar.example.ae. Workable, but treated more like separate sites and slightly more complex to configure.
- Separate domains: useful for distinct country brands, but more costly to build authority for.
- URL parameters: a lang parameter added to the address. Supported by some plugins, but not recommended for search.
Subdirectories are the default recommendation. Also decide whether to translate URL slugs. Arabic slugs are readable to Arabic users and can support search relevance, though they appear percent-encoded when copied into some tools. Either approach can work; what matters is consistency.
Step 4: Install and configure the translation layer
Once the plugin is installed, work through its settings methodically:
- Add languages and set the default. Confirm Arabic uses a right-to-left locale so WordPress loads RTL styles.
- Set URL format to match Step 3.
- Choose what is translatable: pages, posts, custom post types such as projects or services, taxonomies and custom fields.
- Configure the language switcher: position it in the header, show language names in their own script and link to the equivalent page rather than the homepage.
- Decide on browser language detection: keep any automatic behavior light, and never trap users or search engines in one language.
Step 5: Translate content, strings and media
Content is only part of the job. A multilingual WordPress website also contains hundreds of interface strings that come from the theme and plugins.
Pages, posts and custom fields
Translate pages in order of commercial value: homepage, services, contact, key landing pages and then supporting content. For sites built with Advanced Custom Fields or a page builder, confirm the translation plugin supports those fields; most major plugins have integrations, but configuration matters.
Theme and plugin strings
Buttons, labels, footer text and form messages often come from the theme or plugins. Translation plugins include string translation tools, and Loco Translate can edit standard translation files directly. Check cart messages, search results, 404 pages and email notifications, which are commonly missed.
Menus, widgets and media
Create a separate menu for each language, since menu labels and structure often differ. Translate image alt text and captions, and produce language versions of any image containing text, such as banners.
Step 6: Handle RTL, forms and commerce
An Arabic version is more than translated text. Test the RTL layout on every template: headers, mega menus, sliders, icons with direction, tables and form fields. Themes vary widely in RTL quality, so choose one with proper RTL support before building.
- Forms: translate labels, placeholders, validation errors, confirmation messages and auto-replies. Tag each submission with its language so your team replies correctly.
- WooCommerce: products, attributes, variations, shipping labels and transactional emails all need translation. WPML offers WooCommerce Multilingual and Polylang has a paid WooCommerce add-on; check compatibility with your payment gateway and any checkout plugins.
- WhatsApp and chat: set prefilled messages and chat greetings per language.
Step 7: Configure SEO and test before launch
Search visibility depends on each language being clearly identified. Major translation plugins add hreflang annotations automatically and integrate with Yoast SEO and Rank Math for per-language titles, descriptions and sitemaps. Write metadata per language from genuine keyword research rather than translating the English versions.
Before launch, run a checklist across both languages:
- Every page has a working equivalent or a deliberate exclusion.
- The switcher lands on the matching page.
- Hreflang tags reference each other correctly and include x-default where appropriate.
- Forms submit, auto-reply and route correctly in each language.
- Page caching stores separate versions per language.
- RTL layout is correct on mobile as well as desktop.
Keep it maintained
Set a publishing rule so new content does not drift into one language only, and review translations when source pages change. Most translation plugins flag outdated translations, which makes this manageable.
Frequently asked questions
Which plugin is best for a multilingual WordPress website?
It depends on the site. WPML and Polylang suit most business sites and stores that need translations as separate, editable posts. TranslatePress suits teams who prefer translating visually on the page. Weglot suits those wanting a managed cloud service. Match the tool to your content types, page builder, e-commerce needs and who will maintain translations.
Should I use subdirectories or subdomains for languages?
Subdirectories such as /en/ and /ar/ are the usual recommendation. They keep all languages on one domain, are straightforward to set up with translation plugins and are easy for search engines to understand with hreflang. Subdomains and separate domains are valid for specific cases, such as distinct regional brands, but add complexity.
Can I add Arabic to an existing English WordPress site?
Yes. A translation plugin can be added to an established site, and English URLs can usually stay as they are while Arabic is added under its own path. The main work is checking that the theme handles RTL properly, translating strings and forms, and adding Arabic metadata. Test on a staging copy first.
Does a multilingual site slow WordPress down?
Translation plugins add some database queries, and the impact varies by plugin and configuration. With good hosting, page caching configured per language and a lean theme, most multilingual sites perform well. Test speed on each language version, since Arabic pages may load extra fonts that need optimizing.
Building for every language from day one
A well-built multilingual WordPress website gives each audience a complete, credible experience while keeping management in one place. The work comes down to a clear plan, a suitable translation architecture, careful handling of strings, RTL and forms, and SEO configured for each language.
If you are planning an Arabic and English WordPress site, or adding a language to an existing one, we would be glad to discuss the right structure for your content and team.
