Website Migration SEO Checklist for Businesses in the UAE

A website migration keeps your search visibility only if every important old URL is mapped to a new one, redirects work on launch day and the new site is technically sound before it goes live. For UAE businesses moving to a new design, CMS or domain, often with English and Arabic versions, the SEO work should start at the planning stage, not after traffic drops.

What counts as a website migration?

A website migration is any change that alters how search engines find and understand your site: a new domain, a new CMS or ecommerce platform, a change in URL structure, a switch to encrypted connections, merging several sites or adding language versions. A redesign that keeps every URL and the content the same carries less risk than a replatforming.

Knowing which type you are doing tells you how much SEO work is needed. If you are still deciding whether to rebuild or redesign, our guide on choosing between a website rebuild and a redesign explains the trade-offs.

Why do migrations lose traffic?

Migrations usually lose traffic because old URLs stop working without redirects, valuable content is removed or thinned, internal links break, or technical settings block search engines on the new site. Most of these causes are preventable.

Common mistakes include launching with the staging site's "noindex" setting still on, redirecting every old page to the home page, changing page titles and headings without reason, and dropping the Arabic version or merging it into English pages. Some fluctuation after a large migration is normal, but a sharp, lasting drop usually points to one of these issues.

Another frequent cause is lost internal linking. When menus, footers and related-content blocks are redesigned, pages that used to be linked from everywhere can end up buried several clicks deep. Search engines read internal links as a signal of importance, so compare the internal link structure of the old and new sites for your top pages before launch.

What should you do before the migration?

Before the migration, take a full inventory of what you have and what performs, then decide what moves, what merges and what is retired. This is the most important stage.

• Crawl the current site and export every URL, including Arabic pages, images and PDFs.
• Export the pages that bring search traffic, leads or sales from your analytics and search console.
• List pages with links from other websites, because they carry authority.
• Record current page titles, meta descriptions, headings and structured data for top pages.
• Decide for each URL: keep, merge into another page or retire.
• Build a redirect map from every old URL to its closest new equivalent.
• Plan URL patterns for both languages, with separate Arabic URLs and hreflang.
• Benchmark rankings, traffic and conversions so you can compare after launch.
• Confirm the new site's page speed and Core Web Vitals on staging.

How should redirects be planned?

Redirects should be permanent (301) and point each old URL to the most relevant new page, not to the home page. One-to-one mapping for important pages is worth the effort.

Avoid redirect chains, where one URL redirects to another that redirects again; point old URLs straight to the final destination. Keep redirects in place long term. Test the full map on staging with a crawler before launch, and again in production on launch day. For bilingual sites, check that English URLs redirect to English pages and Arabic to Arabic, because mixing them confuses both visitors and search engines.

What about bilingual English and Arabic pages?

Bilingual pages need their own URLs in both the old and new structure, hreflang annotations that pair them correctly and redirects that respect the language of each page. Treat the Arabic site as a full part of the migration.

Arabic pages are often the ones forgotten in redirect maps because they were added by a plugin or a separate team. Include them in the crawl, check that Arabic titles and descriptions are carried over and confirm the new templates render right to left correctly before launch.

How is a migration project usually run?

A migration is usually run as discovery, a written scope with the redirect map, phased build, pre-launch testing, a planned launch window and close monitoring afterwards. SEO tasks sit inside each stage rather than at the end.

Discovery covers goals, platforms, content inventory and stakeholders. The written scope lists templates, content to move, the redirect map, tracking and what is out of scope. During the build, the SEO lead reviews templates for titles, headings, structured data, internal links and speed. Pre-launch testing crawls staging, checks redirects, tracking and forms, and confirms indexing settings. Launch happens at a quiet time with the team ready to fix issues. Handover includes documentation of redirects, tracking and the content model. Our SEO and SEM services cover this work alongside web development in the UAE.

Clear ownership matters as much as the plan. Name one person who approves the redirect map, one who signs off on content changes and one who can make fixes on launch day, so problems are solved in hours rather than days.

What should you check on launch day and after?

On launch day, check that the site is indexable, redirects work, tracking fires and key pages load quickly; in the weeks after, monitor rankings, traffic, crawl errors and conversions against your benchmark.

• Robots settings and meta robots allow indexing in production.
• XML sitemaps list the new URLs and are submitted to search engines.
• A sample of old URLs, including Arabic ones, redirect correctly.
• Analytics, tag manager and conversion events work on all templates.
• Forms, search and checkout work in both languages.
• No important pages return errors in the crawl.
• Canonical tags point to the right URLs.
• Page speed is in line with what was measured on staging.

What drives the cost and effort of migration SEO?

The cost and effort are driven by the number of URLs, the amount of content changing, the number of languages and how much the URL structure changes. A small brochure site and a large ecommerce catalogue are very different projects.

Other drivers include the quality of the existing site data, redirects from previous migrations, platform constraints on URLs and redirects, and the depth of monitoring after launch. The main trade-off is speed of launch against thoroughness of mapping: skipping the inventory saves time before launch but often costs more afterwards.

What does a realistic scenario look like?

For example, a Dubai company moves its English and Arabic website from an old CMS to a new one and changes the URL structure at the same time. The Arabic pages were created by a plugin with query-string URLs, and several service pages are being merged.

A careful plan would crawl both languages, export the pages that bring traffic and leads, and map each old URL to a new one, merging service pages where it makes sense. Arabic pages would move to clean URLs with hreflang pairs. Redirects would be tested on staging and again at launch, and the team would review search console and analytics daily for the first weeks, fixing any missed URLs quickly.

Frequently asked questions

Will we lose rankings after a migration?

Some movement is common, but a well-planned migration with complete redirects usually limits it. Large drops are typically caused by preventable mistakes.

How long should we keep redirects?

Keep them long term. Removing redirects later can break old links from other sites and bookmarks.

Can we change content during the migration?

Yes, but change only what you need to. Changing URLs, design and content at once makes problems harder to diagnose.

Do we need to migrate old blog posts?

Keep posts that bring traffic or links and update them; merge or retire thin ones with proper redirects.

If you are planning a new website, see our UAE services or talk to us about a migration plan.