Website Migration in Dubai Without Losing Your Rankings

You keep your rankings through a website migration by changing one thing at a time, redirecting every old URL to its real equivalent with a permanent redirect, and watching Search Console for eight weeks afterwards. Traffic almost never disappears because Google punished the move. It disappears because a redirect pointed at the wrong page, a staging rule stayed switched on, or a redesign and a domain change happened in the same weekend.

This is the runbook we use for a Dubai website migration, built on what Google Search Central publishes rather than on folklore. Every rule quoted below was read from Google’s own documentation on 4 October 2026.

Key takeaways

• Google tells site owners to plan changes “one after the other, not everything at the same time”: move the domain, then change the layout, then change the platform.
• Map old URLs to new ones before the build starts. The map is the deliverable that decides whether the migration works, not the design.
• Use server side permanent redirects, 301 or 308. Google follows up to 10 hops but advises redirecting straight to the destination and keeping any chain to no more than three redirects.
• Redirecting a lot of old pages to the home page can be read as a soft 404, so a page with no equivalent should return 404 or 410 instead.
• The Change of Address tool only applies to a domain or subdomain move, works at domain level only, does not carry subdomains with it, and runs for 180 days.
• Arabic and English versions need hreflang annotations updated to the new URLs on both sides, because Google ignores the pair if the two pages do not point at each other.
• Keep redirects at least a year. Google’s guidance for the Change of Address window is a 180 day minimum, after which it treats the old site as unrelated.

What a website migration actually changes

Before anything else, write down which of these four layers is moving. They carry completely different risk.

Google’s own best practice for site moves is blunt about combining them: if you want to move to a new domain, change your content management system and change the layout, do them one at a time. The Change of Address help page repeats the point from a different angle, warning that keeping the same architecture in the new location passes signals more directly, and that combining a move with a redesign of content and URL structure will probably cost traffic while Google relearns the individual pages.

Most Dubai agencies sell the opposite, because a single launch date is easier to invoice. From a development perspective the staged version is cheaper in the end, since a drop after a combined launch gives you no way to tell which change caused it.

Build the redirect map before anyone designs a page

The map is a spreadsheet with one row per old URL and one column for its destination. Build the list of old URLs from four places at once, because no single source is complete.

• Your existing XML sitemap, which holds the pages you already told Google about.
• Search Console, filtered to the last 16 months of pages that received impressions. Anything with clicks is a page you cannot afford to drop.
• Server access logs, which show URLs that still get requested even though nothing links to them any more.
• A crawl of the live site, to catch pages the sitemap never included.

Then add images, PDFs and downloads. Google asks specifically for embedded content, including videos, images, JavaScript and CSS, to be moved the same way as everything else. A company profile PDF that collected links for six years is worth more than most of the pages people argue about.

Each row gets one of three decisions: redirect to the equivalent page, redirect to the page that absorbed it if content was consolidated, or return 404 and let it go. That third option is a real decision and not a failure. Google’s guidance is that URLs with no equivalent on the new site should correctly return 404 or 410, and warns separately against redirecting many old URLs to one irrelevant destination such as the home page, which it says can be treated as a soft 404.

One issue we often see in Dubai is a 2018 site with sixty service pages written for keyword coverage, being migrated into a cleaner twelve page structure. The right answer is usually to consolidate, redirect the forty eight into the twelve that replaced them by subject, and accept a small number of honest 404s for pages that never ranked for anything.

Arabic pages are where bilingual migrations break

If the site runs English and Arabic, the hreflang annotations have to be rewritten to the new URLs on both versions at the same moment. Google’s rule is unforgiving here: each language version must list itself as well as all the other versions, and if two pages do not both point to each other the annotations are ignored. Half-updated annotations are the same as no annotations.

Three things to settle before launch:

• The URL pattern for Arabic. A subdirectory such as /ar/ moves with the domain and keeps everything inside one Search Console property. A separate subdomain does not move with a Change of Address request, which the tool explicitly states does not carry subdomains, so it needs its own request.
• The self-referencing canonical on every new page, pointing at its own new URL. Google lists this as the first of the three things to update once the mapping exists.
• An x-default annotation if there is a language selector or a home page that redirects by language, which Google recommends as the fallback for users whose settings match none of your versions.

Check the pairs after launch by requesting the Arabic page and confirming it names the English URL, then doing the reverse. Two pages, thirty seconds, and it catches the single most common bilingual mistake in the region.

The staging site is the most common way a launch disappears

Google lists forgotten noindex rules and robots.txt blocks first in its troubleshooting section for site moves, and tells site owners who block crawling during development to prepare in advance both the robots.txt the live site should have and the list of URLs from which noindex has to be removed.

Protect staging with HTTP authentication rather than with a noindex meta tag, because a password cannot be forgotten on launch day in the way a meta tag can. If staging is only protected by robots.txt, remember that blocking crawling does not reliably keep a URL out of results, so authentication is the safer habit.

On launch morning, in this order: remove the authentication, confirm the live robots.txt serves the rules you intended, view source on five pages across different templates and search for “noindex”, then run those five through the URL Inspection tool. A staging environment only helps if the last thing you do is take the fence down.

Change of Address: when it applies and when it does nothing

The tool is narrower than most people assume. Google says to use it when moving from one domain or subdomain to another, and lists four situations where it should not be used at all: HTTP to HTTPS, moving pages between paths inside the same site, switching between www and non-www on the same domain, and a hosting move with no visible URL change.

Three conditions catch people out. You have to own both properties in Search Console under the same Google account. The property has to be at domain level, so a path such as example.com/en/ cannot be moved. And the tool does not carry subdomains, so a move from example.ae to example.com needs a separate request for www, for any Arabic subdomain, and for any other variant, each verified in Search Console first.

After a successful request, the notification appears for 180 days and Google emphasises the new site over the old for that period. Keep the redirects longer. Google’s broader site move guidance asks for at least a year and notes that after the 180 day window it treats a still-crawlable old site as unrelated.

The first 48 hours

Work through this in order, not in parallel, so that a problem is attributable to one step.

• Spot check thirty redirects from the map, chosen across templates rather than from the top of the list. Confirm each returns a single 301 straight to a 200 page, with no chain and no redirect to the home page.
• Submit the new XML sitemap in Search Console, and keep the old sitemap submitted for a while so you can watch indexed counts fall on one and rise on the other. Google describes exactly this pattern and says warnings about redirecting URLs in the old sitemap can be ignored.
• Update internal links to the new URLs instead of relying on the redirects. Google asks for this immediately after the move to cut server load and improve the experience.
• Update Google Business Profile, the Dubai directory listings, your social profiles, any Google Ads and Meta destination URLs, and the email signature. Ad landing pages pointing at redirected URLs still work, but they cost you a hop on every paid click.
• Confirm analytics and the Search Console verification method survived. Google warns that verification tokens can differ when the URL changes, and that an HTML file or meta tag used for verification has to exist in the new copy of the site.

What normal looks like for the next eight weeks

Expect movement. Google states plainly that visibility may fluctuate temporarily during a move, that this is normal, and that rankings settle over time. For a medium-sized site it says it can take a few weeks or more before the new URLs are shown instead of the old ones, and longer for large sites.

So the question is not whether impressions wobble. It is whether the shape is right. Watch four things weekly in Search Console: indexed pages rising on the new property, 404s staying flat rather than climbing, impressions recovering on the queries you held before, and server errors staying at zero. Google also warns that it crawls a migrated site more heavily than usual, because crawls of the old site get redirected on top of normal crawling, so check that the host has the capacity for it.

If 404s climb in week one, the redirect map has gaps and the fix is quick. If indexed counts hold but impressions keep sliding into week six on pages that redirect correctly, the problem is usually content rather than migration, and that is a different piece of work. This is also the moment to pick up anything deferred during the build, from maintenance through to the pages nobody rewrote.

Mistakes that cost months

• Letting the old domain expire. Keep paying for it. Google recommends holding it at least a year so nobody else buys an abandoned domain that still carries your links.
• Redirecting with a 302 because a developer set it as a temporary measure and nobody changed it back. Google recommends permanent redirects, 301 or 308, where technically possible.
• Chaining old to interim to new because two migrations happened in three years. Google advises going straight to the destination and, where that is not possible, keeping the chain to no more than three redirects and fewer than five.
• Launching during your busiest month. Google suggests timing a move to coincide with lower traffic, which in much of the UAE means the summer rather than the fourth quarter.
• Submitting a change of address before the redirects are live. Google’s own sequence puts the pre-work and the redirects first, and the tool runs a check for 301s before it accepts the request.

If you are planning a move and want the redirect map and the Search Console work handled by people who have done it before, that is part of how we run a website build in Dubai. Send us the current sitemap and we will tell you what the mapping looks like before you commit to anything.

All Google guidance cited above was read from Google Search Central and Search Console Help on 4 October 2026 and can change; check the current documentation before a launch. Sources: Google Search Central, “How to move a site” (site move with URL changes); Google Search Central, “Localized versions of your pages”; Google Search Console Help, “Change of Address tool”. Cover photo: Dubai in January 2025 13, via Wikimedia Commons (CC0).