Our site is only 18 months old. Is it too early to redesign it?

No, and 18 months is the ordinary point in this market. What decides it is not the age of the design but whether the company still matches it: an activity added to the licence, a mainland branch, the first clients you can name, a second language that stopped being optional. If none of those has happened, the problem is usually one page rather than the site, and that is worth proving before anything is replaced. Whether the site is losing enquiries for a reason a redesign can address is settled at build a high-converting website.

Will a redesign lose the rankings we have?

Not if every address is mapped before the cutover, and on a site this young there is usually less to map than the question assumes. Each address that exists is matched to where it goes, the redirects are tested before launch, and positions are watched through the move. The larger risk here runs the other way: retiring the two or three pages that were quietly working, because nobody had measured which ones they were. That is why the page-level read comes before any design.

We opened a mainland branch, or added an activity to the licence. Does the site have to change with it?

Yes, and it is the change left until last more often than any other. A free-zone entity generally cannot sell direct to mainland UAE customers without a distributor, a mainland branch, or a permit under Dubai Executive Council Resolution No. 11 of 2025, so on the day one of those lands, every page describing who you serve is out of date and the enquiry routing behind it points at the entity that can no longer take the work. The change is structural rather than cosmetic: routes, service pages, and where a form sends the buyer. What your licence lets the site claim is read in more depth on web design in Dubai.

Redesign or rebuild, and how do you decide?

By what has to change underneath. A redesign keeps the platform and reworks the structure, the content and the interface; a rebuild replaces the platform because it cannot carry what the company now does. The test we apply is whether your own team can add a page type without going back to whoever built the first version. Where the answer is no you are buying a rebuild whether or not anyone calls it one, and the build side of that work is scoped separately.

What happens to the content and the URLs we already have?

Both are inventoried before anything is drawn. Every page is crawled, joined to its search and analytics record, and sorted into keep, rewrite, merge or retire, and the address map is produced from that sort rather than from the new navigation. Content that earns its place moves across even where it does not suit the new layout, and anything retired keeps a redirect to the closest page that is still live. Where the site is young enough that almost nothing is indexed, we say so instead of building a migration around it.

What does a redesign cost compared with a first build?

Less than a first build where the structure survives the change, and more where it does not. Four things move the figure: how much of the sitemap still fits the entity, whether there is a search history to migrate, how much content has to be rewritten for the company as it is now, and whether your team can still edit the current platform. There is no standard rate in this market, so we scope against those four and put the number in writing before any design starts. The drivers for a first build are a different list, answered on website design.

Can you redesign the English site now and add Arabic later?

Yes, and what decides the cost of later is what this rebuild reserves now. Arabic is a layout state and a route structure before it is a translation, so a rebuild that specifies the mirrored component set and puts every route under a locale segment turns the Arabic version into content work. A rebuild that does not is the reason Arabic gets quoted as a second redesign a year afterwards. We write down which of the two you are buying, at the point the structure is agreed rather than at the point the invoice arrives.

Website redesign · UAE

Website redesign that matches the company now.

Most sites here are replaced in the second year, not the fifth. Webzenia starts by reading what changed in the company, then says which parts of the site still hold.

Get a read on what should actually change

What a redesign replaces

What a website redesign replaces.

A website redesign here rarely starts with the design. It starts with an event in the company, a short list of what still works, and a decision about what has to survive the move.

What changed.

An activity added to the licence, a branch, a new kind of buyer, clients you can finally name, a second language. The trigger is an event with a date on it, which makes it checkable rather than a matter of taste.

What is worth keeping.

The pages that earn enquiries, the copy that is still true, and the structure that still fits. On a site this young the list is shorter than anyone expects, and it is the part nobody has measured.

What must survive the move.

The addresses that exist, the pages an ad set or a listing already points at, and any position earned since launch. Where that list is genuinely short we say so, rather than pricing a migration around it.

Two answers to the same complaint

A redesign or a fix.

Not every site that stopped fitting needs replacing. The question is how much of it the change actually reached.

	A targeted fixOne thing is wrong, and you know which	A redesignThe company changed shape, the site did not
What set it off	A number moved. The page got slow, or the form stopped arriving.	An event. A new activity, a branch, a client list, a second language.
The first question	Which page, which step, and what it used to do.	What the company sells now, and which entity may sell it.
What it touches	One template, one flow, sometimes one field.	The structure and the routes, which is why it is the larger job.
Your addresses	Unchanged. Nothing needs mapping and nothing needs a redirect.	They move, so every one is mapped before the cutover, not after.
When it is wrong	When the site describes a company that no longer exists. A faster page still says the wrong thing.	When one page, one form or one load time is the whole problem.

Which one fits you.

We scope the read before the work, because from the outside the two look identical: what changed, what still earns its place, and what a fix alone would leave unsolved. The read is the deliverable either way, and it tells you which column you are in. If nothing has been built yet this is a first build rather than a redesign, and how one is scoped here is a different conversation. If the site was built for the market you came from and ranks there rather than here, the answer is international SEO, not a rebuild.

The UAE context

Why redesigns come in year two.

Webzenia has worked with Gulf clients since 2018. Three things make a redesign in this market start earlier, and for a different reason.

01of 03
An event, not an anniversaryWhat sets the date
A company event triggers it.
A JLT commodities trader under DMCC adds an activity to its licence. A Deira trading house on a DET mainland licence opens a branch. A second language stops being optional. Each has a date on it. Buyers still search for a web design company, not a redesign.
Our methodThe read starts with the last twelve months of the company, not with the date the site launched.
02of 03
Less to protect is not nothingWhere the risk moved
A young site still has pages worth keeping.
By month 18 a first site usually holds a few pages doing real work: one that ranks for a service term, one an ad set has been pointed at all year. Nobody recorded which, so the risk at rebuild is discarding them rather than losing a redirect.
Our methodPage-level value is measured before anything is retired, not read off the new site afterwards.
03of 03
The first site had no briefQ2 2026 leasing data
Your first site had no brief.
Two-thirds of Q2 2026 Dubai office leasing was in units under 500 sq ft, so a Business Bay brokerage on a DET mainland licence commissions its site to a deadline. A site bought that way has no brief behind it, and the only description of the problem available later is that nobody likes it.
Our methodThe first deliverable is the brief the first build never had, written before anything is drawn.

The scope

The redesign, part by part.

Six pieces of work. The first two decide how much of the other four you actually need.

An audit and a baseline.

The numbers the new site will be judged against, read beside the licence, the entities and what the company is now allowed to claim

BaselineLicence read

A keep, rebuild and retire list.

Every page sorted into what earns its place, what is rebuilt and what goes, decided from the data rather than from the meeting

Page by pageDecided first

The company as it is now.

Identity, proof and claims brought up to the entity that exists today, including the clients and coverage you can finally reference

IdentityClaims

A rebuild your team can change.

A faster site that your own people can add a page to, rather than one that needs the developer who built the first version

Core Web VitalsEditable

Every address mapped.

Every address that exists mapped to where it goes, and where that list is genuinely short, a sentence saying so instead of a migration line

RedirectsTested first

Cut over, then measured.

Launched against the baseline recorded before anything moved, so the redesign is held to a number rather than to an opinion

BaselineAfter launch

Our stack

The tools we decide with.

The kit behind a redesign that starts as a diagnosis. Select one to see why it earns its place, and what we do with it that most do not.

Screaming Frog

Why Screaming Frog

A crawl is the only honest inventory of a site nobody documented. It returns every address, template, title and redirect that actually exists, including the pages the current team has forgotten are live.

How we excel

We crawl before the first conversation about design, then join the crawl to the analytics and search data so each address arrives with what it is worth attached. That joined list is what the keep decision is made from.

Full inventoryRedirect auditCoverage

Screaming FrogEvery URL

SitebulbEvery URL

A CMS page listPublished only

The old sitemapOften stale

How the redesign runs

Decide, rebuild, then cut over.

Three phases, and the first one can end the engagement. If a targeted fix is the right answer, that is the output.

01Weeks 1 to 2Decided

Read the company and the site.

We start with the licence, the entities and what you are now permitted to sell, then crawl the site and join every address to its search and analytics record. What comes out is a keep, rebuild and retire list with a reason against each line. Where the list says a fix, we quote the fix and the engagement stops there.

Read firstThe licence and the entities
OutputKeep, rebuild, retire
BaselineRecorded and handed over

02Weeks 3 to 6Built

Rebuild what the decision replaced.

The structure is redrawn against the entity that exists now, and the pages the list marked keep move across with their content and their addresses intact. Everything replaced is drawn beside the page it replaces, so the review is about the decision rather than the styling.

StructureRedrawn against the entity
Kept pagesContent and address intact
ReviewOld page beside new

03Week 7 onwardMeasured

Move the addresses, read the numbers.

Where there is a search history the cutover carries a full redirect map, tested before launch and monitored through it. Where there is almost none, the same phase is a content and decision map instead, and we say that rather than pricing a migration. Either way the new site is read against the baseline from week one.

With a historyFull redirect map, tested
Without oneA content and decision map
Judged onThe baseline, not the launch

Judged against the baseline recorded before anything moved, never against the new homepage.

Measured against the old site

Keep list firstAddresses mappedBaseline held

Our commitment

Our promises on the migration.

A redesign is the one project where you can end up with less than you started with. These four are what we ask to be held to.

Nothing retired before it is measured.
Traffic, enquiries and entry points are recorded page by page before anything is removed, and a page that earns its place comes across whether or not it suits the new design. A page nobody measured is not a page nobody needs.
Every address is mapped.
You receive the redirect map before the cutover, line by line. Where the site has almost nothing indexed and nothing pointing at it, we say so and scope the move accordingly rather than billing for a migration with nothing to migrate.
The baseline is recorded first.
Enquiries, entry pages, load time and positions are taken from the old site first and handed to you in writing. The new site is then judged against those, not against the meeting where the design was approved.
We recommend the fix when it fits.
Where one page, one form or one load time is the whole problem, we say so, quote that instead and leave the rest alone. A redesign sold to a company that needed a fix is paid for twice and solves the problem once.

Common questions

Website redesign in the UAE, answered

No, and 18 months is the ordinary point in this market. What decides it is not the age of the design but whether the company still matches it: an activity added to the licence, a mainland branch, the first clients you can name, a second language that stopped being optional. If none of those has happened, the problem is usually one page rather than the site, and that is worth proving before anything is replaced. Whether the site is losing enquiries for a reason a redesign can address is settled at build a high-converting website.
FAQ · 01
Not if every address is mapped before the cutover, and on a site this young there is usually less to map than the question assumes. Each address that exists is matched to where it goes, the redirects are tested before launch, and positions are watched through the move. The larger risk here runs the other way: retiring the two or three pages that were quietly working, because nobody had measured which ones they were. That is why the page-level read comes before any design.
FAQ · 02
Yes, and it is the change left until last more often than any other. A free-zone entity generally cannot sell direct to mainland UAE customers without a distributor, a mainland branch, or a permit under Dubai Executive Council Resolution No. 11 of 2025, so on the day one of those lands, every page describing who you serve is out of date and the enquiry routing behind it points at the entity that can no longer take the work. The change is structural rather than cosmetic: routes, service pages, and where a form sends the buyer. What your licence lets the site claim is read in more depth on web design in Dubai.
FAQ · 03
By what has to change underneath. A redesign keeps the platform and reworks the structure, the content and the interface; a rebuild replaces the platform because it cannot carry what the company now does. The test we apply is whether your own team can add a page type without going back to whoever built the first version. Where the answer is no you are buying a rebuild whether or not anyone calls it one, and the build side of that work is scoped separately.
FAQ · 04
Both are inventoried before anything is drawn. Every page is crawled, joined to its search and analytics record, and sorted into keep, rewrite, merge or retire, and the address map is produced from that sort rather than from the new navigation. Content that earns its place moves across even where it does not suit the new layout, and anything retired keeps a redirect to the closest page that is still live. Where the site is young enough that almost nothing is indexed, we say so instead of building a migration around it.
FAQ · 05
Less than a first build where the structure survives the change, and more where it does not. Four things move the figure: how much of the sitemap still fits the entity, whether there is a search history to migrate, how much content has to be rewritten for the company as it is now, and whether your team can still edit the current platform. There is no standard rate in this market, so we scope against those four and put the number in writing before any design starts. The drivers for a first build are a different list, answered on website design.
FAQ · 06
Yes, and what decides the cost of later is what this rebuild reserves now. Arabic is a layout state and a route structure before it is a translation, so a rebuild that specifies the mirrored component set and puts every route under a locale segment turns the Arabic version into content work. A rebuild that does not is the reason Arabic gets quoted as a second redesign a year afterwards. We write down which of the two you are buying, at the point the structure is agreed rather than at the point the invoice arrives.
FAQ · 07

Keep exploring

Explore Website Design & Development

Part ofWebsite Design & Development

Website Design

A design system drawn for both reading directions, not screens.

Website Development

Builds sequenced around the approvals the launch date waits on.

UI/UX Design

Flows and states tested with real people before anything is built.

eCommerce Development

Stores wired for the payment set, the courier and the invoice.

Shopify Development

The plan decides more than the theme. We settle that first.

WooCommerce Development

A store you own outright, with the running cost priced first.

WordPress Development

Built for the two people who have to publish it, in both scripts.

Headless CMS Development

For content that has to reach more than one surface.

Speed Optimisation

The origin, the scripts and the consent layer, not the network.

Next step

See what is worth keeping.

Send us the site and tell us what changed. We will come back with what to keep, what to rebuild, and what to leave alone.

Tell us what you need.