SEO Migration Checklist: What to Do Before, During, and After a Site Move

Overview

This guide gives you a working SEO migration checklist you can reuse for almost any site move. It is written for publishers, marketers, SEO leads, and site owners who need a clear process rather than abstract advice.

For this article, a migration means any change that can affect search visibility, crawling, indexing, or URL equity. That includes:

• Moving to a new domain
• Switching CMS platforms
• Redesigning templates or navigation
• Changing URL structures
• Consolidating subfolders, subdomains, or sections
• Updating internal linking and taxonomy at scale
• Migrating from staging to production with major content or template changes

The main principle is simple: preserve what already works before you improve what does not. Most migration losses come from broken redirects, missing pages, weak QA, accidental noindex directives, or incomplete tracking. A careful website migration SEO process lowers those risks.

Before you start, define the scope in one sentence. For example: “We are moving from one CMS to another while keeping the same domain, changing blog URLs, and consolidating category pages.” That sentence helps your team decide what must be mapped, tested, and monitored.

It also helps to separate migrations into three phases:

1. Before launch: benchmark, crawl, map, prepare, and test.
2. During launch: validate redirects, indexability, canonicals, analytics, and server behavior.
3. After launch: monitor traffic, crawling, indexing, ranking, and page-level recovery.

If you need a framework for measuring impact after the move, pair this checklist with SEO KPIs by Site Type: What Blogs, SaaS Sites, and Publishers Should Track and a practical SEO Reporting Dashboard so the team can spot changes quickly.

Checklist by scenario

Use the core checklist first, then add the scenario-specific items that match your project. That approach keeps your technical SEO migration work focused and easier to QA.

Core checklist for any migration

These steps apply to nearly every move, whether you are changing a domain or simply redesigning templates.

Before launch

• Export your current URL inventory. Include all indexable pages, major media assets if relevant, XML sitemap URLs, and top-performing landing pages from analytics and Search Console.
• Benchmark current performance. Save organic sessions, clicks, impressions, rankings for priority queries, conversions, and top linked pages. This becomes your baseline.
• Crawl the current site. Record status codes, title tags, canonicals, noindex rules, internal links, redirect chains, orphan pages, and indexable URL counts.
• Identify your highest-risk pages. Usually these are pages with backlinks, pages driving conversions, pages ranking for valuable queries, and evergreen content with stable traffic.
• Build a redirect map. Create a one-to-one mapping from every old URL to the most relevant new URL. Avoid redirecting many unrelated pages to the homepage.
• Preserve metadata where appropriate. Keep successful title tags, meta descriptions, H1s, structured content sections, and internal anchor patterns unless there is a clear reason to change them.
• Review internal linking logic. Migration is a good time to fix weak navigation and support an intentional topical map, but avoid large-scale changes without documentation.
• Prepare technical rules. Confirm canonicals, robots directives, XML sitemaps, hreflang if used, pagination behavior if relevant, and faceted navigation rules.
• Audit analytics and reporting. Make sure GA4 events, conversion points, Search Console properties, and dashboards are ready to compare pre- and post-launch performance.
• Test on staging. Crawl the staging environment and verify templates, links, canonicals, structured data, headings, and status codes. Keep staging blocked from indexation.

Launch day

• Deploy redirect rules. Test a representative sample of high-value URLs and edge cases.
• Check indexability. Confirm pages intended for search are not blocked by noindex tags, robots rules, authentication walls, or accidental canonical targets.
• Validate canonicals. They should point to the intended live URLs, not staging, old paths, or generic templates.
• Test server responses. Watch for 404s, 500s, soft 404 behavior, redirect loops, and slow responses on key templates.
• Generate and submit XML sitemaps. Include only canonical, indexable URLs.
• Verify analytics and Search Console. Make sure tracking works on live pages and property ownership is configured correctly.
• Spot-check internal links. Navigation, breadcrumbs, related content widgets, author pages, and footer links often break in redesigns.

After launch

• Monitor coverage and crawl activity. Review indexing trends, excluded URLs, and crawl anomalies.
• Track top pages daily at first. Focus on the pages and directories that mattered before launch.
• Fix redirect gaps quickly. Add rules for high-priority 404s and broken backlinks as they appear.
• Update internal links to final destinations. Redirects are useful, but internal links should point directly to live canonical URLs.
• Refresh external references where possible. For a domain move especially, update important profiles, directory listings, and owned backlinks.
• Compare baseline vs current performance. Use organic sessions, clicks, impressions, key landing pages, and conversions rather than a single top-line number.

Scenario 1: Site redesign on the same domain

This is often treated as “just a design update,” but redesigns can alter templates, headings, crawl paths, page speed, and internal linking enough to hurt rankings.

• Check whether navigation labels, menus, and breadcrumb structures changed.
• Compare old and new internal link depth for important pages.
• Preserve content blocks that currently help rankings, even if the layout changes.
• Review image handling, lazy loading, and JavaScript-dependent elements that might hide content from crawlers.
• Test mobile layouts carefully, especially if key content moved lower on the page or into tabs.

Scenario 2: CMS migration

A CMS switch is one of the most common forms of website migration SEO work. It often introduces silent changes to URL rules, canonicals, taxonomies, and templates.

• Verify permalink behavior and trailing slash consistency.
• Audit category, tag, author, and archive pages for duplication.
• Check default noindex behavior on filtered or low-value templates.
• Confirm editable fields for titles, meta descriptions, canonicals, schema, and image alt text.
• Make sure the new CMS does not auto-generate thin pages you do not want indexed.
• Test how the CMS handles pagination, search pages, and media attachment URLs.

Scenario 3: Domain migration

A full domain change needs the strictest process because it affects every URL, every backlink signal, and every branded search path. Your domain migration checklist should include the following:

• Map every old URL to its new equivalent where possible.
• Keep site architecture changes minimal during the move if you can. Combining a redesign, new CMS, and domain change raises complexity fast.
• Verify redirects at the page level, not just the domain level.
• Add and verify the new property in Search Console.
• Update XML sitemaps, robots references, canonicals, and structured data references to the new domain.
• Update important external links under your control, including social profiles, local listings, partner pages, and documentation.
• Retain the old domain and redirect environment long enough to capture delayed requests and backlinks.

Scenario 4: URL structure change or content consolidation

This often happens when teams clean up blog categories, merge overlapping pages, or improve a weak information architecture.

• Review pages with overlapping intent before merging. Do not combine pages that target different search needs.
• Keep the strongest URL where possible rather than creating unnecessary new paths.
• Transfer useful content elements from retired pages into the surviving destination.
• Update contextual internal links, not just navigation links.
• Review keyword intent and cannibalization issues. If you are unsure, revisit your content mapping process with SEO Content Brief Checklist.

Scenario 5: Publisher migration with monetization concerns

Publishers often face extra migration risk because ad placements, affiliate modules, author pages, archives, and internal recirculation systems are tightly connected to organic traffic.

• Protect high-earning evergreen articles first.
• Test ad scripts and performance impact after launch.
• Review article schema, author markup, and date handling.
• Check related-post modules and editorial recirculation links.
• Make sure content pagination and infinite scroll do not create crawl or UX issues.

What to double-check

These are the items that most often deserve a second pass. If your migration timeline is tight, prioritize these checks over cosmetic refinements.

1. Redirect quality

Redirects should be relevant, direct, and complete. Avoid blanket rules that send every retired page to the homepage or a category page with mismatched intent. That preserves less value and creates a poor user path. Also look for chains such as old URL to interim URL to final URL. Update those to a single hop where possible.

2. Canonicals and indexation rules

Many migrations fail because templates inherit the wrong canonical or noindex settings. Double-check page templates for posts, categories, product-like pages, author profiles, and archives. A few wrong template settings can scale across thousands of URLs.

3. Internal linking strategy

Even with perfect redirects, a weak post-launch internal linking structure can slow recovery. Confirm that your key pages still receive links from the main navigation, category pages, and relevant in-content references. If your migration changes content clusters, use this chance to strengthen your internal linking strategy intentionally instead of leaving it to old widgets or plugin defaults.

4. XML sitemaps

Your sitemap should reflect the new canonical, indexable URLs only. Remove redirected, noindexed, duplicate, or parameter-based URLs. A clean sitemap helps search engines discover the right pages faster after launch.

5. Structured data and template content

Schema markup often breaks quietly in redesigns. Test the templates that matter most, including articles, breadcrumbs, organization details, and author pages where applicable. Also verify that headings, bylines, dates, and supporting content blocks still render correctly.

6. Search Console and GA4 setup

Post-launch confusion often comes from missing comparisons rather than actual SEO damage. Make sure your google search console seo workflow and ga4 for seo views are ready before launch. Annotate the migration date, create segmented reporting for key directories, and keep your baseline exports organized. For ongoing review, a simple dashboard is often better than a complex one no one checks.

If your reporting setup is weak, build one before the move using the ideas in SEO Reporting Dashboard: KPIs, Dimensions, and Client-Friendly Views.

7. Backlink preservation

This article is mainly about migration operations, but link equity matters throughout the process. Export your most linked pages before launch and test them after launch first. If a domain or URL changes, consider outreach to update your highest-value backlinks where practical. Thoughtful follow-up can protect referral traffic and preserve link signals. If you need a process, review Email Outreach for Link Building and Link Prospecting Methods.

Common mistakes

The best migration plans usually fail in ordinary ways, not unusual ones. Here are the mistakes that appear most often and are worth preventing upfront.

• Changing too many things at once. A redesign, CMS switch, domain move, and content rewrite done together can make diagnosis much harder when performance drops.
• No baseline benchmark. Without pre-launch exports, teams end up arguing about whether performance really changed.
• Ignoring non-top pages. Long-tail content, archives, image URLs, and older evergreen articles often hold more value than expected.
• Using incomplete redirect maps. Redirecting only “important” pages and leaving the rest to 404 can create unnecessary losses.
• Launching with staging directives. Accidental noindex tags, blocked robots rules, or staging canonicals still happen.
• Overwriting successful content. A design refresh should not strip out helpful copy, headings, FAQs, or body text that supports rankings.
• Forgetting internal links. Redirects are not a substitute for updated navigation and contextual linking.
• Submitting messy sitemaps. Sitemaps with redirects, duplicates, or blocked URLs slow down cleanup.
• Not monitoring log-like signals. Even without full server log analysis, you should still watch crawl errors, spikes in exclusions, and sudden page-level drops.
• Declaring success or failure too early. Some fluctuation is normal. What matters is whether key sections are being crawled, indexed, and stabilized over time.

A useful rule during any site redesign SEO project: if a page currently earns organic traffic, backlinks, or conversions, document exactly what made it successful before anyone edits or relocates it.

When to revisit

This checklist works best as a living document rather than a one-time article. Revisit it whenever the underlying inputs change, especially before planning cycles and before any release that affects URLs, templates, navigation, or measurement.

Use this practical revisit schedule:

• 4 to 8 weeks before launch: finalize scope, export benchmarks, crawl the current site, and complete redirect mapping.
• 1 to 2 weeks before launch: crawl staging, QA templates, validate analytics, and test sample redirects and canonical logic.
• Launch day: assign owners for redirects, indexability, tracking, and urgent fixes.
• First 72 hours after launch: review top landing pages, crawl issues, coverage changes, 404s, and tracking integrity.
• First 2 to 4 weeks: compare baseline metrics by page group and directory, not just sitewide totals.
• Quarterly after major structural changes: audit internal links, sitemap quality, and content consolidation results.

To make this article actionable, keep a migration worksheet with these tabs:

1. Current URL inventory
2. Top pages by traffic, links, and conversions
3. Redirect map
4. Template QA checks
5. Launch-day validation list
6. Post-launch issue log
7. Weekly recovery report

If your process needs tool support, a lightweight stack is enough: a crawler, Search Console, GA4, a spreadsheet, and a reporting view your team will actually open. You can also review Free SEO Tools Worth Using and Top SEO Tools for Keyword Research, Links, Audits, and Reporting to fill any workflow gaps.

Final action step: before your next migration meeting, assign one owner to each of these five areas: redirects, indexation, internal links, analytics, and post-launch monitoring. Most migration problems are not caused by a lack of SEO knowledge. They happen because ownership is vague. A clean checklist, a clear baseline, and accountable reviews will do more for organic traffic growth than last-minute fixes after rankings fall.