A website migration is ready when its risks are measurable, assigned, and tested, not simply when the new design looks finished. Whether you are changing platforms, redesigning a site, changing domains, or completing a major upgrade, compare performance before and after launch.
This website migration SEO checklist covers seven areas that can affect visibility, usability, tracking, and ongoing performance. It also shows when each check belongs in the process and who should own it.
When to complete each migration check
| Stage | Priority checks | Decision |
|---|---|---|
| Before migration | Baseline data, content inventory, URL mapping, redirects, access, backups, and staging. | Proceed when scope, ownership, and destinations are approved. |
| Launch day | Redirects, crawl directives, canonicals, forms, tracking, mobile behaviour, security, and key-page performance. | Pause if a critical journey, tracking system, or search signal is broken. |
| After launch | Crawl errors, indexing, organic landing pages, conversions, speed, availability, and feedback. | Document anomalies before changing several variables. |
1. Establish baseline performance and SEO measurements
A baseline gives you evidence for distinguishing migration problems from normal variation. It does not guarantee that rankings, traffic, conversions, or speed will remain unchanged.
Measure representative pages, including the homepage, key service or product pages, top organic landing pages, contact or booking pages, blog content, and important account or checkout journeys.
- Organic sessions, conversions, leads, purchases, and important landing pages.
- Indexed pages, prominent queries, crawl errors, and internal links.
- Mobile and desktop loading and user-experience measurements.
- Form submissions, calls, downloads, transactions, and other tracked actions.
- Current URLs, titles, canonicals, indexability, and structured data.
Record the date, tools, page samples, devices, and test conditions. Use a repeatable approach so the comparison remains meaningful.
2. Inventory content and map every important URL
For each current URL, record its purpose, page type, traffic or conversion value, title, headings, canonical, media, internal links, and forms. Decide whether the content should be kept, improved, consolidated, or retired.
Give every retained or consolidated page one clear destination. Do not send unrelated URLs to the homepage merely to avoid documenting a decision. Confirm who supplies and approves content, metadata, media, downloads, and forms.
The guidance on content migration, redirects, and performance testing can help clarify operational responsibilities.
- Crawl the current URL set, including important non-navigation pages.
- Mark URLs as keep, improve, merge, redirect, or retire.
- Match each retained URL to its exact new destination.
- Review navigation, images, files, forms, and embedded services.
- Obtain approval for high-value pages before development is complete.
3. Protect redirects, canonicals, sitemaps, and crawl access
A redirect map should cover URL changes caused by a new platform, folder structure, domain, catalogue, or content consolidation. Test that old URLs reach relevant final destinations directly, without chains or loops.
Review canonical URLs, indexability directives, robots.txt, XML sitemaps, internal links, and regional signals where applicable. Keep staging out of search results while it is being tested, then confirm that production is crawlable after launch.
- Test representative high-value old URLs and known variations.
- Confirm each redirect reaches the intended final URL.
- Check destination status, canonical, and indexability.
- Review robots directives, sitemap URLs, and internal links.
- Submit the production sitemap and inspect priority pages in Search Console.
Google's official documentation on site moves and migrations with URL changes belongs in the technical review when URLs or domains change.
4. Test speed, responsiveness, security, and functionality
A migration can preserve URLs while damaging the experience through heavier templates, failed scripts, or broken mobile layouts. Test representative templates and important user journeys across browsers and screen sizes.
- Check navigation, buttons, media, downloads, and embedded content.
- Submit important forms and verify notifications, integrations, and confirmations.
- Check mobile responsiveness, readable text, touch targets, and layout shifts.
- Measure representative pages rather than only the homepage.
- Review HTTPS, access controls, updates, backups, error handling, and staging exposure.
- Test checkout, booking, account, search, or portal flows where relevant.
Lighthouse can support diagnosis, but its score is not a complete release decision. After launch, include website speed optimization and SEO validation in final QA, followed by performance monitoring.
5. Verify analytics, Search Console, and SEO signals
Do not assume tracking survives a platform or template change. Verify the complete path from page load to recorded event.
- Confirm analytics tags load on intended pages and do not fire twice.
- Test forms, calls, purchases, downloads, and sign-ups.
- Confirm Search Console ownership, the correct property, sitemap access, and priority URL inspection.
- Review titles, descriptions, headings, canonicals, indexability, links, and structured data.
- Check campaign parameters, consent settings, attribution, and referral exclusions.
Separate technical verification from performance interpretation. A traffic drop may reflect a tracking failure rather than a search visibility change, so record what changed, when, and which system confirms it.
6. Assign migration responsibilities before launch
Many migration failures are ownership failures. Every task needs one responsible owner, a reviewer, and an escalation path.
| Owner | Typical responsibilities |
|---|---|
| Business owner | Approve scope, priorities, access, timing, key journeys, and the go-live decision. |
| Developer | Manage build, hosting, deployment, redirects, backups, security, forms, integrations, and fixes. |
| SEO specialist | Validate URL mapping, canonicals, indexability, sitemaps, metadata, links, and crawl signals. |
| Marketing team | Confirm campaigns, landing pages, tracking, content, conversions, and reporting continuity. |
Confirm ownership of the domain, hosting, source code, analytics, Search Console, third-party accounts, and backups. Document the launch sequence, rollback plan, support contacts, and release criteria.
7. Monitor performance after the migration
Begin monitoring as soon as the new site is live. Check redirects, important pages, forms, analytics, sitemap access, crawlability, and key user journeys during the initial launch period.
Then review trends across normal reporting cycles. Monitor:
- Crawl errors, indexing changes, redirect failures, canonical conflicts, and unexpected noindex directives.
- Organic landing pages, query visibility, traffic, leads, sales, and agreed outcomes.
- Mobile and desktop speed for important templates.
- Analytics continuity, event volumes, attribution, and conversion paths.
- Availability, server errors, broken links, failed forms, and support requests.
Maintain a migration log with dates, incidents, fixes, and measurements. Change one documented variable where possible, then measure again.
Final website migration readiness checklist
- Baseline performance, SEO, traffic, conversions, and page data is saved.
- The content inventory and URL map are complete and approved.
- Priority redirects, chains, loops, and destinations have been tested.
- Canonicals, robots directives, sitemaps, links, and staging access are reviewed.
- Mobile layouts, speed, browsers, forms, integrations, and security checks are complete.
- Analytics, Search Console, SEO elements, and priority landing pages are verified.
- Backups, ownership, deployment access, contacts, and recovery plans are documented.
- Post-launch monitoring has named owners and scheduled reviews.
Delay launch when a critical journey is broken, important URLs lack approved destinations, tracking cannot be verified, production is blocked from search engines, or nobody owns post-launch investigation.
Frequently asked questions
Does a website redesign count as a migration?
It can. A redesign becomes a migration concern when URLs, templates, content, platform, hosting, domain, tracking, or technical configuration changes.
Should a staging website be blocked from search engines?
Yes. Protect staging with access controls and appropriate crawl or index directives, then verify that production is accessible and staging protections did not carry over.
How long should you monitor a website after migration?
Start immediately and continue through the site's normal reporting cycles. The appropriate period depends on traffic, seasonality, size, and complexity.
What should be compared before and after a migration?
Compare like-for-like templates, organic landing pages, conversions, indexed URLs, crawl errors, redirects, analytics events, mobile experience, and performance measurements.
Who should own the redirect map?
The developer usually implements redirects, while the SEO specialist or project lead validates them. The business owner approves important destinations and priorities.
Make migration performance measurable
A reliable process connects seven decisions: establish a baseline, map content and URLs, protect search signals, test technical performance, verify measurement, assign responsibility, and monitor after release.
Global iTech Systems Ltd supports website builds, major upgrades, testing, SEO validation, deployment, and ongoing website support. To discuss a migration or website upgrade, visit Global iTech Systems Ltd.