A website migration SEO checklist is a step-by-step process for moving a site, changing domains, redesigning templates, switching CMS platforms, or restructuring URLs without losing rankings, traffic, and conversions. Use it before, during, and after any migration that changes URLs, content, internal links, templates, hosting, or technical setup. The goal is simple: preserve what already works in search while giving search engines clear signals about what changed.
When to use a website migration SEO checklist
Use this checklist for any change that can affect crawling, indexing, or relevance, including:
- Domain changes
- HTTP to HTTPS moves
- CMS or platform migrations
- Website redesigns
- URL structure changes
- Subdomain to subfolder moves
- International site consolidation
If your migration changes page locations, page content, internal linking, metadata, canonicals, structured data, or server behavior, SEO needs to be involved from the start, not after launch.
Why this checklist matters
- Protects existing rankings and organic traffic
- Reduces indexing errors after launch
- Preserves link equity with proper redirects
- Helps teams catch technical issues early
Pre-migration SEO checklist
1. Crawl and benchmark the current site
Before anything changes, capture a full picture of the existing website. Crawl the site and export all indexable URLs, status codes, title tags, meta descriptions, canonicals, heading structure, internal links, image alt text, and structured data. Pull performance data from analytics and search performance tools so you know which pages drive traffic, leads, and revenue.
At minimum, benchmark:
- Top organic landing pages
- Pages with backlinks
- Pages ranking for valuable keywords
- Indexed page count
- Core templates such as product, category, blog, and location pages
2. Identify high-value pages to protect
Not every URL has equal value. Build a priority list of pages that must retain visibility after launch. This usually includes homepage variations, key service pages, top blog posts, product categories, lead-generation pages, and any URLs with strong backlinks or branded search visibility.
Flag these pages for extra QA so they receive the most attention during redirect mapping, content migration, and post-launch monitoring.
3. Create a redirect mapping file
If URLs are changing, map every important old URL to its best new equivalent. Use one-to-one 301 redirects wherever possible. Avoid redirecting many unrelated pages to the homepage, because that weakens relevance and often leads to ranking loss.
A good redirect map should include:
- Old URL
- New URL
- Redirect type
- Page type
- Priority level
- Notes for exceptions
Remove redirect chains and loops before launch. Each old URL should resolve directly to the final destination.
4. Preserve on-page SEO elements
During redesigns and CMS migrations, teams often overwrite title tags, headings, body copy, internal links, and metadata. Compare old and new templates to make sure important SEO elements are not lost.
Check that the new site keeps or improves:
- Title tags and meta descriptions
- Primary headings
- Helpful body content
- Internal links to key pages
- Image alt text
- Structured data where relevant
5. Review technical SEO settings on staging
Staging environments should be blocked from indexing, but still fully testable. Confirm that noindex tags, robots rules, password protection, or IP restrictions are used appropriately on staging. Then document exactly what must be removed or changed before launch.
Also test:
- Canonical tags
- XML sitemaps
- Robots directives
- Pagination behavior
- Mobile usability
- Page speed and Core Web Vitals basics
Launch-day SEO checklist
6. Deploy redirects and validate them immediately
As soon as the new site goes live, test your redirect map. Spot-check high-value URLs first, then validate at scale. Look for 404 errors, redirect chains, soft 404s, and pages that incorrectly resolve to the homepage.
7. Update internal links and navigation
Do not rely on redirects for internal navigation. Update menus, breadcrumbs, footer links, contextual links, and XML sitemaps so they point directly to the new URLs. This improves crawl efficiency and helps search engines understand the new structure faster.
8. Check indexability and canonicals
One of the most common migration mistakes is launching with noindex tags still active or canonicals pointing to old URLs. Review a sample of key templates and confirm that:
- Important pages are indexable
- Canonical tags point to the correct live URL
- Robots rules are not blocking essential sections
- Structured data matches the new page content
9. Submit updated sitemaps
Generate fresh XML sitemaps with the final live URLs only. Submit them in your search engine webmaster tools and monitor whether pages are being discovered and indexed correctly. If the migration is large, segment sitemaps by page type to make troubleshooting easier.
Post-migration SEO checklist
10. Monitor crawl errors, rankings, and traffic daily
The first few weeks matter most. Track 404s, server errors, excluded pages, crawl anomalies, and index coverage changes. Compare post-launch performance to your benchmark, especially for priority pages and core keyword groups.
Expect some short-term fluctuation, but investigate quickly if you see sustained drops tied to specific templates, folders, or device types.
11. Reclaim lost signals
If important pages lost rankings, check whether the issue is caused by weaker content, missing internal links, incorrect canonicals, broken redirects, or slower page performance. For pages with strong backlinks, make sure the old URLs redirect properly and consider updating key external links where possible.
12. Keep redirects in place long enough
Do not remove redirects too early. For most migrations, keep critical 301 redirects active for at least 12 months, and often longer for pages with backlinks, bookmarks, or recurring referral traffic.
Short workflow example
A company moves from an old CMS to a new platform and changes blog URLs from /post-name to /blog/post-name. Before launch, the SEO team exports all current blog URLs, identifies the top 100 traffic-driving posts, maps each old URL to its new version, checks that titles and headings are preserved, and tests canonicals on staging. On launch day, they validate redirects, update internal links in category pages and navigation, submit a new sitemap, and monitor indexing and traffic daily for 30 days.
Common website migration SEO mistakes
- Launching without a tested redirect map
- Changing content and URLs at the same time without benchmarking
- Leaving noindex tags on live pages
- Using canonicals that point to old or wrong URLs
- Forgetting to update internal links and sitemaps
- Removing redirects too soon
FAQ
What is the biggest SEO risk during a website migration?
The biggest risk is losing relevance and link equity through broken redirects, missing content, or incorrect indexation settings. Most traffic losses come from avoidable technical mistakes.
Should every old URL redirect to a new page?
Every valuable old URL should redirect to the closest relevant new page. If there is no equivalent, choose the best alternative rather than sending everything to the homepage.
How long does SEO recovery take after a migration?
Small migrations may stabilize in a few weeks. Larger migrations can take several months, especially if many URLs, templates, or content sections changed at once.
Who should own a migration checklist?
SEO should help define requirements, but successful migrations usually involve SEO, development, design, content, analytics, and project management working from one shared checklist.
