Most migrations that lose traffic do not fail on launch day. They fail weeks later, when someone notices leads have dropped and finds hundreds of old URLs returning 404s, a staging noindex tag still sitting in the header, and a menu that links to pages that no longer exist. This website migration SEO checklist is built to catch those problems before Google does.
It covers domain changes, HTTPS switches, platform moves (Wix or Squarespace to WordPress is the one we see most), URL restructures and host-only moves. Work through it in order: before, during, after.
One honest note first. Some ranking movement after a migration is normal, even when everything is done right, because Google has to recrawl and re-evaluate every moved URL. Anyone promising zero loss is guessing. A good process gives you a short, shallow dip instead of a long, deep one.
Which type of migration are you doing? (and how risky is it)
The SEO risk of a migration depends mostly on how many URLs change. A host-only move changes none and is low risk; a domain change combined with a platform move and new URL structure changes all of them and is the riskiest thing you can do to a site.
| Migration type | Do URLs change? | SEO risk | Where it usually goes wrong |
|---|---|---|---|
| Host-only move (same domain, same CMS) | No | Low | DNS cutover downtime, slower server, missing SSL certificate, robots.txt not copied |
| HTTP to HTTPS | Protocol only | Low to medium | Mixed content, canonicals and sitemaps still on http://, redirect chains through www/non-www |
| URL restructure (same domain) | Yes, some or all | Medium | Incomplete redirect map, internal links not updated, category pages dropped |
| Platform move (e.g. Wix or Squarespace to WordPress) | Usually yes | Medium to high | Platform URL patterns (Wix’s /post/, Squarespace collection slugs) not mapped, titles and meta descriptions not carried over, image URLs lost |
| Domain change (e.g. .ca to .com, rebrand) | Yes, all | High | Change of Address not submitted, old domain allowed to expire, backlinks never updated |
| Domain + platform + structure at once | Yes, all, with new patterns | Highest | Everything above, and no way to tell which change caused a drop |
That last row is the trade-off nobody likes. Splitting a rebrand into stages (platform first, domain later) is safer and makes problems easier to diagnose. It also means two rounds of disruption and QA. For a small brochure site, doing it all at once is often sensible. For a store with thousands of product URLs, we would usually stage it. There is no universal answer.
A Canadian-specific point: moving from a .ca to a .com is not neutral. A .ca is a country-code domain that Google treats as a signal the site is relevant to Canada. Moving a Canada-focused business to a generic .com gives that up, so the new site should still say clearly who it serves (local addresses, CAD pricing, and correct hreflang such as en-ca and fr-ca if you run bilingual versions).
Before the migration: the SEO migration checklist for prep work
Before you move anything, record exactly what the current site has and what it ranks for, so you can prove after launch that nothing went missing. Most of the work in a good migration happens here.
- Crawl the old site in full. Run Screaming Frog SEO Spider (or Sitebulb) against the live site and export every URL with its status code, title, meta description, H1, canonical and word count. This is your baseline.
- Pull URLs the crawler cannot find. Orphan pages, old campaign landing pages and PDFs often have links and traffic but no internal links. Export pages from Google Search Console, GA4 landing pages, your XML sitemaps, and top linked pages in Ahrefs or Semrush, then de-duplicate.
- Benchmark performance. Export at least 12 months of Search Console clicks and impressions by page and query, and GA4 organic sessions and conversions by landing page. Set up rank tracking on your important keywords a few weeks before launch so you have a pre-move line to compare against.
- Flag the pages that matter most. Sort by organic clicks, conversions and referring domains. Those pages get manual QA after launch.
- Build the 301 redirect map (worked example below).
- Carry over on-page SEO. Titles, meta descriptions, headings, image alt text, structured data and Open Graph tags. A Wix site’s SEO settings do not import themselves into Rank Math or Yoast.
- Verify Search Console for the new property (and keep the old one). For a domain change you need both verified to use the Change of Address tool.
- Pick a quiet launch window. Avoid seasonal peaks and Friday afternoons.
If you are also changing hosting or moving a WordPress install between servers, our guide on how to transfer a WordPress website covers the file, database and DNS side in detail.
How to build a 301 redirect map (worked example)
A 301 redirect map is a spreadsheet with one row per old URL and the single best matching new URL next to it. Every old URL that had traffic, links or rankings should point to its closest equivalent, not to the homepage.
Here is what that looks like for a hypothetical Toronto renovation company moving from Wix on a .ca domain to WordPress on a .com:
| Old URL | New URL | Note |
|---|---|---|
| example.ca/ | example.com/ | Homepage to homepage |
| example.ca/kitchen-renovations | example.com/services/kitchen-renovations/ | Service now sits in a folder |
| example.ca/post/how-much-does-a-basement-reno-cost | example.com/blog/basement-renovation-cost/ | Wix blog pattern, slug shortened |
| example.ca/blog/categories/tips | example.com/blog/category/tips/ | Category archive kept |
| example.ca/old-spring-promo | example.com/services/ | No equivalent: nearest relevant parent |
| example.ca/gallery-2019 | (none, return 410) | No traffic, no links, no replacement |
A few rules that save pain later:
- One hop only. Old URL goes straight to the final URL. If the site previously moved from http:// to https://, make sure http://example.ca/page goes directly to https://example.com/page/, not through three redirects.
- Match trailing slashes and case to whatever the new site actually serves, or every redirect becomes a two-step chain.
- Use server-side permanent redirects (301 or 308), not JavaScript or meta refresh. Google’s redirects documentation explains how it treats each type.
- Do not dump everything on the homepage. Google tends to treat irrelevant mass redirects as soft 404s.
- Use patterns where the structure is predictable (for example, every
/post/slugto/blog/slug/), add one-to-one rules for exceptions, and test against the full URL list.
On WordPress, redirects can live in the server config (Apache .htaccess or Nginx), at the edge with Cloudflare redirect rules, or in a plugin such as Rank Math’s Redirections module. Server or edge rules scale better; a plugin is easier for a marketing team to maintain.
During the migration: launch day checks
On launch day, the job is to switch the site over, make the redirects live, and confirm within the first hour that search engines can crawl and index the new site.
- Remove staging blocks. Check the robots meta tag on several templates, the
X-Robots-TagHTTP header, robots.txt, and in WordPress the “Discourage search engines from indexing this site” box under Settings, Reading. - Remove password protection or HTTP authentication from the staging environment if that is what went live.
- Deploy the redirects and test a sample of your highest-value old URLs by hand.
- Check canonical tags point to the new URLs on the new domain, not to staging and not to the old domain.
- Update and submit the XML sitemap on the new site in Search Console. It should list only new, indexable, 200-status URLs.
- Confirm analytics and tag tracking fire on the new site: GA4, Google Tag Manager, conversion pixels, call tracking.
- Submit the Change of Address request in the old Search Console property (domain changes only, see below).
The staging noindex mistake
This is the most common way a well-built site vanishes from Google. The developer correctly blocks staging from indexing, the site goes live by copying the database, and the setting comes along. Nobody notices because the site looks fine in a browser. Make “view source and search for noindex” a named step on the launch checklist, with a person responsible for it.
Domain change SEO: using Search Console’s Change of Address tool
If you are moving from one domain or subdomain to another, submit the move in Google Search Console’s Change of Address tool after your redirects are live. It tells Google the move is deliberate and helps it shift search results to the new site.
Some details from Google’s Change of Address help page that people miss:
- It works at the domain level only. You cannot use it to move a path such as example.com/shop/.
- It does not move subdomains below the one you specify, including www. Submit it for every variant of the old domain you have verified (www, non-www, and any others) even if you were not actively using them.
- Google asks you to keep redirects for at least 180 days, longer if the old URLs still get Google traffic, and recommends keeping the old domain registered for at least a year so nobody else buys it.
Google’s broader guide to site moves with URL changes goes further and says to keep redirects “as long as possible, generally at least 1 year.” We would keep them indefinitely: old links from directories and partner sites point at those URLs for years, and renewing a domain is cheap.
For a host-only move where no URL changes, Google has a separate, shorter guide on moving a site without URL changes. The main risks there are downtime and a slower server, not lost URLs.
After the migration: crawl old vs new and fix what broke
After launch, crawl your full list of old URLs to confirm each one redirects in a single hop to a live page, then crawl the new site to find broken internal links and indexing blocks. Repeat checks over the following weeks while Google recrawls.
Crawling old vs new with Screaming Frog
- Old URL list check. In Screaming Frog, switch to List mode, paste or upload every old URL from your baseline, enable “Always Follow Redirects” in the spider configuration, and crawl. The Redirect Chains report shows the final destination and hop count for each. You want every row to end on a 200 page in one hop.
- New site crawl. Crawl the new site in Spider mode. Filter for 4xx responses, internal redirects (3xx), non-indexable pages and missing titles. Compare page counts with the baseline: if the old site had 600 indexable pages and the new one has 350, find out where the other 250 went.
- Compare on-page elements. Join both exports on the redirect map and check that titles, H1s and word counts on your top pages survived. Thin replacement pages quietly cost rankings.
Internal links still pointing to old URLs
Redirects catch them, so many teams leave them. Don’t. Every one forces an extra hop for users and crawlers, and they hide in post content, page-builder buttons and footer widgets. In WordPress, a search-and-replace on the database (WP-CLI’s search-replace command or a plugin like Better Search Replace, after a backup) fixes most of them in one pass.
Monitoring for the following weeks
- Watch Search Console’s Page indexing report on both properties: new URLs should climb while old ones move to “Page with redirect”.
- Review 404s in server logs or a 404 monitor and add redirects for anything with traffic or links that the map missed.
- Compare GA4 organic landing pages and conversions week over week against your benchmark.
- Update the links you control (Google Business Profile, social profiles, directories, ad destinations) and ask your best referring sites to update theirs.
- Run a Core Web Vitals check on the new templates. A new theme or host can be slower than the old one. Our technical SEO guide on Core Web Vitals and crawlability walks through what to look at.
Google’s own guidance says a small to medium site can take a few weeks for most pages to move in its index, and larger sites take longer. A dip in week one is not a reason to undo the migration. A drop that keeps worsening after a month, or one concentrated on specific page groups, usually means missing redirects, lost content or an indexing block on one template.
How to migrate a website without losing SEO: the mistakes we see most
Most lost rankings come from avoidable mistakes, usually because the move was run as a design project with SEO checked at the end.
- Content cut during the redesign. Long service pages and old posts get trimmed for a cleaner design, and they were the pages ranking for long-tail searches. Cut with traffic data in front of you.
- Old domain allowed to lapse. Usually at renewal time, after the person who ran the migration has moved on. Put it on someone’s calendar.
- Too many changes at once with no way to isolate which one caused a drop.
If you are weighing a platform move in the first place, our piece on why migrating to WordPress is often the right decision covers the business case. When we handle WordPress migration services for clients in the US and Canada, the redirect map and the before/after crawl are part of the build, not an add-on, and our SEO services team can audit a migration that has already happened and gone wrong. If the move includes a full rebuild, see our WordPress website development services.
Website migration checklist FAQ
Will I lose rankings when I migrate my website?
You may see temporary fluctuation while Google recrawls the new URLs, even with a clean migration. Nobody can honestly guarantee zero loss.
How long should I keep 301 redirects after a site migration?
Google’s site-move guide says as long as possible, generally at least one year.
Do I need the Change of Address tool for an HTTPS switch?
The tool is built for moves from one domain or subdomain to another. For an HTTP to HTTPS switch on the same domain, sitewide 301 redirects, updated canonicals and an HTTPS sitemap do the work.
Should I redirect deleted pages to the homepage?
No. Redirect to the closest relevant page. If there is no reasonable equivalent and the page had no traffic or links, letting it return a 404 or 410 is cleaner than a misleading redirect.
Does changing hosts affect SEO?
Not if URLs stay the same and the site stays up. The risks are downtime, a slower server, and robots.txt or SSL not being copied across.




