Website redesign without losing your SEO: the Dubai checklist
- Redesigns lose traffic for three reasons: changed URLs without redirects, content cut for visual tidiness, and a staging site that launches still blocking crawlers.
- Record your baseline — URLs, rankings, traffic, enquiries — before anything moves.
- Map every old URL to a new one with a permanent 301 redirect. No catch-all to the homepage.
- A two to six week dip is normal. Eight weeks down is a fault, not a settling period.
A redesign is the most common way a Dubai business quietly loses its search visibility. The new site looks far better, everyone is pleased on launch day, and six weeks later the enquiries have thinned out and nobody can say exactly when it started. The design was never the problem. The problem is that a redesign is a migration — you are moving every address, every page of text and every internal link that Google and the AI engines have spent years learning — and it was planned as a visual project.
The good news: almost every loss is preventable, and the preventive work costs a few hours spread across the project. Here is the sequence we follow.
1. Record the baseline before anything moves
You cannot prove a redesign was safe if you never wrote down what "before" looked like. Two weeks before build starts, capture:
- A full list of live URLs. Export from Search Console and your sitemap, then crawl the site so you catch pages nobody remembered — old landing pages, PDFs, blog posts from a previous agency.
- Your top 20 pages by clicks and impressions from Search Console, and your current position for the queries that actually bring enquiries.
- Enquiry volume by source for the last three months. Traffic is a proxy; enquiries are the thing you are protecting.
- Where AI engines currently name you. Ask ChatGPT, Perplexity and Google's AI answers the questions your buyers ask, and log which of your pages get cited. Our free AI visibility check does this for you, and it is much easier to run before the rebuild than to reconstruct afterwards.
2. Keep the URLs you can, redirect the ones you cannot
Every URL change spends a little of the authority that page has accumulated. So the default is: keep it. Change a URL only when the new structure is genuinely clearer — and when you do, map old to new, one by one, with a permanent 301 redirect to the closest equivalent page.
The two failures we see most often in Dubai rebuilds are worth naming. The first is the catch-all: every old URL redirected to the homepage. Google treats that as a soft 404 and the accumulated value evaporates. The second is the redirect chain — old page to interim page to new page, sometimes three or four hops deep after a couple of rebuilds — which dilutes signals and slows crawling. Point each old URL directly at its final destination.
Redirects are also what stop paying visitors from landing on error pages. Every brochure, email signature and directory listing in the UAE that carries an old link keeps working, or it does not.
3. Do not let the design eat the content
This is the quiet killer. A designer working towards clean, airy layouts trims a 900-word service page to three punchy sentences and a hero image. The site looks modern. The page that used to rank now says almost nothing, and the AI engines that were extracting answers from it have nothing left to extract.
Keep the substance. If a page currently earns traffic, its replacement should carry the same questions, the same specifics and the same headings — restyled, reorganised, even rewritten, but not emptied. This matters doubly for the pages AI answers rely on: fees, timings, curricula, service scope, coverage areas. As we cover in how AI search engines choose which websites to cite, models lift short, self-contained passages. Delete the passage and you delete the citation.
The same goes for title tags, meta descriptions, H1s, image alt text and your structured data. They are content, not decoration, and they are frequently rebuilt from scratch by accident.
4. Rebuild the internal links deliberately
Old sites accumulate internal links over years — a blog post linking to a service page, a service page linking to a case study. New sites usually launch with navigation links only, and the pages that were being supported quietly lose their support.
Before launch, list the internal links pointing at your most important pages and make sure equivalents exist on the new site. While you are there, fix the ones that were broken anyway. This is also the cheapest moment to give your money pages — the ones that convert — more internal support than they had before.
5. The launch-day checklist
Run these in order on the day you go live:
- Remove the crawler block. Staging sites are usually set to noindex or disallowed in robots.txt. Shipping that setting to production is the single most destructive migration mistake, and it is invisible until the traffic disappears.
- Test the redirects against your baseline URL list. Every old address should resolve in one hop with a 301.
- Submit the new sitemap in Search Console and check that canonical tags point at the new URLs.
- Re-check analytics and form delivery. Rebuilds routinely drop the analytics tag or leave a contact form posting into nowhere — see 7 signs your website is losing enquiries.
- Confirm structured data survived the move, and that your Google Business Profile, directory listings and social profiles point at URLs that still exist.
6. Watch the first eight weeks properly
Some movement after a migration is normal. Google re-crawls the site, consolidates the redirects and re-evaluates pages, and positions wobble while that happens. On a clean migration most sites settle within two to six weeks.
What is not normal is a steady decline that never recovers. Check crawl errors and coverage in Search Console weekly, compare your top-20 pages against the baseline, and treat any page that lost its position as a specific question with a specific answer — was it redirected, was its content shortened, did it lose its internal links? Vague reassurance that "SEO takes time" is not a diagnosis. Our guide to how long SEO actually takes sets out what a realistic recovery curve looks like.
Who should own this
The risk in most Dubai redesign projects is organisational, not technical: the design studio owns the look, someone else owns the SEO, and the migration falls between them. Whoever builds the site should be accountable for the redirect map and the search baseline, in writing, before the first page is designed.
That is how we run website projects — the rebuild and the search work sit with the same team, so the redirect map is part of the build rather than a post-launch rescue. A build or rebuild is included in every monthly plan — up to 10 pages on Starter, up to 20 on Growth, a full site on Premium — or quoted standalone to scope; the full breakdown is on our pricing page.
Common questions
Will a redesign hurt my rankings? It does not have to. Losses come from changed URLs without redirects, thinner content, or a site that launches still blocking crawlers — not from new visuals. A short dip while Google re-crawls is normal.
How long until traffic recovers? Two to six weeks on a clean migration. Still down after eight weeks means something is broken and needs diagnosing, not more patience.
Should I keep my old URLs? Keep the ones that work. Change them only with a reason, and always with a one-hop 301 to the closest equivalent.
Can I redesign in stages instead? Yes, and for content-heavy sites it is often safer — move templates and sections in phases so a problem affects a handful of pages rather than all of them at once.