Start with a complete URL inventory, a one to one redirect map, and a staging build with immediate post-launch monitoring. Those three moves protect your traffic more than anything else you can do. Before touching any of it, confirm you have full access to Google Search Console and analytics so you have a clean before and after picture. The phases below walk through exactly how to do each step, in order.
TL;DR:
- A comprehensive URL inventory and full access to Search Console and analytics are crucial for accurate pre- and post-migration comparison.
- Implement a one-to-one redirect map with 301 or 308 status codes, avoiding redirect chains and bulk redirects to preserve ranking signals.
- Set up a staging environment with proper crawled controls and run a thorough technical audit, including schema validation and internal link checks, before launch.
- Assign clear roles for redirect, DNS, analytics, and rollback decisions, and prepare a rollback plan triggered by sharp traffic drops or error spikes within 48 hours.
- Post-launch, monitor traffic, crawl errors, and indexing daily for two weeks, then shift to weekly checks, ensuring that all major issues are resolved quickly.
Table of Contents
- Pre-migration planning: goals, inventory, and a rollback plan
- Build and test: staging environment, technical audits, and QA checklist
- URL mapping and redirects: build a 1:1 map, not a bulk shortcut
- Launch day checklist: what to verify in the first hour
- Post-launch monitoring: what to watch and for how long
- Practical tools and templates to run this checklist
- Backup and rollback strategy if something goes wrong
- What we see go wrong with small business migrations
- Get help running your migration without the guesswork
- Where to check the official guidance
- Sources
- FAQ
Pre-migration planning: goals, inventory, and a rollback plan
Every migration needs a written goal before anyone touches code. Are you moving domains, switching platforms, restructuring URLs, or all three at once? Write down what “success” looks like: traffic within a set range of pre-launch levels, conversion rate holding steady, and rankings for your top queries recovering within a defined window. Trying to redesign your site, change your domain, and rebuild your content structure at the same time is exactly the kind of layered change that Search Engine Journal warns makes it harder to diagnose what broke if traffic drops after launch.
Once goals are set, build your URL inventory. This is tedious but it is the single most valuable document you will produce during the entire project.
- Export every URL from your CMS database or admin panel.
- Pull your current XML sitemap and cross-check it against the CMS export.
- Export top landing pages and top queries from Search Console and analytics for the past 12 months.
- Pull a backlink list from your link tracking tool so you know which pages carry outside authority.
- Merge everything into one master spreadsheet and remove duplicates.
Before any build work starts, confirm you actually have administrative access to the tools that matter: Search Console, GA4, your tag manager, DNS settings, and the domain registrar account. Small businesses lose weeks when the person who originally set up analytics has left the company and nobody has the login. Export baseline reports now, while the current site is still live, covering top pages, top queries, referring domains, and conversion numbers by page. You cannot measure a drop later if you never wrote down what the previous period looked like.
Finally, assign clear roles.
- Someone owns the redirect map and signs off before launch.
- Someone owns DNS and server configuration changes.
- Someone owns analytics and Search Console verification.
- Someone owns the rollback decision and has authority to pull the trigger.
Write a rollback checklist with specific triggers: if organic sessions drop sharply within 48 hours, if Search Console shows a spike in 404 or 5xx errors, or if core conversion pages stop tracking, you revert. Decide this in advance, not while you are panicking at 2 a.m. on launch night.
Build and test: staging environment, technical audits, and QA checklist
Set up a staging environment that testers can reach but search engines cannot. The most common way teams accidentally leak a staging site into Google’s index is a missing or misconfigured robots.txt file, or a staging subdomain with no password protection at all. Use HTTP authentication or an IP allowlist rather than relying on robots.txt alone, since a blocked page can still get indexed if it is linked to from elsewhere.
Once staging is locked down, run a full technical audit before anyone signs off on launch.
- Crawl the entire staging site with a tool like Screaming Frog or Sitebulb to catch broken links, orphaned pages, and duplicate titles.
- Check that the staging sitemap only includes pages you intend to keep live.
- Validate canonical tags point to the correct new URLs, not leftover staging paths.
- Run structured data through Validator to confirm schema markup renders correctly on the new templates, a step covered in more detail in our guide to local business schema.
- Check hreflang tags if you serve multiple languages or regions, since a broken hreflang setup can quietly cannibalize rankings between versions.
Content checks matter as much as technical ones. Compare meta titles and descriptions, headings, and body copy against the old site to catch anything that got dropped during the rebuild, and review internal linking so your highest value pages are still reachable within a few clicks. Our breakdown of why website copy matters for SEO covers the content side of this audit in more depth. Test your primary conversion paths, quote forms, booking widgets, checkout flows, end to end on staging, and check page speed and mobile rendering before launch, since a slower new site can undo any SEO gains from the migration itself.
Pro Tip: Keep a copy of the staging robots.txt file separate from the production one in version control, so nobody accidentally pushes the “disallow everything” version live.
URL mapping and redirects: build a 1:1 map, not a bulk shortcut
Your redirect map is the backbone of the entire migration. Start by prioritizing which pages need mapping first.
- Rank pages by organic traffic volume over the past 12 months.
- Layer in pages that drive the most conversions, even if traffic is modest.
- Add every page currently indexed in Search Console.
- Add every page that shows up as a target in your backlink export.
- Map the remaining long-tail pages last, to their nearest topical equivalent, never to the homepage by default.
For implementation, Google Search Central recommends server-side permanent redirects, specifically 301 or 308 status codes, and explicitly warns against redirect chains and temporary 302 redirects because they slow down how quickly search engines transfer ranking signals to the new URL. Keep every redirect a single hop: old URL straight to new URL, never old URL to an intermediate URL before the final destination. Mass-redirecting dozens of unique pages to your homepage might feel like a shortcut, but it tells search engines those pages no longer have distinct value, and you lose whatever ranking signal each one carried individually.
Redirects need real testing, not a spot check. Crawl the full redirect map in a tool like Screaming Frog in “list mode” to confirm every source URL returns the expected status code, then manually click through a sample of high-traffic pages on the live site to confirm the destination renders correctly and the canonical tag matches.
Once you move to a new domain, the Search Console Change of Address tool tells Google directly, but only after your redirects are live and you have verified ownership of both the old and new properties. Google’s own guidance says to keep those redirects in place for a sufficient period after a domain-level move, since search engines need that window to fully transfer signals.
Launch day checklist: what to verify in the first hour
Launch day succeeds or fails in the first sixty minutes. Work through checks in this order.
- Confirm the production robots.txt allows crawling and does not contain leftover staging “disallow all” rules.
- Confirm analytics and tag manager are firing on the live domain by watching real-time reports.
- Crawl a sample of your redirect map on the live site to confirm status codes and final destinations are correct.
- Submit the updated XML sitemap in Search Console and confirm the new property is verified.
- Spot check canonical tags and hreflang attributes on a handful of key pages.
- Run your most important templates through the schema validator one more time on the live URLs.
- Check rendering and load behavior on both desktop and mobile for your top five landing pages.
If organic sessions or crawl activity drop sharply within the first day, treat it as a configuration error until proven otherwise. Missing tracking code and accidental crawl blocks are far more common causes than a genuine ranking penalty. Check server logs and Search Console crawl stats first, and have the person who owns DNS and the person who owns analytics both reachable by phone, not just Slack, for the first 24 hours.
Post-launch monitoring: what to watch and for how long
The first two weeks after launch deserve daily attention. Check GA4 sessions against your pre-launch baseline, watch Search Console’s coverage report for spikes in errors or excluded pages, and review crawl stats for sudden drops in pages crawled per day. Server logs will show you whether search engine bots are actually reaching your new URLs or hitting dead ends.
From weeks three through twelve, you can shift to weekly checks.
Want this running in your business without doing it yourself?
Book a Free Consultation →- Track keyword position changes for your priority terms against the pre-migration baseline.
- Watch indexation progress in Search Console until most of your important pages show as indexed.
- Review your backlink profile to confirm major referring domains are pointing at the new URLs.
- Monitor top landing pages for traffic and conversion recovery, not just raw session counts.
When problems surface, fix in priority order: broken redirects first, since they cause the most direct signal loss, then canonical errors, then missing or misfiring analytics tags. Watch for soft 404s too, pages that return a 200 status but show a “not found” style message, since these quietly waste crawl budget and confuse indexing. Keep your rollback triggers from the planning phase visible and revisit them honestly if metrics do not recover on the timeline you expected.
Pro Tip: Set a recurring calendar reminder to check Search Console’s Change of Address status and redirect coverage at the 30, 90, and 180 day marks, since that final window is when Google expects you to still have redirects live.
Practical tools and templates to run this checklist
You do not need an expensive toolkit to execute this properly. A site crawler like Screaming Frog or Sitebulb handles technical audits and redirect testing. Google Search Console and GA4 cover indexing, crawl stats, and traffic monitoring at no cost. The schema validator checks structured data before and after launch, and the official Google guidance on site moves is worth bookmarking directly.
For the redirect map itself, a shared Google Sheet works fine for most small teams.
- Old URL and new URL columns, filled in exactly as they appear in your CMS export.
- Status column, tracking whether each redirect is mapped, implemented, or tested.
- Notes column for anything unusual, like a page being merged into a broader topic.
- Owner column so everyone knows who signs off on that row.
Backup and rollback strategy if something goes wrong
Take a full backup of your database, files, and current DNS settings before you touch anything, and confirm the backup actually restores correctly on a test environment rather than assuming the export worked. This single step is the difference between a stressful hour and a lost weekend if the migration goes sideways.
Your rollback plan should specify exactly what “reverting” means for your setup. For most small businesses, the fastest fix is reverting a DNS change or removing a staging block, not trying to patch individual broken pages one at a time while traffic keeps falling. Keep the old hosting environment or domain accessible for at least the first two weeks after launch, even if you plan to cancel it eventually, so a full reversion stays possible.
Decide who has the authority to call a rollback and make sure that person is reachable on launch day and for the following 48 hours. Document the specific triggers from your planning phase: a defined drop in organic sessions, a spike in server errors, or lost tracking on conversion pages. Having those thresholds written down before launch removes the guesswork when something actually looks wrong, and it keeps the decision from becoming an argument in the middle of a crisis.
What we see go wrong with small business migrations
The most frequent mistake is leaving the staging robots.txt file active on the live domain, quietly blocking search engines from the new site for days before anyone notices. A close second is analytics tracking that never got reinstalled on the new templates, leaving weeks of blind spots. We also see redirect maps that funnel dozens of unique pages straight to the homepage instead of their closest topical match. Our free SEO audit surfaces these exact risk items before they cost you traffic.
— Cristo
Get help running your migration without the guesswork
Running this checklist solo takes real hours, and a missed redirect or a forgotten analytics tag can cost you rankings you spent years building. A digital agency builds and migrates websites in-house, with no outsourcing, so the same team that maps your redirects also handles your SEO and analytics setup on the new site.
If you want a second set of eyes before you launch, our free SEO audit reviews your current site and flags migration risk items like orphaned pages, thin redirects, and missing schema. From there:
- Our Website Development team handles staging builds, redirect implementation, and launch day technical checks.
- Our SEO and Local Search service covers the Search Console work, structured data, and post-launch monitoring.
- Plans run month to month with no lock-in contract, and pricing starts with the Sprout plan at $300 CAD per month.
Start with the free audit, see exactly what a migration would touch on your site, and decide from there whether you want to run it yourself or hand it to a team that does this for a living.
Where to check the official guidance
- Google’s site move documentation for redirect and crawling rules.
- Search Console’s Change of Address tool guide for domain moves.
- Validator for structured data checks.
- A 4 to 8 week migration timeline breakdown for planning cadence.
Sources
- Move a site with URL changes – Google Search Central
- Change of address – Search Console Help
- Google: Don’t Combine Site Moves With Other Big Changes – Search Engine Journal
- Validator
FAQ
What are the steps involved in a website migration?
A migration generally moves through pre-migration planning, staging build and testing, redirect mapping, launch day validation, and several weeks of post-launch monitoring. Each phase in this checklist builds on the last, starting with a full URL inventory and ending with weekly reporting on rankings and traffic recovery.
What are the 7 migration strategies?
There is no single official list of seven migration strategies, and definitions vary by source. In practice, most migrations fall into a handful of categories: domain changes, platform changes, URL structure changes, HTTP to HTTPS moves, content consolidations, design relaunches, and combinations of these, each requiring the same redirect and monitoring discipline described above.
What are the key SEO checklists for website migration?
The core items are a complete URL inventory, a one to one redirect map using server-side 301 or 308 redirects, a locked staging environment for testing, and post-launch monitoring through Search Console and analytics. Structured data validation and a documented rollback plan round out the essentials.
How do I migrate a website without losing SEO?
Preserve SEO by mapping every important old URL to its closest new equivalent with a single-hop permanent redirect, never a chain or a bulk redirect to the homepage. Use the Search Console Change of Address tool for domain moves, keep redirects live for at least 180 days, and monitor indexing and crawl stats daily for the first two weeks after launch.
Recommended
Less reading. More growing.
We build the systems these articles describe. Websites, AI follow-up, reviews, automation. And run them for you.
Keep reading
3–12 Month Runway: Month to Month SEO for Small Businesses in Canada
