Website Migrations Without Losing Rankings: Redirects and Checks

To migrate a website without losing rankings, you need to map every valuable old URL to its closest new equivalent with a permanent (301) redirect, keep the content and on-page signals of your important pages intact, make sure the new site is crawlable and indexable on launch day, and monitor Search Console closely for several weeks afterwards. Most traffic losses after a migration come from missing redirects, accidentally blocked pages or content removed during a redesign — all of which are preventable with planning.

Know what kind of migration you are running

Different migrations carry different risks. Many projects combine several, which multiplies the risk.

Migration type	Example	Main risk
Redesign, same URLs	New look on the same CMS	Content or internal links removed; templates change headings and titles
URL restructure	/our-services/seo becomes /services/seo	Every changed URL needs a redirect
Platform change	WordPress to a headless or custom build	URL patterns, metadata, rendering and redirects all shift at once
Domain change	.com to .ae, or a rebrand	Google must transfer signals to a new domain
Protocol or subdomain	HTTP to HTTPS, www to non-www	Sitewide redirects and canonicals must be consistent

If you can, avoid changing domain, platform and structure in a single launch. Separate steps make it far easier to diagnose problems.

Phase 1: Before you build

Benchmark everything

Export from Search Console and analytics the pages that earn clicks, impressions, conversions and external links over the last year. Crawl the current site and keep the full list of URLs, titles, meta descriptions, headings and canonical tags. This is your baseline and your safety net.

Decide which pages carry forward

Every page with traffic, links or conversions should either move to the new site or redirect to a genuinely equivalent page. Removing content during a redesign — "we'll simplify the services section" — is one of the most common causes of lost visibility.

Check the new templates

Make sure the new templates output unique title tags, a single H1, crawlable navigation links, correct canonical tags and any structured data you use. If the new site relies on JavaScript, confirm that the main content is present in the rendered HTML. If your website is being rebuilt by a development partner, share these requirements before build, not after.

Phase 2: Build the redirect map

The redirect map is a spreadsheet with two columns: old URL and new URL.

1. Start with the full list of old URLs from your crawl, sitemaps, Search Console and analytics, plus URLs with external links.
2. Map one-to-one wherever an equivalent page exists. The new page should satisfy the same need as the old one.
3. Map to the nearest relevant parent when a page is merged — an old sub-service page might redirect to the combined service page.
4. Do not redirect everything to the homepage. Google tends to treat irrelevant redirects like that as soft 404s, and visitors land somewhere unhelpful.
5. Let truly obsolete pages return 404 or 410 if there is no relevant equivalent and they have no meaningful links or traffic.
6. Use permanent redirects (301 or 308) and avoid chains: old URL to final URL in a single hop.
7. Remember non-HTML files such as PDFs and important images.

Phase 3: Launch-day checks

Run these within the first hours:

• The new site is not blocked: robots.txt allows crawling and no staging-environment noindex tags have survived.
• A sample of old URLs — especially your top pages — redirect in one hop to the right destination with a 301 or 308 status.
• Canonical tags point at the new live URLs, not the staging domain or the old site.
• hreflang annotations, if you have a multilingual site, reference the new URLs.
• The new XML sitemap is live and submitted in Search Console.
• Analytics and conversion tracking fire on the new site, including WhatsApp, call and form events.
• Internal links point to new URLs directly rather than relying on redirects.

For a domain change, verify both domains in Search Console and use the Change of Address tool once redirects are in place.

Phase 4: The weeks after launch

Some fluctuation is normal while Google recrawls and processes the change; how long it lasts depends on the size of the site and how much changed. Watch for signals that something is actually wrong:

• Page indexing report: a rise in "Not found (404)", "Blocked by robots.txt" or "Excluded by 'noindex' tag".
• Performance report: compare clicks for your top pages against the baseline. A sharp drop on specific pages usually points to a redirect or content issue on those pages.
• Crawl stats: spikes in server errors.
• Analytics: landing pages that disappear without their replacements picking up the traffic.

Keep redirects in place for the long term — Google advises keeping them for at least a year, and there is rarely a good reason to remove them at all. Our guide to crawlability and indexing explains how to read the indexing statuses you will see.

Frequently asked questions

Will rankings definitely drop after a migration?

Not necessarily. A well-planned migration with like-for-like content and complete redirects often recovers quickly. Losses are most likely when content is removed or redirects are missing.

Should we update external links to point to the new URLs?

Where you control them — social profiles, your Google Business Profile, directory listings — yes. For others, the redirects carry most of the value.

Key takeaways

• Benchmark traffic, links and page data before anything changes.
• Build a one-to-one redirect map and avoid blanket homepage redirects.
• Check robots.txt, noindex, canonicals, hreflang and tracking on launch day.
• Monitor Search Console for weeks and keep redirects permanently where you can.

If a redesign or replatform is on your roadmap, review it against a website redesign checklist and bring in Wot Digital's SEO migration support early — redirect planning is much easier before build than after launch.