Website redesign in Dubai: when it is due and what it costs

A full website redesign in Dubai runs roughly AED 4,000 to 10,000 for a small brochure site, AED 15,000 to 40,000 for a mid-size corporate site with content migration, and AED 30,000 to 110,000 and up for e-commerce with catalogue and payment integrations. Adding a proper Arabic version usually adds 30 to 50 percent on top. Those are reported Dubai market bands, not our rate card.

The harder question is whether you need one at all. Plenty of Dubai businesses pay AED 40,000 to rebuild a site whose real problem was a 6-second mobile load and a contact form nobody could submit on an iPhone. That is a two-week fix, not a three-month project.

A website redesign is a rebuild of structure, templates and often URLs. A refresh is a visual and performance update on the existing structure, with the URLs untouched. The difference matters because URL changes are what put your organic traffic at risk, and nothing else in the project comes close.

Signs a redesign is actually due

Look at numbers, not at whether the design feels dated. Five signals hold up in practice.

Start with mobile LCP. Open PageSpeed Insights and read the field data section, which is real Chrome user data rather than the lab score. If Largest Contentful Paint on mobile sits above 4 seconds while 70 to 85 percent of your UAE traffic arrives on a phone, you are losing sessions before the page paints. Sometimes that is fixable inside the existing build. When it comes out of a page builder stacking six nested containers per section, it is not.

Next, pull 12 months of GA4. Sessions flat or growing while the conversion rate falls quarter on quarter means the site has stopped matching what people arrive expecting. That is a structure problem, and structure problems do not respond to new colours.

Then compare devices. Some desktop advantage is normal. A site converting at 0.3 percent on mobile against 1.4 percent on desktop is broken somewhere specific: a form, a filter, a sticky header eating half the viewport.

The fourth signal is the stack. WordPress on an abandoned ThemeForest theme with a PHP version past end of life, Magento 1, an AngularJS front end. Once security updates stop, you are no longer choosing whether to rebuild, only when.

The fifth is operational and the one owners underrate. If nobody on your team can publish a landing page, change a price or add a service without a three-day developer queue, the site is a cost centre. That alone justifies a rebuild on a modern CMS more often than any visual argument does.

One signal that gets misread: losing positions after a Google core update. That is usually a content and E-E-A-T issue rather than a design one, and a redesign will not fix it. Diagnose it with an SEO review of content and technical health before you touch the templates.

When you do not need a redesign

If traffic is stable, mobile LCP is already under 2.5 seconds, the stack is supported, and your complaint is that the design looks like 2021, buy a refresh instead. It costs a fraction and carries no ranking risk.

A refresh keeps the URL structure and the CMS. Inside that constraint you can change a surprising amount. The figures below are reported Dubai market bands, not a quote:

Refresh scope	What it fixes	Reported band (AED)
Typography, colour system, spacing	Dated look, weak hierarchy	3,000 – 8,000
Above-fold rebuild on top 5 landing pages	Bounce on paid and organic entry pages	4,000 – 12,000
Image compression, script audit, font subsetting	Mobile load time, Core Web Vitals	3,000 – 9,000
Forms, mobile navigation, WhatsApp handoff	Lead capture on mobile	2,500 – 7,000
New photography and copy on key pages	Credibility, message match	Varies by shoot scope

Those rows are per scope. Combine two or three of them and a typical refresh lands between AED 6,000 and 20,000, against two to four weeks of calendar time. Because no URL moves, your organic traffic does not move either.

I will not quote you an uplift percentage for a refresh, because the honest answer is that it depends entirely on what was broken. What I can say from running these projects is that the tightly scoped ones are the only ones you can learn from. Change five templates and you know which change moved the form submissions. Change layout, copy and URLs in a single release and you get one number at the end with no way to attribute it.

The test is simple. Write down the three business outcomes you want. If all three can be reached without changing the URL structure or the CMS, you want a refresh. Send us the URL and we will tell you which side of that line you are on: message the team.

What a redesign includes and what it costs in AED

Prices in Dubai vary more by who does the work than by what the work is. A freelancer on Upwork, a five-person studio in Business Bay and a full agency will quote the same scope with a spread of three times or more between the ends.

Project type	Reported Dubai band (AED)	What sits inside
Small brochure redesign, 5–10 pages	4,000 – 10,000	New design, responsive build, forms, content reused, same URLs
Mid-size corporate, 20–60 pages, content migration	15,000 – 40,000	Discovery, IA, custom design, CMS build, migration, redirect map
E-commerce redesign with integrations	30,000 – 110,000+	Catalogue migration, payment gateway, CRM and inventory hooks, checkout rebuild
Multilingual with Arabic and RTL	Add 30–50% to the band above	Translation, mirrored layouts, Arabic typography, BiDi QA, hreflang

Two notes on those numbers. The e-commerce floor sits higher than the AED 15,000 floor we quote for a new store in our breakdown of what a business website costs in Dubai, and the reason is migration: moving 400 SKUs with their variants, reviews and URL history is work that a fresh store does not have. Second, the freelancer end of each band is real but narrow. It works when the scope is genuinely a template swap. It stops working the moment somebody has to own a redirect map.

Most redesign conversations reach us from the marketing side rather than the design side. We run paid and organic for premium retail and e-commerce brands in the UAE (Fabiana Filippi, Rayhaan, DSQ Cosmetics, Toktam Jewelry among them), and the pattern repeats: the ad account is fine, the traffic is fine, and the site is the bottleneck. That is a useful diagnostic position, because it means the redesign brief starts from what the pages have to do commercially instead of from a moodboard.

What a serious quote should itemise: discovery and analytics review, information architecture and URL mapping, UX wireframes, visual design, front-end build, CMS integration, content migration, redirect implementation, pre-launch QA, and a post-launch monitoring window. If a quote is one line saying "website redesign, AED 22,000", the parts you care about are the ones not written down. Our own scoping notes for web build and redesign work itemise every one of those lines before a price appears.

What pushes the cost up

Most of the spread inside a band traces back to the same short list.

Arabic and RTL

An Arabic version is not a translation dropped into the same layout. The entire interface mirrors: navigation, sidebars, breadcrumbs, form labels, progress indicators, directional icons. Logos, clocks and media playback controls do not mirror. Getting that distinction wrong is the single most common tell of a cheap Arabic build.

The technical work is specific. The document needs dir="rtl", and the CSS needs logical properties (margin-inline-start, padding-inline-end, text-align: start) instead of hardcoded left and right, or half the layout collapses. Arabic script joins, so letter-spacing has to go to zero or the words visibly break apart. text-transform: uppercase does nothing in Arabic, so any button styled that way loses its visual weight. Line height needs more room than Latin text for diacritics and descenders, typically 10 to 20 percent more.

Then there is mixed-direction text. Arabic paragraphs in a Dubai context are full of Latin fragments: brand names, "AED 1,500", phone numbers, email addresses. The Unicode bidirectional algorithm handles most of it, but punctuation at the boundary flips in ways that look fine to a developer who does not read Arabic and wrong to every customer who does. Wrapping those fragments in <bdi> or dir="auto" fixes it. Catching it requires a QA pass by somebody who reads Arabic, which is a line item most quotes leave out.

Font choice matters more than in English. System fallbacks for Arabic render poorly across devices, so you specify a real webfont (Noto Naskh Arabic, IBM Plex Sans Arabic, Cairo and similar) and you subset it, because unsubsetted Arabic font files are heavy. Finally, both language versions need reciprocal hreflang tags (ar-AE and en-AE, plus x-default) or Google serves the wrong version to the wrong user.

Integrations

Every system the site talks to is a separate project inside the project. A payment gateway (Network International, Telr, PayTabs, Stripe) needs merchant onboarding, test transactions and 3D Secure handling. CRM handoff needs field mapping and a plan for what happens when the API is down. Inventory sync, shipping rates, WhatsApp lead routing, booking calendars, invoicing: each one adds days and each one adds a failure mode you only discover in production.

Catalogue and content migration

Moving 40 pages is an afternoon. Moving 400 product pages with variants, images, meta descriptions, reviews and URL history is where e-commerce redesigns overrun. Ask for a migration plan with a row count before you sign, not after.

If your project touches two of those three, plan the budget at the upper half of the band. We scope Arabic and integration work separately so the number is visible rather than buried: ask for a scoped quote.

Timeline and phases

A redesign is discovery, architecture, design, build, migration, QA, launch, and a monitoring window. The phases overlap, but the sequence does not change.

Phase	Small site	Mid corporate	E-commerce
Discovery, analytics and GSC audit	3–5 days	1–2 weeks	2 weeks
IA, URL map, redirect map	2–3 days	1–2 weeks	2–3 weeks
Design	1–2 weeks	2–4 weeks	3–5 weeks
Build and CMS	1–2 weeks	3–6 weeks	6–10 weeks
Content migration	3–5 days	1–3 weeks	3–6 weeks
Pre-launch QA and staging crawl	2–3 days	1 week	1–2 weeks
Total	4–6 weeks	8–12 weeks	12–20 weeks

Arabic adds two to four weeks, mostly in translation review and BiDi QA rather than in development. Add client review cycles honestly: a project with a five-person approval committee runs 30 to 50 percent longer than the same project with one decision maker, and no agency can compress that for you.

Avoid launching into a period you cannot monitor. Ramadan (expected to begin around 6 to 8 February 2027), the last two weeks of December, and the opening week of a major campaign are all poor launch windows for different reasons. If Q4 is your season, launch in September and let the site settle before the spend goes up.

How to not lose organic traffic in the move

Redesigns fail here, and they fail the same way every time: nobody wrote the redirect map until after the site went live.

Before development finishes:

1. Export every indexed URL. Google Search Console, Performance report, Pages tab, 16-month window, export to CSV. Then the Links report for your most-linked pages. Then crawl the live site with Screaming Frog or Sitebulb and save the crawl. That is your inventory, and you cannot redirect what you never listed.
2. Map old to new, one to one. Every URL carrying clicks, impressions or backlinks gets a specific destination. Redirecting everything to the homepage is not a plan; Google treats bulk homepage redirects as soft 404s and drops them.
3. Use 301, never 302, and allow no chains. A pointing to B pointing to C leaks signal and slows crawling. Every old URL points straight at its final destination.
4. Keep the copy on your top pages. Change the URL, the design and the body copy of a ranking page in one release, watch it drop, and you will never know which change did it. Move the URL first and rewrite a month later.

At launch:

5. Check robots.txt. The most common launch disaster, in Dubai and everywhere else, is a staging Disallow: / shipping to production. Check it in the first five minutes after go-live, then check the templates for leftover noindex meta tags.
6. Add self-referencing canonicals on every new URL and submit a fresh XML sitemap in GSC. Temporarily submitting a sitemap of the old URLs helps Google find the redirects faster.
7. Use Change of Address in GSC only if the domain itself changed. The tool sits in Search Console settings and needs both properties verified. Same domain with new URLs needs no tool, only the redirects.

For the first two weeks, watch four things daily: the Pages report in GSC for "Not found (404)", Crawl stats for spikes in server errors, clicks by page in the Performance report against the same period last month, and GA4 landing page sessions. Server logs beat all of them if you have access.

A dip is normal. Expect organic clicks to fall 10 to 20 percent for two to six weeks while Google re-crawls and re-evaluates, then recover. A drop past 30 percent, or a dip still there at eight weeks, means something is broken, and it is almost always redirects, robots.txt or a template-level canonical pointing at the wrong URL. If that is where you are now, a technical crawl finds it in a day: get an audit.

Core Web Vitals: why redesigns often get slower

The thresholds Google uses, measured at the 75th percentile of real mobile users: LCP at or under 2.5 seconds, INP at or under 200 milliseconds, CLS at or under 0.1. Field data in PageSpeed Insights runs on a 28-day rolling window, so a fix you ship today shows up in that report a month later. Judge the launch on lab data first, then confirm with field data in week five.

Redesigns get slower because visual ambition arrives as file weight. The recurring offenders: a hero video that ships 8 MB before anyone scrolls, four webfont weights at 20 to 40 KB each where two would do, an animation library pulled in for one fade, a designer's hero image exported at 4 MB instead of a 200 KB WebP, and a third-party stack (chat widget, heatmap, three tracking pixels) adding several hundred KB of JavaScript to every page.

Put the numbers in the brief before design starts, not in QA afterwards. A performance budget of "LCP under 2.5s on a mid-range Android over 4G, total page weight under 1.5 MB" changes what the designer proposes. Added after the design is approved, it turns into a fight nobody wins. The same discipline applies to entry pages built for paid traffic, which is why our notes on landing pages that convert start with load time rather than layout.

What to require from the supplier in writing

Six clauses. None of them are unusual, and a supplier who resists any of them is telling you something.

The redirect map is delivered and approved by you before development ends, as a spreadsheet with old URL, new URL and status code. Not a promise to handle redirects at launch.

You hold owner-level access to Google Search Console, GA4, the domain registrar, the hosting account and the repository. In your company's name, not the agency's. This one costs nothing and saves a great deal when the relationship ends.

Staging is password protected or noindexed, and there is a written pre-launch checklist covering robots.txt, meta robots, canonicals, sitemap, analytics, forms and payment test transactions.

A post-launch report at 14 and 30 days covering 404s, redirect chains, index coverage and Core Web Vitals field data. Written, not a phone call.

A defect window: launch-caused SEO and functional regressions fixed at no extra cost for 30 days after go-live.

Source files and code handed over on final payment. The site is your asset.

If you are still shortlisting suppliers, the criteria for that decision sit in our guide to choosing a web development partner in Dubai rather than here.

FAQ

How do I know it is time to redesign my website? Check five metrics rather than the look. Mobile LCP above 4 seconds in PageSpeed Insights field data, conversion rate falling while traffic holds or grows, mobile converting at less than half of desktop, a CMS or framework no longer receiving security updates, and any content change requiring a developer. Two or more of those together justify a rebuild. One on its own usually points to a targeted fix.

How much does a website redesign cost in Dubai? Reported market bands run AED 4,000 to 10,000 for a small brochure site, AED 15,000 to 40,000 for a mid-size corporate site with content migration, and AED 30,000 to 110,000 or more for e-commerce with catalogue and payment integrations. A proper Arabic version adds roughly 30 to 50 percent. The spread inside each band reflects who does the work, from freelancer to full agency.

Will I lose my Google rankings after a redesign? Only if the migration is handled badly. With a one-to-one 301 redirect map built before launch, no redirect chains, correct canonicals and a clean robots.txt, expect a temporary dip of 10 to 20 percent in organic clicks for two to six weeks, then recovery. Sites that lose rankings permanently almost always skipped the redirect map or shipped a staging robots.txt to production.

How long does a website redesign take in Dubai? Four to six weeks for a small brochure site, eight to twelve weeks for a mid-size corporate site with content migration, and twelve to twenty weeks for e-commerce with integrations. An Arabic version adds two to four weeks. Multi-stakeholder approval cycles extend all of those by 30 to 50 percent.

Redesign or refresh: which do I need? If the URL structure and CMS can stay as they are while you still reach your business goals, you need a refresh. A single-scope refresh starts around AED 2,500, and a combined visual plus performance pass typically lands between AED 6,000 and 20,000 over two to four weeks with no SEO risk, because no URL moves. A redesign is warranted when the structure, the platform or the URL architecture itself is the constraint.

Do I need an Arabic version of my website? It depends on the audience, not on a rule. If you sell to UAE government entities, to family businesses, or to a consumer segment outside the expat professional bracket, Arabic changes conversion. If your buyers are international B2B or the expat market, English usually carries the site. Half-built Arabic, meaning machine translation in a mirrored-but-unfixed layout, damages credibility more than having no Arabic at all.

What is a 301 redirect and why does it matter in a redesign? A 301 is a server response telling browsers and search engines that a page has moved permanently to a new address, and it passes the ranking signals of the old URL to the new one. In a redesign that changes URLs, the 301 map is the mechanism that carries your accumulated organic authority across. Without it, every old URL returns a 404 and the equity built over years is gone.

My traffic dropped after launch. What do I check first? In order: robots.txt for a Disallow: / that shipped from staging, page templates for leftover noindex meta tags, the GSC Pages report for a spike in "Not found (404)", canonical tags pointing at old or wrong URLs, and the redirect map for chains or URLs that were never mapped. That sequence catches the large majority of post-launch drops, and all five are checkable within a working day.

Written by Artur Gall, CEO and founder of SkyLight Marketing.