Update your WordPress site without calling a developer.

One site, one install, two locales. A multilingual layer keeps both versions of a page linked, switches the reading direction with the language, and gives each locale its own address so search treats them as two pages rather than one. What decides whether that actually works is the theme: it either ships a maintained right-to-left stylesheet or it does not, and no plugin can invent a layout the theme never had. Two separate installs double the work and split the maintenance, which is why we only recommend it when the two audiences are genuinely different businesses. When the Arabic layout itself has to be decided is answered on website design, and the typeface pairing behind it on brand identity design.

Yes, and that is a build decision rather than a WordPress one. The same platform can hand your team a block editor, a page builder canvas or a set of named fields, and those are three very different jobs for someone who writes rather than codes. We model the content first, so a service page is filled in like a form instead of composed on an empty canvas, and we walk the people who will publish through it before the theme is finished. The test we hold ourselves to is whether a coordinator can add a page in their first week without asking us anything.

Three, and the smallest is usually where to start. The first is to keep the builder and lock it down: fix the templates, strip the widgets nobody uses, and give your team a short list of what they may safely edit. The second is to rebuild the page types as blocks and move the content across, which is the common answer when the pages are all the same shape underneath. The third is a full rebuild, and it is only right when the layouts carry logic nobody can read or the licences holding them together have lapsed. We say which of the three we would do before quoting any of them, and if the real complaint is that the site is slow rather than that nobody can change it, that is a measurement job before it is a rebuild.

All of it, and the part that gets missed is the licences. A WordPress site usually runs on a paid theme and three or four paid plugins, and every one of those renews on an account somebody owns. We open them in your name, hand over the renewal dates with the site, and give you an administrator account rather than a lesser role labelled as one. The domain is worth checking early too, since a name directly under .ae is open to any registrant while a .co.ae wants a trade licence behind it. Where a previous supplier is holding the hosting or the domain, getting those back is a separate exercise covered on website development.

A CDN handles delivery; the origin region decides everything WordPress cannot cache. Images, stylesheets and cached pages already arrive from an edge in Dubai whatever continent the server sits on, so on a brochure site the origin matters less than the hosting invoice implies. What still waits on the origin is what WordPress builds on every request: a search, a form submission, anything behind a login, and the admin your own team publishes in. That last one is the reason this question has a different answer for WordPress than for a static site, because a marketing manager feels the distance on every save long before a visitor feels it on a page. AWS has run an in-country region, me-central-1, since 29 August 2022, and local managed hosts sit on comparable infrastructure. Move for residency, or because publishing is slow. Do not move expecting cached pages to arrive faster, because they already do.

Whoever the handover names, and if the handover names nobody then the answer is nobody. WordPress runs more of the web than anything else, which is why an install left alone is the ordinary way a site is broken into, and why updates are not something a build can finish. So the handover states who applies core and plugin updates, how often, who is called when an update breaks a page, and where the backup is restored from. That holder can be your own team and we write it down either way. Hardening the install and responding to an incident are separate work with a separate scope.

Four things, and the page count is not one of them. How many page types the site needs, whether the layout has to work in both reading directions, how much of the content and photography already exists, and how much of the publishing your own team wants to do without us. There is no standard rate in this market, which is why two quotes for the same brief rarely resemble each other and why a number on its own tells you very little about what you are buying. We scope against those four and put the figure in writing before anything is built. What a first build involves for a company trading inside one emirate is set out on web design in Dubai.

WordPress earns its place when the site is content-led and the people updating it are not developers, which describes most companies here running a marketing manager and a coordinator between them. It is the wrong answer when the site has to stay in step with a system the business already runs, when the content model matters more than the writing, or when a second surface such as an app has to read the same content. Who publishes, and how often, is what settles it. We say which case you are in on the first call rather than after the quote, and what a build looks like on the other answer is set out on the website design and development pillar.