Website Migration Checklist 2026: The Small-Business Guide to Moving Safely

A website migration — new design, new CMS, new domain, or all three — is the riskiest week in your website's life. Google treats it as a trust test: pages move, URLs change, and if the signals break, rankings can drop for weeks or months. Most of the damage is preventable, and the prevention is almost entirely planning.

The existing guides on this topic are written for enterprise teams with staging environments and SEO departments. This one is for the small-business owner or marketing manager coordinating a migration with an agency or freelancer: what to do, in what order, and what to watch — in plain language.

Before anything: what kind of migration is this?

Not all migrations carry the same risk. Know which one you're doing:

• Redesign, same URLs — lowest risk. The danger is broken templates, lost metadata, and content that quietly disappears in the redesign.

• CMS or platform change (e.g., WordPress to a custom build) — medium risk. URLs usually change, functionality needs rebuilding, redirects are essential.

• Domain change — highest risk. You're asking Google to transfer all trust to a new address. Everything must be airtight.

• HTTP to HTTPS — by 2026 this should be done already, but if it isn't, do it as part of the migration, not after.

If you're changing domains, be extra careful with every step below — and seriously consider professional help. A domain migration done badly can cost months of traffic.

Phase 1: Pre-launch — inventory everything (2–4 weeks before)

Crawl your current site. Use Screaming Frog (free under 500 URLs) or your CMS's sitemap to list every page. Record: URL, title, word count, traffic (Google Analytics), and backlinks (Search Console's Links report). This is your baseline — without it, you can't tell what the migration cost you.

Audit your content first. A migration is the worst time to carry dead weight and the best time to clean house. Run a content audit and decide each page's fate: keep, update, merge, or delete. Migrate only what's worth keeping.

Build the redirect map. For every old URL that won't exist at the same address, map it to the most relevant new URL — one-to-one, never bulk-redirect everything to the homepage. A spreadsheet with old URL → new URL → redirect type (301) is the single most important document in the migration. Every URL with traffic or backlinks gets a row.

Benchmark your metrics. Record current organic traffic, keyword positions for your top 20 terms, indexed page count (site: search), and Core Web Vitals scores. You'll compare against these weekly after launch.

Export everything. Full backup of the site, database, and media. Export your analytics data and Search Console history. Save a copy of the old site's HTML for at least a few key pages — you'll want it if something goes missing.

Phase 2: Staging — test before the world sees it (1–2 weeks before)

Build on staging, not live. Your agency should have a password-protected staging copy of the new site. Crawl it and check:

• Every important page exists and renders correctly (including on mobile).

• Title tags, meta descriptions, and headings transferred properly — redesigns are notorious for dropping metadata.

• Canonical tags point to the final URLs, not the staging domain.

• Structured data (schema) validates in Google's Rich Results Test.

• Internal links point to new URLs, not old ones.

Test the redirects on staging. The redirect map should be implemented and testable before launch day. Spot-check every high-traffic URL: old address → correct new address, single 301 hop, no chains, no loops.

Test what makes you money. Submit every form. Click every phone number and email link. Complete a test checkout or booking. Confirm conversion tracking fires (thank-you page views, events). Broken lead capture is the silent killer of migrations — the site looks fine, but enquiries quietly stop arriving.

Remove staging blocks. Make sure the staging site's "discourage search engines" setting and any noindex tags get removed on the production version. This is embarrassingly common and catastrophically easy to miss.

Phase 3: Launch day — the cutover

Launch day should be procedural, not dramatic. A calm checklist:

• [ ] Put up a maintenance notice if needed and take the final backup.

• [ ] Point DNS / go live with the new site.

• [ ] Verify the homepage and top 10 traffic pages load correctly (desktop and mobile).

• [ ] Verify redirects are live: test a sample of old URLs in a fresh browser session.

• [ ] Submit the new XML sitemap in Google Search Console; remove the old one.

• [ ] Confirm the robots.txt is the production version (not the staging block).

• [ ] Verify analytics and conversion tracking are recording.

• [ ] Test one form submission and one full conversion path end-to-end.

• [ ] Check that the SSL certificate covers all hostnames (www and non-www).

Do the launch early in the week and early in the day — never Friday afternoon. If something breaks, you want your agency awake and available.

Phase 4: The 60-day watch (after launch)

Migrations don't fail on launch day; they fail slowly over the following weeks. Monitor for at least 60 days:

• Week 1: Check Search Console daily — coverage errors, 404 spikes, indexing of new URLs. Crawl the live site and compare against your redirect map. Fix broken redirects within 24 hours.

• Weeks 2–4: Watch rankings and impressions for your top 20 keywords. Some fluctuation is normal; a sustained drop on a page means its redirect or content needs attention. Verify old URLs are dropping out of the index and new ones are entering.

• Weeks 4–8: Compare traffic against your pre-launch baseline. Check that backlinks still resolve (external sites linking to old URLs should now land on the right new pages via your redirects). Review server logs for 404s you missed.

What "normal" looks like: minor ranking wobble for 1–3 weeks, then recovery to baseline or better. What's not normal: traffic down 30%+ after a month, pages stuck unindexed, or a growing pile of 404 errors. That's a broken migration, and it needs immediate professional attention.

The 5 mistakes that cause most migration damage

1. No redirect map — launching and "letting Google figure it out." Google doesn't figure it out; it forgets.

2. Bulk redirects to the homepage — the lazy version of a redirect map. It tells Google the content is gone.

3. Migrating dead content — carrying 200 pages when 60 matter. Audit first, migrate what's worth keeping.

4. Forgetting conversion tracking — analytics breaks silently, and nobody notices the leads stopped for two weeks.

5. Launching Friday at 5 PM — because every migration has a surprise, and surprises need your team awake.

When to hire a professional (the honest threshold)

You can coordinate a simple redesign migration yourself with this checklist and a competent freelancer. Hire a specialist when: you're changing domains, your business depends heavily on organic traffic for revenue, you have 500+ pages, or you're moving to a fundamentally different platform. Migration rescue work costs far more than migration planning — our website redesign vs rebuild guide helps you scope the project, and business website builds start from $1,200 with a fixed quote after a free consultation. If you're still deciding whether to redesign at all, our business website cost guide covers the real numbers.

FAQs

How long does a website migration take to recover in rankings?

For a well-executed migration: minor fluctuation for 1–3 weeks, then recovery to baseline. Domain changes and sloppy migrations can take 2–6 months. If traffic hasn't recovered after 60 days, something is broken — audit the redirects and indexing, don't just wait.

Do I need redirects if my new site has the same pages?

If the URLs are byte-for-byte identical, redirects aren't needed — but verify, because redesigns almost always change something (trailing slashes, www vs non-www, category paths). If anything about the URL changed, redirect it.

Should I delete old blog posts during a migration?

Not automatically. Check each post's traffic and backlinks first — keep, update, or merge posts with value; only delete genuinely dead pages, and redirect the URLs.

Can I migrate my site myself without an agency?

For a simple redesign on the same platform with unchanged URLs, yes — this checklist covers it. For domain changes, platform switches, or revenue-critical sites, the risk/reward favors hiring someone who's done it before. One failed migration costs more than the professional fee.

What should I do if traffic drops after migration?

First, don't panic for two weeks — some wobble is normal. Then check: Search Console coverage errors, 404 spikes, redirect correctness (Screaming Frog), and whether key pages are actually indexed (site: operator). Fix 404s and broken redirects immediately; request re-indexing of critical pages.

Is it better to migrate everything at once or in phases?

For small-business sites, all at once — phased migrations multiply the testing and monitoring burden. Enterprise sites phase by section. Either way, the redirect map and the 60-day watch are non-negotiable.

Migrate like it's the riskiest week of your site's life — because it is

A website migration done right is uneventful: rankings wobble, recover, and the new site performs better. The difference between that and a disaster is the boring work — the inventory, the redirect map, the staging tests, the 60-day watch. Do the planning and the launch is just a Tuesday.

Planning a move? Contact us for a free consultation — we'll review your migration plan, flag the risks, and give you a fixed quote for the build. If your current plan is solid, we'll tell you that too.

Related reading

• Website Redesign vs Rebuild 2026 — decide what kind of project this actually is.

• Website Conversion Rate Optimization Checklist — once only the good pages survive the move, make them convert.

• Business Website Cost 2026 — what the project should cost.

• Website Maintenance Cost 2026 — what to budget after the launch.