Website Migration Guide: How to Move to a New Platform Without Losing SEO
A complete before, during and after migration framework: URL inventory, mapping, redirects, metadata, staging QA, launch, and post-launch crawl and index monitoring.
Quick answer
To migrate a website without losing SEO, inventory every existing URL and its performance before you start, map each old URL to its closest new equivalent, implement permanent server-side redirects, carry over metadata, content, canonicals and internal links, test everything on staging, and launch with an updated sitemap and correct robots settings. Afterward, monitor crawling, indexing, rankings, traffic and redirect errors in Search Console and analytics for several weeks, fixing issues as they appear.
What Counts as a Migration
Any change that alters URLs, platform, domain or site structure: moving CMS, changing ecommerce platform, merging sites, switching to HTTPS or a new domain. This guide focuses on platform migration. For deciding whether to migrate at all, see website replatforming and redesign vs rebuild. For Shopify specifically, see migrating to Shopify.
Before: Benchmark and Inventory
You can't protect what you haven't measured. Record the current state thoroughly before touching anything.
- URL inventory from a full crawl, the XML sitemap, analytics landing pages and Search Console
- Analytics baseline: traffic and conversions by page and channel
- Search Console baseline: indexed pages, top queries, top pages, existing errors
- Ranking snapshot for priority keywords
- Backlink report showing which URLs have external links
- Content inventory: which pages move, merge or retire
- Current performance: Core Web Vitals for key templates
During: Map, Build and Test
Build the URL map first: every old URL with its new destination. Pages with traffic, conversions or backlinks get the most attention. Retired pages redirect to the closest relevant page, not the homepage.
| Task | What to do |
|---|---|
| URL mapping | One-to-one mapping from old to new URLs, prioritized by traffic and links |
| Redirects | Permanent server-side redirects; avoid chains and loops |
| Metadata | Carry over or improve titles, descriptions and headings |
| Internal links | Update links to point directly at new URLs |
| Canonicals | Self-referencing canonicals on new pages |
| Sitemap | New XML sitemap listing only live, indexable URLs |
| Robots | Staging blocked from indexing; production robots.txt reviewed before launch |
| Structured data | Recreate schema on new templates |
| Staging QA | Crawl staging, test redirects in bulk, check templates and analytics |
Staging and QA
Test on a staging environment that's blocked from search engines. Crawl it to find broken links and missing metadata, run the full redirect list against it, check every template on mobile and desktop, and confirm analytics and conversion tracking fire correctly.
Planning a platform migration?
ZSpace Labs plans and executes migrations with URL mapping, redirect testing and post-launch monitoring built into the process.
Launch
Launch at a lower-traffic time with the team available. Enable redirects, remove staging blocks from the production site (a surprisingly common mistake is launching with noindex or a blocking robots.txt), submit the new sitemap, and confirm tracking. If the domain changes, verify both properties in Search Console and use its Change of Address tool.
After: Monitor and Fix
Google's own guidance notes that medium-sized sites can take weeks to be fully reflected in search, and larger sites longer. Watch closely during that period.
- Crawl the live site to confirm redirects and internal links
- Check Search Console coverage for indexing issues and 404s
- Compare traffic and conversions against the baseline by page
- Track priority rankings
- Monitor server logs or redirect reports for missed URLs
- Fix redirect gaps and errors as they appear
- Keep redirects in place long term
Common Migration Mistakes
- Redirecting everything to the homepage
- Launching with noindex or a blocking robots.txt copied from staging
- Losing content or metadata on templates that weren't reviewed
- Redirect chains from earlier migrations left in place
- Analytics not tracking on launch day
- Removing redirects too soon
12 checks that prevent SEO and data loss
The condensed checklist below works for a quick review. For a full migration, these twelve checks are where problems most often start. Each one says what to do, why it matters and how to confirm it is done. Do not change URLs unless there is a clear reason; every changed URL needs a redirect and carries some risk. For store migrations, also see ecommerce SEO migration and migration testing.
| Check | Why it matters | How to confirm |
|---|---|---|
| 1. Full backups of site, database and media | A failed launch must be reversible | A restore has been tested, not just a backup taken |
| 2. Crawl and URL inventory of the old site | You cannot redirect pages you do not know exist | Crawl export plus URLs from analytics, Search Console and the sitemap |
| 3. Performance baselines | You need to know what normal looked like | Traffic, rankings for key pages, conversions and Core Web Vitals recorded |
| 4. URL map, old to new | Keeps links, bookmarks and rankings working | Every old URL with traffic or backlinks maps to the closest equivalent |
| 5. Permanent (301) redirects | Passes users and search signals to new URLs | Bulk-test every mapped URL: one hop, correct destination, no chains or loops |
| 6. Content and metadata parity | Missing titles, descriptions or body copy can lose rankings | Compare titles, descriptions, H1s and main content on key templates |
| 7. Canonicals, hreflang and structured data | Errors here can deindex or misattribute pages | Validate on staging; canonicals point to new live URLs |
| 8. Internal links updated | Avoids internal redirect chains and broken links | Crawl staging for links to old URLs and 404s |
| 9. Data migration verified | Orders, customers, forms and accounts must survive | Record counts and spot checks match the old system |
| 10. Analytics and conversion tracking | Without it you cannot see the impact | Test events fire on staging and production for forms, checkout and calls |
| 11. Indexing settings at launch | Staging blocks often leak into production | robots.txt and meta robots allow indexing; new sitemap submitted |
| 12. Post-launch monitoring | Problems show up over days and weeks | Daily checks of 404s, Search Console coverage, traffic and conversions for several weeks |
Website Migration Checklist
A condensed version to work from.
- Full URL inventory and baselines recorded
- URL map complete and reviewed
- Permanent redirects implemented and bulk-tested
- Metadata, content, canonicals and structured data carried over
- Internal links updated
- Staging crawled and QA'd, analytics verified
- Production indexing enabled and robots.txt correct
- New sitemap submitted in Search Console
- Post-launch monitoring scheduled for several weeks
Want your migration reviewed before launch?
Talk to ZSpace Labs about protecting your search visibility through a platform move. Explore our website and web app development services.
Conclusion
SEO-safe migration is methodical: inventory, map, redirect, test, launch, monitor. Most lasting losses come from shortcuts in one of those steps. For keeping the new site healthy afterward, see website maintenance and SEO-friendly development. For online stores, see ecommerce replatforming and Shopify store migration.
For related guides, see ecommerce platform migration, ecommerce SEO migration and ecommerce URL migration.
Common questions.
Some temporary fluctuation is common, but significant lasting losses usually come from avoidable mistakes: missing redirects, lost content, changed internal links, blocked crawling or dropped metadata. A careful migration minimizes that risk.
Permanent server-side redirects (301 or 308) from each old URL to its most relevant new equivalent. Google's guidance states that permanent redirects don't cause a loss of PageRank.
No. Redirect each old URL to its closest equivalent. Mass redirects to the homepage are typically treated like missing pages and waste the old pages' value.
Google notes it can take weeks for a medium-sized site to be reflected, and longer for large sites. Monitor closely throughout that period.
It's safer to change fewer things at once. If you must change several, invest more in mapping, testing and monitoring so problems can be traced.
A spreadsheet listing every old URL and the new URL it should redirect to, along with notes on content, metadata and priority.
Combine a crawl of the live site with your XML sitemap, analytics landing pages, Search Console pages and backlink data, since each source catches URLs the others miss.
Google recommends keeping redirects for as long as possible, generally at least a year. Many sites keep them indefinitely.
That redirects work, the new sitemap is submitted, robots.txt isn't blocking crawling, pages aren't set to noindex, analytics is tracking, and Search Console shows no spike in errors.