WordPress in the UAE, where the multilingual plugin is the whole decision
WordPress can run a bilingual UAE site well, but the decision that determines how well is the multilingual layer. WPML and Polylang change how content is stored, how the site is backed up and migrated, and how much a future redesign costs. In a market where the person managing the site frequently changes, the second decision that matters is who holds responsibility for updates.
WordPress is the most common platform we are asked to work on in the Emirates, usually because a business already has a site on it and wants Arabic added, or wants the site to stop being slow. Both requests lead to the same two questions, and neither is about WordPress itself. What is the multilingual layer, and who is responsible for updating the thing after we leave? Theme, plugins and hosting are all downstream of those two answers.
A bilingual WordPress site accumulates a particular kind of debt. The multilingual plugin becomes load-bearing: it decides how posts are stored, how URLs are formed, how the sitemap is generated and what hreflang is emitted. Moving away from it later is a migration, not a settings change. Meanwhile the theme was chosen for its English demo and has partial right-to-left support, so Arabic pages are nearly right and visibly not. And because expatriate staff turnover is high here, the person who knew which plugins mattered has often left, so updates stop, and an unmaintained WordPress site is not an old site. It is an exposed one.
When this work makes sense
Questions worth asking any supplier
Which multilingual plugin, and why that one? The answer shapes storage, URLs, hreflang and the cost of your next redesign. "Whichever we normally use" is not a reason.
Does the theme support right-to-left natively, or through a stylesheet someone added? Ask to see an Arabic page on the actual theme before the licence is bought.
Who is responsible for core, theme and plugin updates after launch, named, in writing, with a cadence? Unowned WordPress becomes a security problem within months, not years.
How many plugins does the proposal require, and what happens if one is abandoned? Every plugin is a dependency on a third party's continued interest.
Can your team publish an Arabic page end to end without a developer? If not, the bilingual site will drift into a bilingual homepage and an English site behind it.
Deliverables
Multilingual setup with the plugin chosen deliberately and the reasoning documented for whoever inherits the site
Theme work so Arabic pages are correct rather than approximately correct, layout, navigation, icons and form alignment
Arabic typography configured for readability: line height, font fallback, and numeral handling in mixed text
Plugin audit with each one justified, and anything abandoned or duplicated removed
Performance work, caching, image handling, database cleanup, measured rather than asserted
A named maintenance arrangement with an update cadence and a staging environment to test in
Editor training so your team can publish in both languages without calling us
Built with
Process
A UAE WordPress engagement starts with an inventory rather than a design. We list every plugin, what it does, when it was last updated and whether anything still depends on it, which on an inherited site typically identifies several that can be removed immediately and one or two that are load-bearing and unmaintained. The multilingual decision is then made explicitly against your publishing reality: how often you will publish in Arabic, and who will do it. A plugin that suits a developer-managed site is the wrong answer for a marketing team that publishes weekly.
The standard nine stages, discovery, strategy, UX/UI, development, content and SEO, testing, launch, measurement and continuous improvement, apply to every project. The paragraph above is what differs for this one.
What moves the number
Pricing depends on scope, functionality, integrations and content requirements. These are the factors that change it most:
Three ways to run a bilingual WordPress site
WPML
Fits: Sites with substantial content in both languages and a translation workflow to manage
Limits: Commercial licence, heavier on the database, and a genuine migration to move away from later
Polylang
Fits: Smaller bilingual sites where the structure is simple and the editing team is small
Limits: Less capable on complex content models; some functionality sits behind the paid tier
Two separate installs
Fits: Cases where the Arabic site is genuinely a different site rather than a translation
Limits: Two of everything to maintain, and hreflang between them has to be managed by hand
Case studies
No published UAE WordPress case study yet. Our Dubai office is in Standard Chartered Tower, Downtown Dubai. Client work will be published when we have permission to name the business and outcomes that can be evidenced rather than described.
MBGDesk operates from 4 offices in India, United States, United Kingdom, United Arab Emirates. We hold no industry certifications and do not imply otherwise.
Frequently asked questions
Can we add Arabic to our existing WordPress site?
Usually, and the real question is what the theme does when you do. We take one representative page, switch it to right-to-left on your actual theme and show you the result before anything is purchased or committed. That half-day tells you whether you are looking at a configuration job or a theme replacement.
WPML or Polylang?
It depends on how much you will publish and who will publish it. WPML handles translation workflow and larger content models better; Polylang is lighter and simpler for a small bilingual site. The wrong answer is whichever one the agency always uses, because you are the one who has to live with the storage model.
Our site has thirty-something plugins. Is that a problem?
It depends entirely on which ones. The number matters less than whether each is maintained, necessary and not duplicating another. An audit usually finds several that can go immediately, and occasionally one that is abandoned upstream and holding something important together, which is worth knowing before it breaks.
Why is our WordPress site slow?
Most often images served at full size, a page builder rendering far more markup than the page needs, and no caching layer. We measure before changing anything, because the obvious culprit and the actual one are frequently different, and a rebuild sold on a guess is an expensive way to find that out.
Who updates the site after launch?
Someone has to, by name and on a schedule. We can do it, or your team can with a staging environment and a documented process. What does not work is leaving it unassigned, which is the state most of the inherited UAE sites we see are in, and it is how a working site becomes a compromised one.
Will our team be able to publish in Arabic themselves?
That is the point of setting the multilingual layer up properly. If publishing an Arabic page requires a developer, the Arabic side of the site stops being updated within a couple of months and you are left with a bilingual homepage. Editor training is part of the handover rather than an extra.
Should we move off WordPress entirely?
Sometimes. If you publish frequently and need non-technical editors, WordPress is usually the right tool. If the site is essentially static and the plugin estate has become the main maintenance burden, a different approach may cost less to run. We will say so if that is what we think, and the reasoning is on our WordPress platform page.
Services that connect to this
Talk to us about this
Tell us what you are trying to build and we will come back with scope, approach and an estimate.