Most migration disasters trace back to one skipped step. This is the full website migration SEO checklist we run on every site we move: before, during, and after launch.
Here is the uncomfortable math of website migrations: months of design work, weeks of development, and all of it can be undone by a single skipped afternoon of SEO work. When a migrated site loses half its traffic, the postmortem almost never finds something exotic. It finds a missing redirect file, a staging site that went live with "noindex" still on, or a URL structure that changed with no map back to the old one.
This is the website migration SEO checklist we run on every site we move or rebuild. It is organized the way the work actually happens: before the migration, during the build, on launch day, and in the weeks after. If you are doing a redesign rather than a full platform move, the same discipline applies with lighter steps, and our guide to redesigning without losing SEO covers that version.
Before the Migration: Benchmark Everything
You cannot tell whether the migration succeeded if you never recorded the starting point. Before anyone builds anything:
- Crawl the entire existing site. Every URL, including old blog posts, tag pages, and PDFs. The pages you forgot exist are the ones Google remembers.
- Export your rankings. Every keyword you rank for, with positions and landing pages, from your rank tracker and Google Search Console.
- Export traffic by page. A year of data if you have it. Seasonal pages look worthless in the wrong month.
- Inventory your backlinks. Which URLs have links pointing at them? Those URLs carry authority you do not want to orphan.
- Screenshot your Search Console coverage. Indexed page counts, top queries, and any existing issues, so post-launch changes are attributable.
Save all of it somewhere the whole project can see. This benchmark is the contract the new site has to honor.
Before Launch: Build the Redirect Map
The redirect map is the single most important document in the migration. It is a boring spreadsheet with two columns, old URL and new URL, and it is worth more than any design file in the project:
- Map every old URL to its closest equivalent on the new site, one to one wherever possible
- Do not blanket-redirect everything to the homepage. Google treats mass homepage redirects as soft 404s, and the authority those pages earned evaporates
- Decide deliberately what gets retired. A page with no traffic, no rankings, and no links can die, but send its redirect somewhere sensible anyway
- Use 301 (permanent) redirects, not 302s
- Check for redirect chains: old URL to older URL to new URL wastes crawl budget and dilutes signals. Point everything directly at the final destination
While the new site is in staging, carry over the on-page signals Google already trusts: page titles, meta descriptions, heading structure, image alt text, and internal links. Rewrite them where they were weak, but never lose them by accident. And confirm the staging site is blocked from indexing while it is in progress, then confirm someone owns the job of unblocking it at launch. Both halves of that step have burned real businesses.
Launch Day: Verify, Don't Assume
Everything on launch day is checkable within an hour, and every item has caused a traffic collapse for someone who skipped it:
- Test the redirects. Take your crawl list from the benchmark and run it: every old URL should resolve with a single 301 to the right new page
- Confirm "noindex" is gone and robots.txt is not blocking the site
- Submit the new XML sitemap in Search Console
- If the domain changed, file the change of address in Search Console
- Spot-check titles and descriptions on your top 20 pages against the benchmark
- Verify analytics and conversion tracking fire on the new site
- Click through the main navigation and key internal links looking for anything pointing at old URLs or staging URLs
After Launch: Monitor Until It Settles
Rankings wobble after a migration even when everything was done right. Google has to recrawl the site, process the redirects, and re-evaluate pages in their new form. That is normal for a few weeks. What you are watching for is the difference between a wobble and a slide:
- Track your benchmark keywords daily for the first month, then weekly
- Watch Search Console's coverage report: indexed pages should transition, not shrink
- Check the crawl stats and 404 report; a spike in 404s means the redirect map missed something
- Compare page-level traffic against the benchmark month over month
- Keep the redirects live permanently. Old links around the web never update, and Google can take months to fully process the move
If a page loses ground and stays down past the settling period, diagnose it against the benchmark: is the redirect missing, is the new page thinner than the old one, or did an internal link disappear? The benchmark turns "traffic is down" from a mystery into a lookup.
The Bottom Line
None of this is difficult. It is disciplined, and that is exactly why it gets skipped when a launch is behind schedule and everyone just wants the new site live. Print the checklist, assign an owner to every item, and do not let launch enthusiasm override the boring steps. Your rankings took years to earn. Protecting them takes a few days of care.
Website Migration SEO FAQ
Does a website migration always hurt SEO?
No. A properly executed migration typically shows a brief fluctuation of a few weeks while Google recrawls and re-evaluates, and many well-run migrations show no visible dip at all. Sustained traffic losses come from execution failures: missing redirects, changed URLs with no mapping, blocked crawlers, or content that got thinner in the move. All of those are preventable, which is the whole point of the checklist.
How long does it take rankings to recover after a migration?
For a small business site with clean redirects, expect things to settle within four to eight weeks. Larger sites and domain changes can take three to six months for Google to fully process. If rankings are still sliding after the settling period, something specific is wrong, and the pre-migration benchmark is what lets you find it quickly.
Do I really need to redirect every single old URL?
Every URL that has traffic, rankings, or backlinks needs a redirect to its closest equivalent, and that usually covers more pages than you expect. Genuinely dead pages with no traffic and no links can be allowed to 404, but when in doubt, redirect. What you must not do is point everything at the homepage: Google treats bulk homepage redirects as soft 404s and discards the authority you were trying to preserve.
What is the most common website migration mistake?
Launching with no redirect map at all, usually because the new site was built by a team that treated URLs as a design detail. A close second: leaving the staging site's "noindex" setting on after launch, which quietly removes the entire site from Google until someone notices. Both are five-minute checks on launch day.
Should I migrate my site and redesign it at the same time?
It is common and it is fine, but change as few variables as you can. If you move platforms, redesign, and rewrite all your content simultaneously, a post-launch ranking drop becomes impossible to diagnose. Where possible, keep URL structure and core content stable through the move, then iterate on content afterward with data.
At K Squared Consulting, migration protection is built into every website redesign we ship, and our SEO migration service covers moves where another team is building the new site. You work directly with the founders. Let's talk.