A website migration can wipe out good rankings faster than most ad budgets can replace them. For a small business, that means fewer calls, form fills, and store visits.
A migration is closer to moving a store than repainting a room. If the signs, address changes, and forwarding steps break, customers and Google both get lost. This seo site migration checklist helps us protect traffic, leads, and local visibility before, during, and after launch.
Start by sizing the migration risk
Not every migration carries the same SEO risk. Still, each one changes signals that search engines use to find, index, and rank pages.
The common small business cases are easy to spot. A domain change moves every page to a new address. A redesign can remove strong content, internal links, and templates that already rank. A CMS switch, such as WordPress to Shopify, can change URLs, metadata, schema, and page speed. An HTTPS move can create duplicate protocol versions or mixed-content errors. A URL structure update can break old page paths that still earn clicks and links.
This quick view helps us set priorities:
| Migration type | Biggest risk | First priority |
|---|---|---|
| Domain change | Lost authority and broken paths | Map every old URL to its new match |
| Redesign | Deleted content and weak templates | Keep top content, headings, and links |
| CMS change | URL shifts and missing SEO fields | Test templates on staging |
| HTTPS move | Duplicate versions and mixed content | Force HTTP to HTTPS with 301s |
| URL cleanup | 404s and redirect chains | Use one-hop redirects |
For local businesses, another layer matters. If the website URL changes, we also need to update Google Business Profile, location pages, citations, and tracking tied to landing pages. Keep the business name, address, and phone consistent unless they truly changed.
Before migration, protect what already works
Most migration wins happen before launch. As O8’s prioritized migration tasks point out, the pages with traffic, backlinks, and leads deserve the most attention first.
Before anyone touches launch settings, we should capture a clean baseline. Export top landing pages, conversions, rankings, backlinks, indexed URLs, and local pages that drive calls. Then crawl the current site and keep that file. It becomes the shared map for our team, developer, and agency if something disappears later.
Next, build the migration plan around these steps:
- Crawl the current site and flag pages with traffic, links, leads, and local intent.
- Map every old URL to a new URL in a spreadsheet, page by page.
- Keep high-performing copy, title tags, headings, internal links, and schema unless there is a clear reason to change them.
- Test the new site on staging, while blocking it from indexing.
- Check mobile performance and Core Web Vitals, especially LCP, INP, and CLS.
- Set up analytics, Search Console, backups, and rollback access before launch day.
If the move is permanent, use 301s, not 302s. Our 301 vs 302 redirects guide explains the difference in plain language. Also, don’t dump old pages onto the homepage. Match each old URL to the closest live replacement.
The safest migration plan is simple: preserve first, improve second.
This matters even more during redesigns. We shouldn’t rewrite every service page at the same time we change templates, URLs, and hosting. Too many moving parts make drops harder to trace.
For CMS changes, template checks matter. Compare canonicals, title tags, structured data, image handling, and internal navigation before and after. If we’re replatforming an online store, Shopify’s replatforming SEO strategies offer a strong outside reference for product and collection URL changes.
Launch day is about clean handoffs
Launch day is not the time for guessing. We want every major SEO signal to point in one direction.
First, remove any staging noindex rules on the live site. Then confirm that robots.txt allows crawling and that the live XML sitemap lists only indexable canonical URLs. Our XML sitemap guide for SEO is useful if we need a quick check.
Next, test redirects in batches. Spot-check top pages, then crawl the old URLs to confirm they land in one hop on the right new page. Also update internal links, canonicals, structured data, navigation, and breadcrumbs so they point to final URLs, not redirected ones.
For domain changes, keep the old domain live and forwarding. Add both properties in Google Search Console, submit the new sitemap, and use Change of Address. For large URL changes, it also helps to submit one sitemap of new URLs and one list of old URLs that now redirect. For HTTPS moves, force all HTTP pages to HTTPS, fix mixed content, and pick one hostname, either www or non-www.
Local visibility needs the same care. Update the website URL in Google Business Profile, major directory listings, social profiles, and email templates. If a location page changed, update the link anywhere customers still find it.
A small drop for a week can happen. Long drops usually point to missed redirects, blocked crawling, or lost page content.
After migration, monitor the pages that make money
The first month after launch is where quiet problems show up. Search engines need time to recrawl, and small businesses often feel that delay in leads before rankings fully settle.
For the first week, we should check Search Console and analytics daily. After that, weekly reviews often work well for the next 4 to 6 weeks. Watch indexed pages, crawl errors, redirects, Core Web Vitals, and leads by landing page. A site can hold traffic overall while the pages that drive calls quietly lose visibility.
Keep an eye on the basics. Fix 404s fast. Remove redirect chains. Restore missing metadata, schema, or internal links. If rankings dip on key pages, compare the old version against the new one line by line. Often the issue is simpler than it looks, such as thinner copy, missing headings, or weak internal linking.
For a broader post-launch review, Omega Digital’s 2026 migration checklist is a helpful companion. We can also run a technical SEO checklist for migrations to catch speed, crawl, and indexing problems that surface after release.
The safest migrations are the boring ones
A careful migration doesn’t promise zero movement. It gives us control. When we keep redirects clean, content stable, and local signals updated, we protect the rankings and leads we’ve already earned.
That is the real goal of a good seo site migration checklist. We want the launch to feel uneventful because search engines, customers, and future leads can still find the right pages without friction.
