Access first
Domain, hosting, admin and repository ownership. Checked before anything else because it determines what is possible at all, and recovering it takes weeks rather than days.
Platforms · WordPress
WordPress migration in Dubai: rescuing a site someone else built
Auditing an inherited WordPress build, clearing plugin debt, hardening security, and moving off bad hosting. What to fix, what to rebuild, and how to tell which.
- 4.7 Google rating
- 200+ clients
- In Dubai since 2018
45 minutesto a fixed written quote
WordPress migration in Dubai is most of the WordPress work we are asked for, and it is not building a new site. It is taking over one that already exists, usually after the agency that built it has gone quiet, and working out what can be saved. That is a different job from a fresh build and it needs a different first step: an honest audit before anyone promises anything.
WordPress migration in Dubai covers several situations that get described with the same words. Moving hosts. Moving off an abandoned theme. Moving from another platform onto WordPress. Taking ownership from a supplier who will not cooperate. Each has its own risks and they are not interchangeable.
This page is about inherited builds specifically. If you are choosing a platform from scratch, start at choosing a CMS instead, because WordPress may not be the right answer for you.
First
The WordPress migration audit in Dubai, before anything is promised
A day of looking prevents a quarter of expensive surprises.
Every WordPress migration in Dubai starts with the same examination, and the findings determine whether the honest recommendation is repair, partial rebuild or a fresh start. Quoting before this is guessing, and a quote produced without it will change once the work begins.
Access and ownership. Who holds the domain registration, the hosting account, the WordPress administrator login and the code repository if one exists. This is checked first because it determines whether anything else is even possible. A surprising number of UAE businesses discover their domain is registered to a former supplier.
Versions. WordPress core, PHP, the database server, the theme and every plugin. PHP’s own support schedule is public, and a site on an unsupported version is receiving no security fixes at the language level regardless of how current WordPress itself is.
The theme. Whether it is a commercial theme, a page builder, or custom code. Whether the author still ships updates. Whether it has been edited directly, which means updates would overwrite the changes. This single finding decides more rebuild decisions than any other.
The plugin set. What each one does, whether it is maintained, whether two of them duplicate each other, and whether any is abandoned. Abandoned plugins with database access are the most common route into a compromised WordPress site.
The content model. Whether the structure matches what the business now needs, or whether everything has been forced into pages because nobody set up the right content types.
Versions and support
Core, PHP, database, theme and plugins against their own support schedules. Unsupported components receive no security fixes, whatever the dashboard says.
Theme and structure
Whether the theme is maintained and whether it has been edited in place. The finding that most often decides between repair and rebuild.
The usual problem
Plugin debt on an inherited Dubai WordPress site
Plugin debt is what a WordPress migration in Dubai usually exists to clear, and it accumulates when every requirement is met by installing something. It is the defining characteristic of a WordPress site that has had several owners, and clearing it is most of what a WordPress migration in Dubai actually involves.
The pattern is consistent. Someone needed a contact form, so a form plugin went in. Someone needed a slider, so a slider plugin went in. A page builder arrived to make editing easier and brought forty of its own add ons. Two SEO plugins are installed because nobody removed the first when they added the second. A caching plugin fights with the host’s own caching.
The costs are real and they compound. Every plugin is code you did not write, running with full database access, updating on its own schedule. Each adds page weight. Conflicts between them produce faults that are difficult to diagnose because nobody knows which combination causes them. And an abandoned plugin becomes a permanent security exposure the moment a vulnerability is published for it.
Clearing it is unglamorous and finite. Identify what each plugin actually does, remove the duplicates, replace the ones doing trivial jobs with a few lines of theme code, and find maintained alternatives for the abandoned ones. Most sites we inherit lose a third to a half of their plugins with no loss of function.
The one caution is that removing a page builder is not a plugin removal, it is a rebuild of every page it touched, because the content is stored in its own format. That belongs in the rebuild decision rather than the clean up.
WordPress plugin audit questions
- What does this actually do on the live site
- When did the author last ship an update
- Does another installed plugin already do it
- Would a few lines of theme code replace it
- Does it have database write access
- Is it a paid plugin with a lapsed licence
- Does removing it change what visitors see
Security
Hardening after a WordPress migration in Dubai
Most compromises exploit something known and unpatched rather than anything sophisticated.
WordPress publishes its own hardening guidance, and the majority of incidents we are called to trace back to items on that list being ignored rather than to a novel attack.
Update discipline after migration. Core, themes and plugins current, with a route to apply security releases quickly. Automatic updates for minor core releases are sensible; automatic updates for everything on a heavily customised site will eventually break something at an inconvenient moment.
Accounts. Every administrator account belongs to someone who still works with you. Inherited sites routinely carry logins for the previous agency and for staff who left years ago. Remove them, and give editors the editor role rather than administrator.
Authentication. Strong unique passwords and two factor on administrator accounts. The login page is attacked continuously by automated traffic regardless of how obscure your business is, because the attacks are indiscriminate.
File permissions and the hosting. Correct permissions, PHP execution disabled in the uploads directory, and a supported PHP version. Shared hosting where another compromised account can reach your files is a genuine risk in this market and it is not visible from the dashboard.
Backups that have been restored. An untested backup is a hope rather than a plan. The test is whether someone has actually restored it to a staging environment and confirmed the site works.
Where a site handles personal data there is a further consideration. The UAE’s personal data protection framework places obligations on how data is stored and secured, and a contact database sitting in an unmaintained WordPress install is a compliance question as well as a technical one.
Everything current
Core, themes, plugins and PHP on supported versions, with a defined route to apply security releases within days rather than at the next redesign.
Accounts cleaned
Former agencies and departed staff removed, editors given the editor role, two factor on every remaining administrator.
Server side hardening
Correct file permissions, no PHP execution in uploads, a supported PHP version, and hosting that isolates your account from its neighbours.
Backups proven
Offsite, automated, and restored at least once to a staging environment so you know the restore actually works before you need it.
Hosting
WordPress migration in Dubai: moving hosts without losing anything
A large share of WordPress migration work in Dubai is simply a hosting move, usually off shared hosting that has become the site’s main performance problem. Done carefully it is routine; done carelessly it causes an outage and a search visibility dip.
The sequence matters. Build the new environment first and get the site working on it, reachable privately, before anything public changes. Test it properly: every template, the forms actually submitting, the checkout if there is one, and the site in both languages.
Then reduce the domain’s time to live setting a day ahead so the switch propagates quickly. Take a final backup and content freeze. Move the database and files, point the domain, and issue the certificate on the new host before rather than after the switch, because a certificate warning during propagation is what visitors will remember.
Afterwards, check the things that quietly break. Outbound email frequently stops working because the new host handles mail differently, and nobody notices until a customer says they never received a confirmation. Cron jobs that drove scheduled publishing may not have moved. File paths hardcoded by a previous developer may point at the old server.
Since the URLs do not change, search visibility should be unaffected, and Google’s guidance on site moves mainly concerns URL changes rather than hosting. The risk is a slower server or an interruption long enough to be noticed during a crawl.
WordPress migration hosting checklist
- New environment tested privately before any switch
- Every template and form checked, both languages
- Time to live lowered a day ahead
- Final backup and a content freeze
- Certificate issued before the switch, not after
- Outbound email tested on the new host
- Scheduled tasks confirmed running
- Old host kept live for a week as a fallback
The decision
WordPress migration in Dubai: repair or rebuild
The question every audit has to answer, and the one agencies answer dishonestly most often.
In any WordPress migration in Dubai there is a commercial incentive to recommend a rebuild, because a rebuild is a larger project. It is worth knowing that before you receive the recommendation, and worth asking any supplier to justify it against the alternative.
Repair is right when the theme is maintained or is custom code you own and understand, the content structure still matches the business, and the problems are maintenance debt: outdated versions, plugin sprawl, poor hosting, missing security. All of that is fixable in place, usually for a fraction of a rebuild, and without the search visibility risk a rebuild carries.
Rebuild is right when the theme is abandoned by its author and has been edited directly, so nothing can be updated without losing the changes. Or when the content model is fundamentally wrong for what the business now does. Or when a page builder has made every page a proprietary blob that no other tool can read. Or when the code has been customised to the point that any change breaks something elsewhere.
There is a middle route people forget: keep the content and the URLs, replace the theme. This is frequently the right answer and it is rarely offered. The content stays where it is, the addresses do not change so search visibility is preserved, and the presentation layer is rebuilt cleanly. It costs meaningfully less than a full rebuild.
Whatever the answer, it should come with reasoning you can check rather than an assertion. If a supplier cannot explain in plain terms why repair will not work, that is worth pressing on.
Repair
Maintained theme, sound content structure, problems are maintenance debt. Fixable in place, faster, and no search visibility risk from changing URLs.
Re theme without a full WordPress migration
The middle route, rarely offered. URLs and content stay, presentation is rebuilt cleanly. Often the right answer and considerably less than a full rebuild.
Rebuild
Abandoned theme edited in place, wrong content model, or a page builder holding every page in its own format. Justified, and it needs a migration plan.
Coming from elsewhere
WordPress migration in Dubai from another platform
The other kind of WordPress migration in Dubai is moving from a different system entirely: an old bespoke site, a builder platform, Joomla, Drupal, or a static site nobody can edit.
In a WordPress migration the content is the hard part rather than the build. Content in another system is structured that system’s way, and mapping it into WordPress means deciding what becomes a page, what becomes a post, and what needs a custom content type. Doing this thoughtlessly produces a site where everything is a page and nothing can be filtered or listed sensibly.
URLs are the second decision and the one with lasting consequences. Keeping the existing addresses avoids the whole problem, and it is usually possible even when the platform prefers a different pattern. Where they must change, every old address needs a redirect to its specific new one, mapped individually rather than in bulk to the homepage.
Media migration is routinely underestimated. Images embedded with absolute paths to the old domain will break silently. Documents linked from body copy need moving and relinking. On a site with years of content this is the bulk of the work and it does not automate cleanly.
What rarely transfers is functionality. Forms, member areas, calculators and integrations are rebuilt rather than moved, and each needs specifying as though new. A migration quote that does not itemise these has not accounted for them.
WordPress migration inventory
- Every URL, from sitemap, analytics and a crawl
- What each becomes: page, post or custom type
- A redirect mapped for every changed address
- Media files and the links pointing at them
- Forms and where submissions currently go
- Integrations, each specified as new work
- User accounts, if the site has logins
Bilingual
Arabic and English after a WordPress migration
Frequently the weakest part of a site built by someone who did not need to read it.
Bilingual WordPress in Dubai is usually implemented with a translation plugin, and a migration is the moment to examine it, and how well it was set up varies enormously. The audit looks at which plugin, how translations are stored, and whether removing it would strand the Arabic content, which with some implementations it would.
The recurring faults are consistent. Arabic pages carrying English form labels and validation messages, because the plugin translated content but not the theme strings. Layouts that mirror but do not reflow, so mixed direction lines read badly. Fonts without proper Arabic support, so Arabic renders in a system fallback. And hreflang either absent or declared in one direction only, which means it is ignored entirely.
There is also a maintenance question that matters more than the technical one. An Arabic section only stays useful if somebody updates it, and the common state of bilingual UAE sites is an English side that is current and an Arabic side eighteen months behind. That is a process problem rather than a plugin problem, and it is worth resolving during a migration rather than carrying forward.
Where the Arabic content was machine translated at build time, this is the moment to decide whether to keep it. Translated pages match few Arabic searches and read as translated, and the reasoning is set out under Arabic SEO.
Performance
Why a WordPress site awaiting migration is usually slow
The causes are predictable and rarely require a rebuild to fix.
Images
Uploaded at camera or print resolution and resized in the browser. The single most common cause, and fixing it is bulk work rather than clever work.
Plugin weight
Each plugin loading its own stylesheets and scripts on every page, including pages that never use it. Clearing plugin debt usually removes a large share of page weight.
Hosting
Shared hosting with an overloaded neighbour, no object caching, and a database nobody has indexed. Frequently the largest single factor and the least examined.
Server location
A site serving the Gulf from another continent carries latency on every request. No amount of front end work recovers it; regional hosting or a delivery network does.
Measure on field data from real visitors rather than a laboratory score before planning a WordPress migration in Dubai, because your audience’s devices and connections are what count. A WordPress migration in Dubai that moves a site to regional hosting with proper caching frequently produces a larger improvement than any amount of code optimisation, and it costs less. The measurement side belongs with technical SEO.
Working with us
How we run a WordPress migration in Dubai
We start every WordPress migration in Dubai with the audit described above and charge for it as a defined piece of work, because it is genuinely useful on its own. You get a written document covering access and ownership, versions, theme condition, plugin set, security findings, performance causes and a clear recommendation between repair, re theme and rebuild, with the reasoning stated.
If the honest answer is that your site is in reasonable condition and needs a maintenance plan rather than a project, the document says that. It happens more often than the industry admits.
Where work follows, it is quoted separately against the findings rather than as an open ended retainer. Ownership is corrected first if it needs correcting, because everything else depends on it. Then security and versions, then performance, then whatever structural work was agreed.
Everything ends in your name: domain, hosting, repository, logins and documentation, with a recorded walkthrough. Ongoing care afterwards is optional and covered under website maintenance, and nothing we do requires you to keep us.
You get a fixed written quote within 45 minutes during business hours once we have seen the site.
What a WordPress migration needs to start
- The site address
- WordPress administrator access, or the recovery route
- Hosting control panel access if you have it
- Who registered the domain
- Any documentation the previous supplier left
- What is going wrong, in your words
Sequence
How a WordPress migration in Dubai actually runs
Five stages, with a decision point at the end of each.
A WordPress migration in Dubai should never begin with work on the live site. Everything happens on a copy until the moment of switching, which is what makes the process reversible.
Stage one, the audit. Access, versions, theme, plugins, content model, security, performance. Output is a written document and a recommendation. This is where most WordPress migration projects in Dubai should pause, because the finding sometimes changes the plan entirely.
Stage two, a staging copy. A full clone of the live site on a private environment, blocked from search indexing. Every change happens here first. Taking a verified backup before cloning is part of this, not an afterthought.
Stage three, the work. Ownership corrected, versions brought current, plugin debt cleared, security hardened, performance addressed, and whatever structural work was agreed. Each change tested on staging as it lands rather than all at the end.
Stage four, verification. Every template checked, forms actually submitted, both languages walked through on a real phone, and a crawl comparing the staging site against the live one to catch anything that has silently disappeared.
Stage five, the switch. Content freeze, final backup, deploy, certificate confirmed, redirects live if any URLs changed, and the old environment kept available for a week. Then monitoring for a fortnight, because problems from a migration show up within days rather than immediately.
Audit and decide
A written document with a recommendation between repair, re theme and rebuild. A genuine stopping point, not a formality before a preordained project.
Clone to staging
A full private copy, blocked from indexing, with a verified backup taken first. Nothing touches the live site while work is in progress.
Do the work there
Ownership, versions, plugins, security, performance and structure. Tested as each change lands rather than in one pass at the end.
Verify, then switch
Crawl comparison, forms submitted, both languages on a real phone. Then freeze, deploy, and keep the old environment for a week.
What it costs you not to
The price of leaving an inherited site alone
Deferring a WordPress migration in Dubai is a legitimate choice and it is worth understanding what accumulates while you defer.
Security exposure compounds. Each month adds published vulnerabilities for the versions you are running. The risk is not constant; it rises. And a compromised site in the UAE is not only a technical problem where customer data is involved, because the personal data protection framework places obligations on how that data is secured.
Updates get harder. A site two versions behind can usually be brought current in an afternoon. One five years behind may not survive the process at all, because the intermediate steps assume you took them. Deferring converts a small job into a rebuild.
Nobody learns the site. Every month that passes, more of the people who knew how it was built have moved on. Documentation that was thin at handover becomes the only record, and eventually nobody can say why something was done the way it was.
Performance drifts before migration. Content accumulates, images pile up, the database grows, and nothing is ever removed. Sites get slower without anyone changing anything.
None of this means an urgent migration. It means the audit is worth having now even if the work waits, because the decision should be informed rather than deferred by default.
Signs it should not wait
- PHP or WordPress core on an unsupported version
- A plugin abandoned by its author with database access
- Administrator accounts for people who left
- No backup anyone has tested by restoring
- The domain registered to a former supplier
- Customer data held on an unmaintained install
Ownership
Recovering a site from a supplier who has stopped responding
A common enough situation in this market to need its own answer.
A WordPress migration in Dubai sometimes begins with a recovery rather than an audit, because the previous supplier has gone quiet, stopped trading, or is holding access pending a dispute. What is recoverable depends entirely on whose name things are in.
The domain. Any WordPress migration in Dubai checks the registrar record first. If the registrant organisation is your company, you can recover control through the registrar with proof of identity even without the supplier’s cooperation, though it takes time. If the registrant is the supplier, this becomes a negotiation, and for a .ae domain the registry has its own dispute process.
The hosting. If the account is in your company name and billed to your card, the host will restore access with proof. If the site sits inside a reseller account the supplier owns, you cannot get the panel, but you can usually still obtain a copy of your own files and database by asking, since most hosts will assist the site owner.
The site itself. Even with no access at all, a public site can be crawled and its content preserved. That is not a substitute for the database, but it means content is rarely genuinely lost, only the structure and the functionality.
What is usually unrecoverable. Commercial plugin and theme licences bought under the supplier’s account, and any custom code never committed anywhere you can reach. Both have to be repurchased or rewritten, and both should be priced into the recovery.
The practical WordPress advice in Dubai is preventative and it costs nothing. Register the domain in your company name, hold the hosting account yourself, and require repository access at handover. We set every project up that way for exactly this reason.
Check the registrar first
Whose name holds the domain decides how hard the rest becomes. Yours means a slow but certain recovery. Theirs means a negotiation.
Ask the host directly
Even inside a reseller account, most hosts will provide the site owner with a copy of the files and database on proof of ownership.
Price the unrecoverable
Licences bought under their account and uncommitted custom code. Both need repurchasing or rewriting and both belong in the quote.
After the move
Keeping a migrated site from returning to the same state
A WordPress migration in Dubai fixes the condition of a site on the day it completes. Without a routine afterwards, the same debt accumulates and you are back within two years, which is why most sites we inherit have been migrated before.
The routine that prevents a second WordPress migration in Dubai is modest. Core and plugin updates applied on a defined cadence rather than when something breaks, with a staging environment to test anything significant first. Backups running automatically and restored to staging once a quarter so you know they work.
Beyond that, an annual review of the plugin set, because debt returns quietly: someone installs something for a campaign and it stays for five years. A check that no administrator account belongs to somebody who has left. And a note of which commercial licences renew and when, since a lapsed licence means a plugin stops receiving security updates while continuing to run.
Someone has to own this. It is perhaps an hour a month and the reason sites decay is not cost, it is that the responsibility belongs to nobody in particular once a project finishes. Whether that person is internal or us matters less than that they exist, and the arrangement is covered under website maintenance.
The one thing worth doing immediately after any migration is writing down what was done and why. The next person to touch the site, who may not be you, will otherwise repeat the same discovery work you just paid for.
The monthly routine
- Core and plugin updates on a set cadence
- Anything significant tested on staging first
- Backups verified by restoring, quarterly
- Administrator accounts reviewed
- Commercial licence renewals tracked
- An annual cull of unused plugins
- A written record of what changed and why
Multisite and scale
WordPress migration in Dubai for multiple sites and brands
Groups running several sites face a different version of the same problem.
A WordPress migration in Dubai gets more complicated when the business runs several sites: a group with multiple brands, a developer with a site per project, a franchise with a site per branch. The debt multiplies and so does the decision.
The first WordPress migration question in Dubai is whether these should be separate installations or one multisite network. Multisite shares a single core, theme set and plugin set across every site, which means one update applies everywhere. That is the advantage and it is substantial at scale. The disadvantage is coupling: a plugin conflict affects every site, and moving one site out of a network later is genuinely awkward.
The rule of thumb that holds up is whether the sites are genuinely similar. Eight branch sites sharing a design and differing only in content suit multisite well. Eight unrelated brands with different designs, different requirements and different agencies touching them do not, and separate installations are less trouble despite the duplicated maintenance.
The second question is shared infrastructure regardless of the answer. One hosting arrangement, one backup routine, one update schedule and one place where documentation lives. Most groups we audit have each site on whatever hosting the agency that built it happened to use, which makes every site a separate investigation.
A WordPress migration in Dubai also has a licensing point worth checking early. Commercial themes and plugins are usually licensed per site, and a multisite network or a set of eight installations may need a different licence tier than anyone budgeted for.
Multisite suits
Branch or location sites sharing a design, differing mainly in content. One update applies to all, which at eight or more sites saves considerable maintenance.
Separate installs suit
Unrelated brands with different designs and requirements, especially where different suppliers touch them. Duplicated maintenance beats coupled failure.
Shared infrastructure either way
One host, one backup routine, one update schedule, one documentation location. This is the change that helps most and it is independent of the multisite question.
Check the licences
Commercial themes and plugins licence per site. A network or a set of installs may need a tier nobody budgeted for, and lapsed licences stop security updates.
Costs
What a WordPress migration in Dubai is priced against
The variables that move a quote, so you can read one properly.
Quotes for this work vary widely and the reasons are usually legitimate rather than opportunistic. Knowing the variables lets you compare two proposals that look different on the surface.
Page count and content volume. A forty page site and a four hundred page site are different exercises, mostly because of content checking rather than build work.
Whether URLs change. Keeping them costs almost nothing. Changing them means mapping a redirect for every address, which on a large site is the single biggest line in a WordPress migration quote in Dubai.
Languages. A bilingual site roughly doubles the verification, because every template and every form has to be walked through twice, in two directions.
Custom functionality. Forms, calculators, member areas and integrations are rebuilt rather than moved, and each is priced as new work. A quote that does not itemise these has not looked at them.
The starting condition. A tidy site on current versions is straightforward. One five years behind, with an edited theme and abandoned plugins, may not survive an in place update at all, and that changes the approach rather than only the hours.
Ask any supplier which of these applies to you and how they priced it. A proposal that gives one figure with no breakdown cannot be compared against anything, and it usually means the audit has not happened.
Biggest variable
Whether URLs change. Keeping them is close to free; changing them means a mapped redirect per address and is the largest line on a big site.
Most underestimated
Custom functionality. Forms, calculators, member areas and integrations are rebuilt, not moved, and each needs specifying as new work.
Ask for a breakdown
One figure with no itemisation cannot be compared and usually means nobody has audited the site yet. The breakdown is the useful part.
When a WordPress migration in Dubai is not what you need
If the site is genuinely fine, a WordPress migration in Dubai is not worth buying. Sites get migrated because a new supplier prefers a different setup rather than because anything was wrong, and the business pays for a change it will not notice. A maintenance plan is frequently the correct and much smaller answer.
If WordPress is the wrong platform for what you are now doing, migrating within WordPress postpones the real decision. A business that has outgrown a content system and needs an application should be looking at a framework rather than another WordPress build.
If nobody in your business will maintain it afterwards, the same problems return within two years. A migration fixes the state of a site on the day it finishes, and without a maintenance route it decays from that day. Deciding who owns it matters more than the technical work.
And if the real problem is that the site does not generate enquiries, a cleaner WordPress install will not change that. That is a conversion question and it belongs with conversion work, which is faster and less expensive than any migration.
If you are unsure which applies, send us the address and we will look and tell you plainly, including when the answer is to leave it alone. Our team works with businesses across Dubai and the wider UAE in Arabic and English, and a fixed written proposal follows within 45 minutes during business hours with no obligation.
Straight answers
Frequently asked questions
Our previous agency will not hand over the site. What can we do?
If the domain and hosting are in your company name you generally have the access you need, even without their cooperation. If they hold both, recovery goes through the registrar and the host with proof of ownership, which takes time. Check who your domain is registered to before anything else, because that determines how difficult this becomes.
How do we know if our WordPress site is secure?
The quick signals are whether core, themes and plugins are current, whether any plugin has been abandoned by its author, whether admin accounts exist for people who left, and whether the hosting is running a supported PHP version. Most compromised sites we see were running a plugin nobody had updated in over a year.
Should we repair the site or rebuild it?
Repair when the structure is sound and the problems are maintenance debt. Rebuild when the theme is abandoned, the content model is wrong for what you now need, or the code is so customised that updating anything breaks something. The audit answers this, and it is the first thing we do.
Will moving hosts affect our search visibility?
A move done properly should not, because the URLs do not change. Problems come from missed redirects, a slower server, or the new host serving an expired certificate. All three are avoidable and all three are checked before the switch.
How many plugins is too many?
The count matters less than what they do and whether they are maintained. Forty well maintained plugins can be healthier than eight abandoned ones. What we look at is which are still supported, which duplicate each other, and which are doing something a few lines of theme code would do better.
Sources
- WordPress: Hardening WordPress accessed 27 September 2026
- WordPress: Requirements accessed 27 September 2026
- PHP: Supported Versions accessed 27 September 2026
- WordPress: Backing Up Your WordPress Files accessed 27 September 2026
- Google Search Central: Site moves with URL changes accessed 27 September 2026
- UAE Federal Decree Law No. 45 of 2021 on Personal Data Protection accessed 27 September 2026
Fixed price, in writing
Send your brief. Get a scope and a price within 45 minutes.
- One fixed number, agreed in writing before work starts
- No obligation, and no pressure to sign
- English and Arabic work, with proper right to left layout
- One team for design, marketing, web, media and copy
Got it. Your quote is being written now.
In business hours you will have it within 45 minutes. Check your inbox for the confirmation.