A website redesign should make life easier for customers. Pages should load smoothly, navigation should make sense, and the site should reflect the business you are today. But there is one risk teams sometimes discover too late: a better-looking website can lose organic traffic if search engines cannot understand what changed.
The problem is rarely the new design itself. Traffic can fall because valuable URLs disappear, redirects are missed, internal links point to old locations, or important pages accidentally become blocked from indexing. These issues are preventable when SEO is included in the migration plan rather than added after launch.
This practical SEO migration checklist explains what to do before, during and after a redesign so your team can launch with fewer surprises.
What Is an SEO Migration?
An SEO migration is a significant website change that can affect how search engines crawl, index and rank your pages. It may involve changing the domain, moving from one CMS to another, updating URL structures, switching to HTTPS, redesigning templates or combining several websites.
Not every visual refresh needs a full migration process. However, if the project changes URLs, page content, navigation, rendering, site architecture or hosting, SEO checks should be part of the release plan. The more moving parts involved, the more important it is to record the existing site and test the new one carefully.
1. Record the Website’s Current SEO Performance
Before changing anything, build a baseline. Without it, you may struggle to tell whether a post-launch change is normal fluctuation or a genuine technical problem.
Capture at least the following:
- Organic clicks, impressions and indexed-page trends from Google Search Console.
- Organic landing-page sessions and conversions from your analytics platform.
- The URLs that attract the most traffic, leads, sales or assisted conversions.
- Current ranking keywords for important commercial and informational pages.
- Backlinks pointing to key pages, especially URLs that have earned strong links.
- Existing indexation, canonical, sitemap, robots.txt and structured-data settings.
Do not focus only on the homepage or the pages with the highest traffic. A product page, service page or helpful article may generate fewer visits but contribute a meaningful share of enquiries. Flag business-critical URLs so they receive extra attention during testing.
If your team needs a prioritised view of technical and content risks, start with an SEO audit before the migration plan is finalised.
2. Crawl and Save the Existing Website
Run a crawl of the live website before the old version is replaced. Export URLs, status codes, titles, meta descriptions, H1 headings, canonical tags, indexability, internal links and other useful page-level details. Keep the export somewhere the development and SEO teams can access.
This crawl becomes your reference point. It helps you compare the old site with the staging site and identify pages that have disappeared, changed status or lost important signals.
Include pages that may not be easy to find through navigation, such as older blog posts, campaign landing pages and pages that receive backlinks. Use XML sitemaps, analytics landing-page reports, Search Console exports and backlink data to supplement the crawl. No single source is guaranteed to reveal every URL that matters.
3. Map Old URLs to the Most Relevant New URLs
URL mapping is one of the most important parts of a migration. Every valuable old URL that is changing should have a clear destination where a genuinely equivalent page exists.
For example, if an old service page is moving from /seo-services/ to /services/seo/, redirect the old URL to the new service page. Do not send every old page to the homepage simply because it is convenient. The destination should match the original page’s purpose and content as closely as possible.
Build a spreadsheet with columns for the old URL, new URL, current status, redirect type, page importance and validation result. Review the mapping for:
- High-traffic landing pages and pages that generate leads or sales.
- URLs with valuable external backlinks.
- Pages with a close replacement on the new site.
- Old URLs that should remain live because they still serve a purpose.
- Pages that can be retired because they have no useful replacement.
Use permanent server-side redirects, usually 301 redirects, when a page has permanently moved. Avoid redirect chains where one URL redirects to another that redirects again. If a page has no suitable replacement, decide deliberately whether it should remain available, be consolidated into a relevant page or return an appropriate not-found response.
4. Test the Staging Site Before Launch
A staging environment gives the team a chance to find issues before customers and search engines encounter them. It should be checked as a real website, not just reviewed visually.
- Confirm important pages return the expected HTTP status codes.
- Check that page titles, meta descriptions, headings and main copy are present.
- Review canonical tags and ensure they point to the intended URLs.
- Check robots directives and make sure production pages will not accidentally carry staging noindex settings.
- Test navigation, breadcrumbs, pagination, filters and internal links.
- Validate structured data and check that it reflects the visible page content.
- Review mobile layouts, page speed and important user journeys.
- Check XML sitemap generation and confirm only canonical, indexable URLs are included.
Keep staging private or protected as appropriate, but do not rely on a robots.txt block alone as a privacy measure. Before launch, create a clear checklist for removing any staging-only restrictions from the production environment.
5. Protect Internal Links and Site Structure
Redirects help users and crawlers reach moved pages, but internal links should still point directly to the new destination. Leaving thousands of internal links pointing through redirects adds unnecessary steps and can make future maintenance harder.
Review menus, footer links, breadcrumbs, related-content modules, blog links, category pages and calls to action. Check that important pages remain reachable through logical navigation and are not left as orphan pages with no useful internal links.
A structured approach to technical fixes and internal-link checks can be included in your broader SEO services plan.
6. Keep Content and Search Intent Consistent
A redesign often comes with copy changes. Some edits improve clarity, but removing useful sections or changing a page’s purpose can affect its relevance for existing searches.
Before launch, compare important pages side by side. Check whether the new version still answers the questions visitors came to solve, includes essential product or service details, and preserves useful supporting information. If several old pages are being merged, make sure the new page covers the distinct needs that made each page valuable.
Do not assume that longer copy is automatically better. The goal is to preserve and improve usefulness, not to keep every sentence simply because it existed on the old site.
7. Prepare the Launch-Day SEO Checks
Assign one person to coordinate SEO validation during launch and make sure the developer, content owner and marketing lead know who is responsible for each check. A short, shared checklist is more useful than a long document no one owns.
- Confirm the correct domain, HTTPS setup and preferred hostname.
- Test key redirects and verify that priority pages return the intended status codes.
- Check that production pages are crawlable and indexable where intended.
- Verify canonical tags, robots.txt and XML sitemaps.
- Test important forms, checkout flows, phone links and conversion tracking.
- Check a sample of high-priority URLs on mobile and desktop.
- Confirm analytics and Search Console verification still work.
- Keep the previous site and migration records available for troubleshooting.
If the website is large, automate checks where practical. Monitoring workflows can help flag unexpected status codes, indexing changes or technical regressions. Automation should support a tested migration plan, not replace human review.
For teams managing frequent releases or large websites, SEO automation can help make repeatable checks and monitoring part of the workflow.
8. Monitor the Site After Launch
A successful launch is not the end of the migration. Search engines need time to recrawl changed URLs, process redirects and update their understanding of the site. Review the data frequently during the first days and weeks, then continue monitoring until performance stabilises.
Prioritise these checks:
- Crawl errors, server errors and unexpected redirect behaviour.
- Indexing reports and the status of important landing pages in Search Console.
- Organic clicks and impressions compared with the pre-launch baseline.
- Landing-page traffic, leads, sales and other meaningful conversions.
- Pages returning 404 errors that still receive traffic or backlinks.
- Unexpected changes to canonical tags, sitemap URLs or robots directives.
Avoid making multiple major changes in response to a single day of fluctuating traffic. Look for patterns, validate the technical evidence and separate migration problems from seasonality, tracking changes or wider search demand shifts. If a serious issue appears, investigate promptly rather than waiting for a monthly report.
Common Website Migration Mistakes to Avoid
- Launching without a complete list of important existing URLs.
- Redirecting unrelated pages to the homepage.
- Leaving staging noindex directives or crawl restrictions on production.
- Changing URLs, content, navigation and templates without documenting the changes.
- Forgetting backlinks, older blog posts or landing pages outside the main navigation.
- Submitting a sitemap containing redirected, non-canonical or non-indexable URLs.
- Removing analytics tags or conversion tracking during the redesign.
- Treating an initial traffic fluctuation as proof that the migration has failed—or ignoring a sustained decline without investigation.
How Long Should SEO Migration Monitoring Continue?
There is no universal end date. A small website with limited URL changes may be easier to validate than a large ecommerce site with thousands of products, filters and international versions. Monitor closely immediately after launch, review trends over the following weeks and continue until the important URLs, indexing patterns and business metrics are behaving as expected.
Keep the URL map, crawl exports, launch checklist and issue log after the project is complete. They provide a useful reference if traffic changes later or another redesign is planned.
Conclusion
A website redesign should improve the experience without discarding the search visibility the business has already earned. The safest approach is to document the old site, map URLs carefully, test staging, preserve relevant content, validate the launch and monitor the results.
SEO does not need to slow a redesign down. Involving the SEO team early usually makes decisions clearer and reduces the number of avoidable fixes after launch. If a redesign or platform change is coming up, use this checklist as a shared working document and prioritise the pages that matter most to customers and revenue.
Need help identifying migration risks before launch? Explore ASG Marketer’s SEO audit services or contact the team through the Contact Us page.
Frequently Asked Questions
What is an SEO migration checklist?
It is a step-by-step set of checks used before, during and after a website change to protect crawlability, indexation, URLs, content, analytics and organic performance.
Will a website redesign affect SEO rankings?
It can. Rankings may change if URLs, content, internal links, page speed, rendering or indexability change. Planning and testing reduce avoidable risks, but no checklist can guarantee that rankings will remain identical.
Do all old URLs need a 301 redirect?
No. Redirect URLs that have permanently moved to a relevant replacement. Keep pages that should remain live, and do not redirect unrelated or permanently removed pages to an irrelevant destination just to avoid 404s.
When should SEO be involved in a website redesign?
As early as possible, ideally during planning and before the URL structure, content templates and navigation are finalised. Early involvement is usually easier than repairing migration issues after launch.
How do I know if a website migration has caused traffic loss?
Compare organic clicks, impressions, landing-page sessions and conversions with the pre-launch baseline. Check Search Console indexing and crawl errors, validate priority URLs and investigate whether the decline aligns with technical changes.




