# Website Migration SEO: A Checklist That Keeps Your Traffic

> Website migration SEO guide: move a site without losing search traffic — URL mapping, one-hop 301 redirects, canonicals, sitemaps and Change of Address.

https://rankproof.eu/guides/website-migration-seo

## Short answer

A website migration keeps its search traffic when every old URL answers one server-side permanent redirect (301 or 308) to its closest new equivalent, the new pages carry self-referencing canonicals, and internal links and the sitemap use only the new URLs. Announce the move: a new sitemap in Search Console and Bing Webmaster Tools, plus the Change of Address tool when the domain changes. Expect rankings to fluctuate for a few weeks and keep the redirects for at least a year.

- **Redirect type**: 301 or 308, server-side
- **Redirect hops**: One, straight to the final URL
- **Keep redirects**: At least 1 year
- **Change of Address tool**: Domain moves only · 180 days
- **Settling time (medium site)**: A few weeks or more

## Website Migration SEO: A Checklist That Keeps Your Traffic

A migration is any change that moves pages to new addresses: a new domain, a new URL structure, a switch to HTTPS, a new CMS that writes URLs differently. Search engines have to learn every new address and move the signals of the old one to it. Done carefully, traffic dips for a few weeks and recovers; done carelessly, pages drop out for months. Every rule below comes from Google's and Bing's own documentation, linked under Sources.

## 1. Know what kind of move it is

| Move | What changes | What to do |
|---|---|---|
| New domain | Every URL | Redirects, new sitemap, Change of Address tool in Search Console, Site Move in Bing |
| New URL structure or CMS | Paths on the same domain | Redirects and a new sitemap; no Change of Address |
| HTTP to HTTPS | The scheme | Redirects; Google detects the change itself |
| www to non-www (or back) | The host name | Redirects and canonicals; no Change of Address |
| New hosting or CDN only | Nothing in the URLs | Keep the site up and fast during the switch; no redirects needed |

Change one thing at a time when you can — the domain first, the design later — so that if traffic drops you know why. Google recommends moving small and medium sites in one go, and large sites section by section.

## 2. Map every old URL

Before anything goes live, build a list of old URLs and where each one goes. Collect them from the old sitemap, the Page indexing report in Search Console, your analytics' landing pages, and the pages other sites link to. Then:

- send each page to its **closest new equivalent**, one to one;
- do **not** send everything to the new home page: Google treats redirects to an unrelated page like a "not found" (a soft 404), and visitors land somewhere that does not answer their click;
- let pages that have no equivalent answer **404 or 410**.

## 3. Redirect in one hop

Use **server-side permanent redirects, 301 or 308**. Point each old URL straight at its final address: a chain such as http → https → www → new path costs a request at every step, and Google advises keeping chains short. Test a sample of the map with a redirect checker before and after launch. If your server also normalises trailing slashes or upper case, make sure that rule does not add a second hop.

## 4. Update everything that points at old URLs

- **Internal links** in menus, footers and body text — a link to a redirect still works but wastes a request.
- **Canonical tags** on the new pages, pointing at themselves.
- **hreflang** links between language versions, if you have them.
- **The sitemap**: only new URLs that answer 200.
- **Structured data** that contains URLs, such as the logo or the organisation's address.
- Profiles, ads, email templates and anything else you control that links to the site.

## 5. Launch and announce the move

1. Remove any `noindex` or robots.txt block left over from the staging site.
2. Submit the new sitemap in Search Console and in Bing Webmaster Tools. Keep the old sitemap for a while if it helps crawlers find the redirects; its warnings about redirecting URLs are expected.
3. For a **new domain**, use the Change of Address tool in Search Console on every variant of the old domain (with and without www). It forwards signals for 180 days and needs you to own both properties. Bing has its own Site Move tool for verified sites.
4. Announce changed URLs to Bing with **IndexNow**, which also tells other engines that support it.

## 6. Watch the weeks after

- In the **Page indexing report**, old URLs move to "Page with redirect" and retired ones to "Not found (404)". That is the migration working, not an error.
- **Impressions and clicks** should shift from old URLs to new ones in the Performance report. Google says it can take a few weeks or more for a medium-sized site.
- Check **server logs** for crawler requests that hit errors.
- Keep the redirects for **at least a year**, longer if the old URLs still get visits or links.

## What our own clean-up looked like

In September and October 2026 we retired several hundred URLs on this site — old tool pages, language mirrors of pages that no longer exist and per-clause pages folded into one. On 12 October 2026 our Page indexing report listed 330 URLs under "Page with redirect" and 246 under "Not found (404)". Both are expected results of the clean-up. One lesson came from reading the list of crawled pages: Google was still visiting an old /requirements address in every language, and it answered 404 although the content had moved. On 18 October 2026 we gave it a one-hop 301 to its new home. Compare what crawlers still request with your redirect map, months after the move.

## A migration checklist

1. Decide what kind of move it is, and change one thing at a time.
2. Export every old URL and map each to its closest new page; mark the ones that should answer 404 or 410.
3. Set up one-hop 301 or 308 redirects and test a sample.
4. Update internal links, canonicals, hreflang, the sitemap and structured data.
5. Remove staging blocks, submit the new sitemap to Google and Bing, and use Change of Address for a domain move.
6. Watch the Page indexing and Performance reports weekly for the first two months.
7. Keep the redirects for at least a year.

## Checking it with RankProof

The redirect checker follows a URL hop by hop (up to 10 hops) and shows the status and target of each step. The sitemap checker counts the URLs in your sitemap and flags http:// addresses, the canonical URL checker shows which address a page declares, the broken link checker finds links that now fail, and the 404 test confirms that missing pages answer a real 404. What no tool on this site can do is see how Google indexes your whole site; that is what Search Console's reports are for.

## Primary sources

- [Site Moves and Migrations — Google Search Central](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes)
- [Change of Address tool — Search Console Help](https://support.google.com/webmasters/answer/9370220)
- [Redirects and Google Search — Google Search Central](https://developers.google.com/search/docs/crawling-indexing/301-redirects)
- [Page indexing report — Search Console Help](https://support.google.com/webmasters/answer/7440203)
- [Website Migration with Bing — Bing Webmaster Blog](https://blogs.bing.com/webmaster/december-2020/Website-Migration-with-Bing)
- [IndexNow — Bing](https://www.bing.com/indexnow)
