
Website Migration Checklist
A website migration keeps its rankings when it follows five phases in order: plan and benchmark, build a one-to-one redirect map, test the new site on staging, launch with a short checklist, then monitor for 90 days.
Sahar
Content Writer
A website migration checklist is the difference between a relaunch that keeps its rankings and one that spends six months climbing back. Whether you are redesigning, changing CMS, moving platform or changing domain, the work that protects your search traffic is the same, and it happens in a fixed order. This guide explains how to migrate a website without losing SEO, in five phases, with a plan template you can copy at the end.
It is the checklist we work from on migration projects. The steps are deliberately boring: most traffic lost in a migration is not lost to anything clever, but to missing redirects, blocked crawling and pages that quietly lost their content.
Need this done right?
Hoop builds the strategy, design and development behind sites like this one, talk to us about yours.
What a Website Migration Checklist Must Cover
Every website migration checklist must cover five things: a plan with a benchmark, a redirect map, a staging test, a launch-day list and at least 90 days of monitoring. Skip any one of them and you either lose traffic or cannot tell whether you have.
What changes from project to project is the detail inside each phase. A redesign on the same domain is mostly about content and internal links. A CMS or platform move adds new URL patterns and templates. A domain change moves every URL at once. If you want a checklist organised by those migration types instead of by time, read our site migration checklist. If you are still deciding whether a migration is the right move, start with what website migration is and how each type affects SEO.
| Phase | When | The question it answers |
|---|---|---|
| 1. Plan and benchmark | Weeks before launch | What do we have, and what is it worth? |
| 2. Redirect map | Before the build is finished | Where does every old URL go? |
| 3. Staging test | Before launch | Will Google see what we expect? |
| 4. Launch | Launch day | Did everything go live correctly? |
| 5. First 90 days | After launch | Is search recovering as expected? |
Phase 1: Plan and Benchmark
Phase 1 records what you have before anything changes. Without a benchmark, you cannot tell a normal post-launch dip from a real loss, and you cannot prove the migration worked.
Scope and URL inventory
List every URL on the current site, not just the ones in the navigation. Combine four sources: a full crawl of the site, the XML sitemap, the pages that received traffic in your analytics over the last 12 months, and the pages with backlinks from your backlink tool. The crawl misses orphaned pages; analytics misses pages with no recent visits; the backlink list catches old URLs that still carry authority.
For each URL, record its traffic, conversions, number of linking domains and the main query it ranks for. This inventory becomes the redirect map in Phase 2. Content, forms, integrations and tracking need an inventory too; our migration website checklist covers those in full.
Benchmark rankings, traffic and links
Export, and save with a date: organic sessions and conversions by landing page, Search Console clicks and impressions by page and by query, rankings for your important keywords, the number of indexed pages, and your top linked pages. Keep at least 12 months of data where you can, so seasonality does not fool you later.
If you are planning a large or complex move, this is also the point to get an outside view. Our SEO migration services start with exactly this benchmark and a written list of risks.
Agree who owns what
Migrations fail in the gaps between teams. Write down, before the build starts, who owns the URL inventory, who writes the redirect map, who implements it, who signs off the staging crawl and who watches Search Console after launch. Agree a freeze on new content and URL changes for the last week before launch, so the redirect map is not out of date on the day it goes live. A one-page plan with names against each task is worth more than a long document nobody reads.
Pick a low-traffic launch window
Launch when traffic is naturally low and your team is available for the following days: usually early in the week, never right before a holiday or your busiest season. A Friday-evening launch with nobody watching on Saturday is how small problems become big ones.
Phase 2: Build the Redirect Map
Phase 2 turns the URL inventory into a redirect map: a spreadsheet with every old URL in one column and its new destination in the next. Redirect mapping is the most important single task in any migration.
One-to-one 301s, one hop
Each old URL should redirect to the single new page that best matches it, with a permanent 301 (or 308) redirect. Google's documentation on site moves with URL changes recommends permanent server-side redirects and mapping old URLs to their new equivalents. A good 301 redirect map has three properties:
- Relevant: the destination answers the same need as the old page.
- Direct: one hop from old to new, never through an intermediate URL.
- Complete: every URL with traffic, links or rankings is on it.
What to do with pages you remove
Not every old page needs a twin on the new site. If a page had no traffic, no links and no rankings, it can return a 404 or 410. If it had value, redirect it to the closest relevant page, such as the parent category or the newer guide on the same topic. Do not redirect everything you remove to the homepage: Google tends to treat irrelevant redirects like soft 404s, and visitors arrive somewhere that does not answer their question.
Common traps
- 302s instead of 301s. Many CMS plugins and hosting panels default to temporary redirects. Check the status code, not just that the redirect works.
- Chains. If the site was migrated before, old URLs may already redirect. Update those rules to point straight at the final destination.
- Redirects to the homepage. Convenient, and almost always wrong.
- Trailing slashes, case and parameters.
/page,/page/and/Pagecan be three different URLs. Decide one format and redirect the others. - Images and files. PDFs and images with backlinks or image-search traffic need redirects too.
How to build the redirect map in a spreadsheet
- Paste every old URL from your inventory into column A, with its traffic, conversions and linking domains in the next columns.
- Sort by value, so the most important URLs are mapped and checked first.
- In the next column, add the new destination for each URL. Use pattern rules (such as a whole blog folder whose slugs do not change) where you can, and write the exceptions out one by one.
- Add a column for the decision type: same page, merged into another page, moved to a parent, or retired without a redirect.
- Have a second person review the top of the list, where mistakes cost the most.
- Export the final map in the format your developer or platform needs, and keep the spreadsheet as the record of what was decided and why.
After launch, the same spreadsheet becomes your test list: run every old URL through a redirect checker and confirm each returns a single permanent redirect to the destination you chose.
Phase 3: The Website Migration SEO Checklist for Staging
Phase 3 tests the new site before Google sees it. Crawl the staging site as if it were live and fix everything this website migration SEO checklist finds before launch day.
- Staging is blocked, but only staging. Protect staging with a password or IP allowlist. If it uses a noindex tag or a disallow rule, list it as something to remove at launch.
- Every important page exists and has its content. Compare the old and new versions of your top pages by traffic. If a ranking page lost the sections that answered its query, put them back.
- Titles, meta descriptions and headings carried over or improved, with one H1 per page.
- Canonical tags point to the new URLs on the new domain, not to staging and not to old URLs.
- Internal links point straight to new URLs rather than relying on redirects.
- Structured data is present and valid on the templates that had it before.
- Hreflang, if you have more than one language or region, references the new URLs.
- Rendering: content and links appear in the HTML Google renders, not only after scripts run.
- Speed and mobile: new templates are at least as fast as the old ones on a phone.
- Analytics and conversion tags fire on every template, so you can measure the result.
- The redirect map is loaded and tested against staging where possible.
Our technical SEO audit checklist goes deeper on each of these checks if you want a complete crawl review.
Run the staging crawl more than once: after the first build, after fixes and just before launch.
Phase 4: Launch, Using a New Website SEO Checklist
Phase 4 is short because the work was done in Phases 1 to 3. The new website SEO checklist for launch day is about confirming that what you tested is what went live.
- Remove staging blocks: noindex tags, disallow rules and password protection.
- Deploy the redirect map and test it in bulk: every old URL should return one 301 to the right destination.
- Check robots.txt and the XML sitemap on the live site, and submit the new sitemap in Search Console.
- Spot-check your top 20 to 50 URLs by traffic: status code, canonical, title, content and tracking.
- Confirm analytics and conversion tracking are recording on the live site.
- For a domain change, use the Change of Address tool; see our domain migration checklist.
For the hour-by-hour launch runbook, the go/no-go decision and a rollback plan, use our launch-day and recovery checklist.
Phase 5: The SEO Migration Checklist for the First 90 Days
Phase 5 is where most migrations are won or lost, because problems that slipped through only show up once Google recrawls the site. Use this SEO migration checklist daily for the first two weeks, then weekly to day 90.
- Indexing reports in Search Console: new URLs being indexed, old ones dropping out, and no rise in "not found", "redirect error" or "crawled, currently not indexed".
- 404 and server errors in your logs and crawl tool: add redirects for any old URL you missed.
- Rankings and traffic against the benchmark, by page and by query, so you can see which sections are recovering and which are not.
- Link reclamation: ask the sites behind your most valuable backlinks to update links to the new URLs.
- Conversions, not just traffic: a site can keep its visits and lose its leads if forms or tracking broke.
Report in plain terms. Send stakeholders a short weekly note for the first month: organic sessions and conversions against the benchmark, indexing progress, errors found and fixed, and anything still open. A shared, honest view stops a normal dip from turning into a panic, and makes sure real problems get developer time quickly.
When is a dip normal? Google says a medium-sized site can take a few weeks for most pages to move in its index, and larger sites longer. Some fluctuation during that time is expected. A dip that keeps deepening after the first few weeks, or that is concentrated in one section of the site, points to a specific problem worth investigating. The recovery section of our launch-day checklist shows how to diagnose one.
Website Migration Plan Template
Copy this website migration plan template into a spreadsheet and add an owner and a due date to every row. To size each row in hours, see how many hours to estimate for site migration SEO.
| Task | Phase | Owner | Done |
|---|---|---|---|
| Full crawl, sitemap, analytics and backlink URL lists combined | 1 | SEO | |
| Benchmark exported and saved (traffic, Search Console, rankings, links) | 1 | SEO | |
| Launch window agreed and team availability confirmed | 1 | Project lead | |
| Redirect map complete for every URL with value | 2 | SEO | |
| Old redirect chains updated to final destinations | 2 | Developer | |
| Staging crawled; content, titles, canonicals and links fixed | 3 | SEO + developer | |
| Structured data, hreflang and rendering checked | 3 | Developer | |
| Analytics and conversion tags tested on every template | 3 | Analytics | |
| Staging blocks removed and redirects deployed | 4 | Developer | |
| Redirects bulk-tested; top URLs spot-checked | 4 | SEO | |
| Sitemap submitted (Change of Address if the domain changed) | 4 | SEO | |
| Daily checks of indexing, errors and conversions (weeks 1-2) | 5 | SEO | |
| Weekly comparison with the benchmark (to day 90) | 5 | SEO | |
| Backlink owners asked to update top links | 5 | SEO / PR |
Keep the template alive after launch. Add a row for every issue found in Phase 5, with its cause and fix, so the next migration starts with your own lessons rather than a blank sheet.
When to Bring in Help
A small site with a few dozen pages and unchanged URLs can be migrated in-house with this checklist. Bring in help when the site has thousands of URLs, a lot of organic revenue, several languages, a platform change, or a history of earlier migrations and redirects.
The discipline is the same at any scale. When we migrated BeesApp, a retail-tech platform in Saudi Arabia, from a patchwork of PHP, Django and Vue to one Next.js, Flutter and FastAPI architecture, the work followed the same inventory, mapping, testing and monitoring steps, with the data migrated and 99.9% uptime after launch. You can read the BeesApp case study.
Planning a migration? Get a free SEO audit before you move. Our SEO migration team benchmarks your current site, lists the URLs that matter and shows you the risks in your plan before anything goes live.
“A migration rarely loses traffic because of the new design. It loses traffic because of the old URLs nobody mapped.”
Key takeaways
- 01Benchmark rankings, traffic and links before anything changes, or you cannot prove what the move did
- 02Map every URL that has traffic, links or rankings to its closest new page with a single 301 redirect
- 03Crawl the staging site for noindex tags, canonicals, broken links and missing tracking before launch
- 04Watch Search Console and analytics daily for the first weeks, then against the benchmark until day 90
Written by
Sahar
Content Writer
Frequently Asked
Questions
Everything you need to know before booking a strategy call. Can't find your answer? Contact us directly.
Ask hoop
Usually replies in minutes
What is the most important step in a website migration?
The redirect map. Every URL that has traffic, backlinks or rankings needs a permanent redirect to its closest equivalent on the new site. Most migration traffic losses trace back to URLs that were left to return 404 errors or were redirected somewhere irrelevant.
PEOPLE ALSO ASK
Swipe for 4 more questions →
Can't find your answer? Contact us directly.


