Search Console tells the truth the week after a migration goes live, and marketing leaders spend that week refreshing it every hour, waiting to see whether the redirect map held or rankings started to slide.
Most teams treat a website migration as a technical handoff, but a website migration SEO checklist changes that. It's a phased, checkable task list covering redirects, backups, and monitoring. Marketing and development teams use it together to protect search rankings and organic revenue when a site changes domains, platforms, or URL structure.
This one runs 25–40 items across three phases: pre-migration, launch day, and post-launch. Copy it into your project tracker, assign owners, and use it to catch the mistakes that quietly cost sites their organic traffic long after launch day looks like a success.
You'll find clear ownership for every task, the redirect coverage that keeps link equity intact, and the post-launch monitoring cadence that catches problems before they show up in a board meeting.
Key takeaways
- Redirect mapping needs four separate checklist blocks, not one table, covering standard URLs, parameters, non-HTML assets, and canonical decisions.
- Choosing between a redirect and a canonical tag depends on whether the old URL should disappear or coexist with a variant.
- A fixed monitoring cadence with named owners at day 1, 3, 7, 14, and 30 catches ranking drops faster than vague weekly check-ins.
- Comparing indexed page counts against submitted sitemap numbers on a set schedule reveals crawl problems before rankings visibly drop.
- Preserving structured data and robot’s directives during migration protects citation continuity in AI answers, not just traditional search rankings.
Confirm scope, team, and baseline data
Lock down migration type and scope, assign named owners, and capture baseline traffic, rankings, and indexed-page counts before any redirect or development work starts. Build this into a tracker with fields for owner, milestone, and status, so nothing sits with an unnamed party.
- Confirm migration type (domain, platform, or structure change) and full scope, with a named owner and escalation contact.
- Export baseline traffic, rankings, conversions, and indexed pages from Google Search Console (GSC).
- Prepare Screaming Frog for crawl comparisons and Ahrefs for backlink and ranking history.
For the full sequence, follow our website migration checklist.
Map every redirect before migration day
A complete redirect plan splits into four checkable workstreams: standard URLs, parameterized and filtered pages, non-HTML assets and campaign pages, and canonical decisions. Treat each one as its own checklist below, and confirm coverage before you touch DNS.
Build 1:1 redirects for every URL
Every live URL needs a mapped 301 destination before launch. Chains longer than 3–5 hops or redirects pulled early risk lost rankings, and every 301 needs to stay live for at least a year, per Google's migration guidance.
Build your inventory using Screaming Frog's migration workflow:
- Crawl the live site
- Export every indexed URL
- Crawl staging
- Compare both lists side by side to catch gaps
Map each row to its closest live equivalent, not the homepage. A simple example: /services becomes /our-services.
Handle parameters, pagination, and filtered pages
Tracking parameters, paginated series, and filtered or faceted URLs each need their own mapping rule, as opposed to a blanket redirect to the root domain. Dumping every variant into your homepage buries the specific pages sales and campaigns still rely on.
Work through three checklist items separately:
- Preserve UTM and tracking strings on any redirect that still feeds attribution reporting.
- Map paginated series (page 2, page 3, etc.) to their equivalent destination on the new site.
- Flag filtered or faceted URLs for manual review, since indexing too many risks keyword cannibalization down the line.
Redirect non-HTML assets and campaign pages
PDFs, downloadable assets, hotlinked images, and old campaign landing pages carry indexed value and backlinks that a redirect map can’t skip. Google indexes PDFs the same way it indexes HTML pages, and a whitepaper with 40 referring domains loses all of that equity if it 404s on migration day.
Pull your indexed PDFs and downloadable assets first and prioritize the ones with backlinks or steady organic traffic. This is also where conversion-focused content tends to live, so a broken redirect here has revenue consequences.
Check your active campaign tracker for old paid-social and email URLs. Those links keep sending referral traffic long after the campaign ends, and an unmapped one turns a warm click into a dead end.
Choose between redirects and canonical tags
Situation
Use
Old URL should disappear permanently (e.g., a retired product page)
301 redirect
Both URL variants must remain live (e.g., a URL with a tracking parameter)
Canonical tag
Use a 301 redirect when the old URL should disappear permanently and use a canonical tag when both URL variants must remain live. A retired product page from your old site should stop resolving entirely and send both users and crawlers to its new home. A parameter variant, like a URL with a tracking tag appended, should stay accessible but point back to one canonical version.
Apply canonicalization consistently across every duplicate cluster. That consistency helps Google and AI crawlers resolve a single authoritative source per topic, which keeps your citation continuity intact through the migration instead of splitting authority across near-duplicate pages.
Execute launch day and validate immediately
Launch-day execution requires three separate controls: a tested backup, monitored deployment with rollback thresholds, and immediate technical validation. Bundling these into one vague "go live" step is how teams miss failures they could have caught in minutes.
The three checklist blocks below assign a named owner, a checkable action, and a rollback trigger to each control, including the 15-minute downtime and 10% redirect-failure thresholds that decide whether you push forward or roll back.
Back up the site before you deploy
A full site backup, including the database and DNS configuration, needs a tested restore before any redirect or code changes go live. Back up the site files, images, database, DNS records, server settings, existing redirects, and metadata as one complete package. Don’t leave them scattered across different tools.
Restore that backup in a staging environment separate from production. Confirm every page loads, the database connects, and DNS settings match what you expect.
Only mark the backup complete once the restore test succeeds. An untested backup gives you false confidence right before launch, so add a checkbox that confirms the restore worked.
Push redirects live and monitor in real time
Redirects go live at the exact moment DNS cuts over to the new site, not before and not after.
As soon as the switch flips, watch:
- Propagation
- Server errors
- Redirect failures
- Live traffic
- Conversion tracking
Roll back if any of these thresholds hit: downtime exceeds 15 minutes, redirect failures affect more than 10% of URLs, or critical functionality breaks.
Teams on Cloudflare need to plan around its redirect-file limits of 2,000 static and 100 dynamic redirects, and account for the duplicate-content risk that comes with proxying instead of redirecting.
Validate technical elements and AI crawler continuity
Technical validation on launch day covers five items, each checked separately:
- Robots.txt rules
- XML sitemap submission
- Canonical tags
- Schema markup
- Analytics tracking
Skipping one because "it looked fine" is how migrations lose rankings quietly over the following weeks.
Add a sixth check that most migration plans miss: Confirm your robots.txt still allows AI crawler user agents after deployment. A blocked crawler cuts off citation opportunities even when your human-facing SEO looks healthy.
Test that structured data renders correctly on the new site so search and answer engines see consistent source signals. That consistency is what protects the citations you've already earned in AI-generated answers.
Monitor rankings on a fixed cadence
Post-launch monitoring needs three separate checklists: index and ranking signals, fixed day 1, 3, 7, 14, and 30 checkpoints, and proactive error and link remediation. A vague plan to "watch things closely" won't catch a rankings drop before it costs pipeline.
The three blocks below assign owners, key performance indicators, schedules, and escalation thresholds for each checkpoint.
Track indexing and rankings after launch
Comparing indexed-page counts against the submitted sitemap count, paired with baseline keyword positions, gives you the earliest warning that a migration has disrupted discovery or rankings. Pull both numbers from GSC's Pages report and your submitted sitemap on a fixed schedule.
Alongside that, track your priority keywords against the exact positions you recorded before launch. Google's own site move guidance confirms this comparison is standard practice for catching migration fallout early.
Escalate any crawl exclusions, index-count gaps, or ranking drops immediately, before they show up in pipeline reporting. If duplicate or thin pages are behind the gap, content consolidation can help close it.
Follow the day 1 to 30 cadence
Set checkpoints on days 1, 3, 7, 14, and 30, and assign each one an owner, a KPI threshold, and an escalation action. A checkpoint with no owner gets missed.
Developers own daily technical checks for server errors, redirect failures, and crawl activity. The marketing lead owns weekly ranking reviews and flags any keyword that drops out of its top-10 baseline position.
Bing recommends monitoring server logs daily for three months post-migration and keeping redirects live for one to two years. Build both into your tracker now. Don’t wait until after something breaks.
Fix common post-migration errors and update links
404s, redirect loops, and soft 404s are the three recurring error types to isolate, and none of them get fixed by someone manually updating high-value backlinks and directory listings after the fact. Give each error type its own row in your tracker instead of lumping them into one catch-all task.
Run Ahrefs or Semrush to pull the URLs still throwing errors, then assign an owner to each row:
- 404s: Pages with no redirect mapped at all.
- Redirect loops: Chains that bounce back to themselves.
- Soft 404s: Pages that return a 200 status but show no real content.
Once errors are cleared, work through outreach. High-value backlinks, directory listings, paid campaigns, social profiles, email signatures, and marketing templates all need the new URL by hand.
For deeper diagnosis on any of these failure types, see our guide to common website migration challenges.
Migrate safely, then grow with strategy
A clean migration only holds the line; it doesn't move it forward. Redirect mapping, log file checks, and staging validation exist to protect the rankings and revenue you already earned, so don’t expect them to generate new demand.
That's the gap most teams hit right after go-live. Traffic stabilizes, the dashboards look fine, and then nothing new happens. Growth after a migration comes from a prioritized roadmap, the kind built on ideal customer profile research, topic-cluster sequencing, and a 90-day review cadence tied to pipeline. Re-running the same checklist every quarter won’t move the needle.
With $50M+ in organic ARR generated and 300+ strategies delivered across companies that needed both execution discipline during a migration and a growth plan after it, Ten Speed has guided that transition for B2B teams enough times to know the pattern.
If your migration is stable and you're ready to build what comes next, map your next growth roadmap with our team.
Frequently asked questions
How long does a full website migration typically take from planning to ranking recovery?
Most B2B migrations need two to six weeks of pre-migration planning, one focused launch day, and then an extended recovery window of up to three months since search engines typically need that long to fully re-crawl and re-rank a migrated site. Larger sites with thousands of URLs or complex redirect maps should expect recovery timelines toward the longer end of that range.
Do we need a staging environment to test a migration before it goes live?
A staging environment is one of the highest-leverage steps in a migration since it lets your team crawl the new site structure, verify redirects, and catch broken templates before real traffic and rankings are at risk. Skipping this step means the first real test of your redirect map happens on the live domain, which is exactly when mistakes get expensive. Testing on staging also gives developers and marketers a shared checkpoint to sign off before DNS cutover, rather than discovering problems mid-launch.
Is it better to migrate a site all at once or roll it out in phases?
A phased migration, moving one site section or template type at a time, generally reduces risk for large or complex sites because it limits how many redirects and templates need validation at once. A single-cutover migration works well for smaller sites where the full redirect map and technical validation are manageable in one pass. The right choice depends on site size and redirect count, not a fixed rule, so teams should scope their URL inventory before deciding.
What should we do if rankings drop after the 30-day monitoring window ends?
A ranking drop after day 30 doesn't mean monitoring should stop; it means the issue likely sits deeper in the redirect map or indexing pipeline rather than in early launch-day errors. Migration risk typically extends well past the first month since search engines can take several months to fully re-crawl a site and redirects are generally expected to stay live for a year or more. Re-running a full crawl comparison against your original redirect map is the fastest way to isolate what changed.
Does moving to a faster or more modern platform guarantee better search rankings after migration?
A faster, more modern platform can remove technical barriers to ranking, but it doesn't automatically improve where a page ranks if the content, internal linking, and topical authority stay the same. Site speed and architecture are ranking factors, not the whole equation, and migrations that focus only on platform upgrades while treating redirects and content signals as an afterthought often see flat or declining performance. Protecting rankings through the migration and then investing in a deliberate content and SEO strategy afterward is what actually compounds growth over time.
