Website Migration Checklist and Redirect Map Generator
Tick off 35 steps before, during and after the move, and build a 301 redirect map from the old and new sitemaps. Your progress stays in this browser.
Migration progress
0 %Progress is saved in this browser.
Before the move
0/14Launch day
0/8After the move
0/13Redirect map
The domains differ, so targets are full URLs on the new domain.
| Old URL | Redirect to | Match |
|---|
Nothing to show for this filter.
Export
Get the full report by email
A PDF with your progress by phase, the open items and the redirect map summary. Free.
Planning a website migration?
Tell us what you move and where. We plan redirects, move sites to the cloud and check SEO after launch, and will reply with options within one business day.
Thank you! We will reply within one business day.
TL;DR: A site migration keeps its traffic when every old URL gets a one-to-one 301 redirect to the closest new page, the new site is tested on staging and closed from indexing until launch, and 404s, indexing and rankings are monitored for several weeks after the move.
Example: what the redirect map shows
An online store moves from old-shop.example to shop.example. The old sitemap has 12 URLs, the new one 11. The tool keeps the home page, the blog and the privacy policy as unchanged paths, maps /contact.php to /contact by path, /catalog/kids to /shop/kids by slug and /about-us.html to /about by similarity. Two pages, /delivery-and-payment and an old promo page, have no match: you pick the target by hand or leave them to return 404 or 410.
What is a website migration?
Any change that alters URLs, content or the technical base of a site at scale: a new domain, a move to HTTPS, a new CMS or platform, a redesign with a new structure, or merging several sites into one.
How do you keep SEO rankings during a migration?
Benchmark traffic and rankings first, keep URLs where possible, redirect every changed URL with a 301 to its closest equivalent, carry over titles, descriptions and structured data, and do not launch with noindex or a blocked robots.txt.
How do you create a redirect map?
Collect all old URLs from the sitemap, a crawl, analytics and backlink reports, list the new URLs, and pair them. Pairs with the same path need no redirect. Pairs with the same slug in a new folder are usually safe. The rest need a human look.
Which redirect format do I need?
Cloudflare Pages reads a _redirects file in the output folder, Apache reads RewriteRule lines in .htaccess, nginx works best with a map block. Netlify also understands _redirects.
How long should redirects stay in place?
At least a year, and as long as old URLs still get traffic or links. Removing them early loses link equity and sends visitors to 404 pages.
What should you check after launch?
Submit the new sitemap, watch 404 and server errors daily for two weeks, compare traffic and rankings with the benchmark, and check that forms, payments and CRM leads work in production.
FAQ
Is the migration checklist free?
Yes. The checklist and the redirect map are free and need no signup. The PDF report is free too and is sent to the email you enter.
Where is my progress stored?
In your browser (localStorage). Nothing is sent to us until you request the report. The share link keeps the checkmarks in the part of the URL after #, which is not sent to the server.
Which sitemaps can the tool read?
XML sitemaps, sitemap indexes, gzip-compressed .xml.gz files and plain-text sitemaps, up to 50,000 URLs per site. A domain is enough: the sitemap is found through robots.txt.
How are URLs matched?
First by the same path, ignoring case, a trailing slash, index.html and file extensions. Then by the same last segment (slug) in another folder, then by similarity of words in the URL. You choose the target for the rest.
Should I redirect deleted pages to the home page?
No. Search engines treat mass redirects to the home page as soft 404s. Redirect to the closest relevant page or return 404 or 410.
Does the map handle URLs with query strings?
Yes in CSV and .htaccess. Cloudflare _redirects and the nginx map match the path only, so such URLs are skipped there and counted in a note.
Is a 301 or 302 redirect better for a migration?
Use 301 (permanent) for a migration. A 302 tells search engines the move is temporary, so they may keep the old URL in the index.