
Website Migration SEO: A Checklist for Moving URLs Without Losing Rankings
A website migration SEO checklist for domain, HTTPS, and URL changes: build the redirect map, set up Search Console, and know what normal recovery looks like.
October 30, 2026 · 11 min read
A website migration is any change where your pages end up at new URLs: a new domain, a switch from HTTP to HTTPS, a new folder structure, or a move to a different CMS that writes its slugs differently. That is what separates it from a redesign. If you're only changing how the site looks and every URL stays the same, start with our website redesign SEO guide instead. It covers the template and launch-day risks.
When URLs change, Google has to rediscover every page, follow a redirect to its new home, and transfer what it knew about the old URL. Google's own site move documentation says to "expect temporary fluctuation in site ranking during the move," and that for medium-sized websites "it can take a few weeks or more for Google to gradually start showing the new URLs instead of the old ones."
So a dip is normal. Losing traffic for good usually means one of three things went wrong:
- Old URLs that don't redirect, or redirect to the wrong place.
- A new site Google can't fully crawl or index.
- Signals still pointing at the old URLs: internal links, canonicals, sitemaps.
This guide covers each one in the order you'll hit it, with a checklist at the end.
What Kind of Website Migration Are You Doing?
The steps overlap, but the risk and the tools are different for each type. Name yours before you plan anything.
| Migration type | Example | Change of Address tool? | Main risk |
| --- | --- | --- | --- |
| Domain change | oldblog.com → newblog.com | Yes | Every URL changes at once; old backlinks point at the old domain |
| Subdomain move | blog.example.com → blog.newsite.com | Yes | Same as a domain change, scoped to one subdomain |
| HTTP → HTTPS | http:// → https:// | No | Mixed content, canonicals and sitemaps left on http:// |
| URL structure change | /2024/05/post-name/ → /blog/post-name/ | No | Large redirect map, easy to leave gaps |
| Platform / CMS move | WordPress → another CMS | Only if the domain changes too | New system writes different slugs, drops pages, changes templates |
Google's Change of Address tool documentation is explicit about the HTTPS case: "For an http to https move, follow the guidelines for site move with URL changes, but don't use this tool; Google will figure out your changes for you." The same goes for moving pages around inside one site, where Google says to "just add redirects, and update your sitemaps as appropriate."
If you can, avoid stacking types. Google's migration guide suggests you "split your move into smaller steps, if that makes sense for your site." A domain change on Monday and a URL restructure the following month is much easier to debug than both at once.
Step 1: Build the Redirect Map Before You Touch Anything
The redirect map is the core of every migration. It is a spreadsheet with one row per old URL and a column for where it should go. Google calls this step out directly: "It's important to map your old site's URLs to the URLs for the new site."
Collect every old URL, not just the ones in your sitemap. Combine three sources:
- Your current XML sitemap.
- A crawl of the live site.
- The Pages tab of the Search Console Performance report, exported for the last 12 months. This catches URLs Google still shows that your sitemap forgot.
Add your top linked pages too. If you track backlinks, export the target URLs so posts with external links don't get lost in the move. Our guide to backlink monitoring covers where to get that list.
Decide where each URL goes. Google's guidance is: "Once you have the listing of old URLs, decide where each one should redirect to." There are three valid answers:
- Same content, new URL: redirect one-to-one. This should be most rows.
- Merged content: redirect to the page that now covers the topic.
- Content you're dropping: don't redirect it to the homepage. Google says to "make sure those URLs correctly return an HTTP
404or410error response code on the new site." Sending dozens of unrelated pages to the homepage tends to get them treated as soft 404s anyway.
Choose permanent, server-side redirects. Google recommends "server side permanent redirects from the old URLs to the new URLs as you indicated in your mapping," and notes that "301 and other permanent redirects don't cause a loss in PageRank." JavaScript or meta-refresh redirects are a fallback, not a plan.
Point each old URL straight at its final destination. If you've moved before, old URLs may already redirect somewhere. Update those rules so they go to the new final URL in one hop. Our redirect chain checker guide shows how to find chains before they multiply.
Step 2: Prepare Search Console for Both Sites
Do this a few days before launch, not on the day.
- Verify both properties. Google's guide says: "verify both the old and new sites in Search Console. Be sure to verify all variants of both the old and new sites." A Domain property covers
http,https, andwwwvariants in one place. - Use the same Google account for both, if you plan to use the Change of Address tool. Google requires that "You must be an owner of both the old and new properties in Search Console" and "You must use the same Google account to manage both properties."
- Export a baseline. Save page-level clicks, impressions, and average position for the old site. After launch the old property's numbers will fall towards zero, so this export is your only "before" picture. Our Search Console performance report guide explains which columns to trust.
- Prepare the new sitemap. It should list only final URLs on the new site that return
200, are indexable, and aren't redirected. See sitemap best practices for what belongs in it, or our WordPress sitemap guide if you're on WordPress.
Step 3: Migration Day Checklist
Turn on the redirects and check the new site within the first hour, while rolling back is still cheap.
Test a sample of redirects by hand. Take 20 rows from your map, including your highest-traffic pages and a few deep posts, and load each old URL. Each should return a single 301 or 308 and land on the right page with a 200. Test both http:// and https://, and both www and non-www, of the old URLs.
Check the new site isn't blocked. Staging sites are often protected with noindex or a Disallow: / in robots.txt. Google's guide reminds you to remove "any noindex or robots.txt blocks that were only needed for the migration."
Update canonicals, internal links, and hreflang. Each new page should have a self-referencing canonical; Google says "Each new URL should have a self-referencing rel="canonical" <link> tag." Google also advises: "Change the internal links on the new site from the old URLs to the new URLs." Internal links that still go through redirects cost you crawl time and leak the old structure back into Google's view. That is part of how link equity flows around a site. If you use hreflang, Google's guide says "be sure to update the annotations to use the new URLs."
Submit the new sitemap in the new property. Google notes that "Submitting a sitemap can help make the discovery process quicker."
File the Change of Address request, if it applies. Only for domain or subdomain moves, and only after redirects are live. Google's prerequisite list includes "Implement a 301 redirect from your old homepage to your new homepage." The tool works only on domain-level properties ("You cannot move properties at the path level"), and it "does not move any subdomains below the specified domain (including www)."
How Long Does SEO Recovery Take After a Migration?
There is no fixed number, but Google gives a few useful markers:
- "To consider a site move complete, Googlebot will have to visit every URL on your old and new site at least once." Small blogs get recrawled faster than large sites.
- The Change of Address tool's effects "continue for 180 days after you start migration in Search Console."
- Google says to "Maintain the redirects for at least 180 days--longer if you still see any traffic to them from Google Search." In practice, keep them as long as you own the old domain. The same page recommends "continuing to pay for the old domain for at least a year."
Week to week, a healthy migration looks like this in Search Console: old-property impressions fall while new-property impressions rise to meet them, and total clicks across the two dip and then settle near the old level. If the new property's line stays flat while the old one falls, Google isn't picking up the new URLs. That points to redirects, blocks, or canonicals.
What to check while you wait:
- Pages report on the new property. Watch for "Not found (404)," "Excluded by 'noindex' tag," and "Blocked by robots.txt" climbing after launch.
- Pages report on the old property. You should see old URLs move into Page with redirect. That's the expected status, not an error.
- URL Inspection on your top pages. Confirm Google has indexed the new URL and picked it as the canonical.
Common Website Migration SEO Mistakes
These are the patterns that show up again and again in migrations that don't recover:
| Mistake | What you'll see | Fix |
| --- | --- | --- |
| Redirecting everything to the homepage | Old pages reported as soft 404s; deep-post rankings vanish | Redirect one-to-one; return 404/410 for truly removed pages |
| Temporary (302) redirects left in place | New URLs slow to replace old ones in results | Switch to 301 or 308 |
| Redirect chains from earlier moves | Slow recrawl, some old URLs never update | Point every old URL straight at its final URL |
| Sitemap still lists old URLs | "Page with redirect" warnings for sitemap URLs | Submit a sitemap with only final new URLs |
| Canonicals pointing at the old domain | Google keeps showing old URLs | Self-referencing canonicals on the new site |
| Removing redirects after a few weeks | Old backlinks and bookmarks start returning 404 | Keep redirects at least 180 days, ideally while you own the domain |
| Changing domain, URLs, and design at once | You can't tell which change caused a drop | Split the move into steps |
If traffic still hasn't recovered after a couple of months and none of these apply, the cause may not be the migration at all. Our guide to why blog traffic drops covers updates and seasonal patterns that can land in the same weeks.
The hardest part of a migration is the watching. You need to compare page-level numbers every week for months, across two properties, and spot the handful of posts that didn't make the jump. Traffic Monitor connects to Search Console with read-only access and shows your clicks, impressions, CTR, and post performance, updated daily. On the Growth plan it sends a Discord alert when a post spikes or drops, so a page that loses its traffic after the move gets noticed in days. You can connect a blog on the free plan to start.
Website Migration SEO Checklist (Copy This)
Planning
- Name the migration type: domain, subdomain, HTTPS, URL structure, or platform.
- Split it into separate steps if you're changing more than one thing.
- Collect every old URL from the sitemap, a crawl, and 12 months of Search Console data.
- Map each old URL to a new one, or mark it
404/410if it's gone.
Before launch
- Verify both old and new sites in Search Console, all variants.
- Export a baseline of page-level clicks, impressions, and position.
- Build the new sitemap with only final, indexable URLs.
- Update internal links, canonicals, and hreflang on the new site.
Launch day
- Turn on server-side
301/308redirects. - Test 20 old URLs, including all protocol and
wwwvariants. - Remove staging
noindextags and robots.txt blocks. - Submit the new sitemap.
- File a Change of Address request (domain or subdomain moves only).
Afterwards
- Compare old and new property traffic weekly.
- Watch the Pages report on both properties.
- Inspect top pages to confirm the new URL is indexed and canonical.
- Keep redirects for at least 180 days, and keep the old domain for at least a year.
Related posts
How to Add a User to Google Search Console (And Which Permission to Give)
How to add a user to Google Search Console, which level to pick (Owner, Full, or Restricted), the per-property limits, and how to remove access safely.
SEO Chrome Extensions for Bloggers: 6 Free Ones Worth Installing (And What Each Can't See)
The free SEO Chrome extensions a blogger actually needs, matched to one job each, plus the one Google retired and what no extension can tell you.
Track your blog rankings automatically
Connect Google Search Console and get daily alerts, keyword research, and AI diagnostics — free to start.
Start free →