A site migration done wrong is one of the fastest ways to erase years of SEO progress, and most of the damage is procedural rather than technical: the right checks run in the wrong order, redirect maps with holes, a launch opened to crawlers before the checklist is finished. Here is the sequence that protects rankings before, during, and after the move.
Why site migrations destroy SEO rankings: the three failure modes
Migrations lose traffic in three predictable ways. The first is incomplete redirect coverage: old URLs that ranked and held backlinks die without a forwarding address, and their equity dies with them.
The second is order of operations. Sites go live before redirects are in place, staging noindex tags travel to production, or robots.txt blocks the new site for its first crucial days. None of these are exotic failures. They are checklist failures, and they happen on professionally managed projects more often than anyone admits.
The third is the absence of a benchmark. Nobody recorded what ranked and what earned revenue before the move, so losses surface as a vague revenue dip months later instead of a fixable list of URLs. All three sit squarely in technical SEO territory, and all three are preventable.
Pre-migration: the crawl, the benchmark, and the URL map
Before anything moves, build three artifacts. First, a full crawl of the current site with Screaming Frog, exporting every indexable URL with its title, status code, and canonical. This is your inventory of what exists.
Second, a performance benchmark: top pages by clicks from Search Console, top pages by revenue from analytics, and current rankings for your tracked keyword set. This is the baseline you will measure recovery against, and without it every post-launch argument becomes opinion.
Third, the URL map: a sheet with one row per current URL and the exact destination it will redirect to on the new site. The map is finished when every URL with traffic, backlinks, or revenue has a destination. Until that sheet is complete, the migration has no launch date.
Redirect strategy: one-to-one mapping and chain prevention
Use 301 redirects, mapped one-to-one. Each old URL points to its closest equivalent: product to product, collection to collection, article to article. Bulk-pointing everything at the homepage feels efficient and works terribly, because Google treats irrelevant redirects as soft 404s and drops the equity instead of passing it.
Prevent chains. If an old URL already redirects somewhere, update the original rule to point directly at the final destination, because every hop leaks signal and slows crawling. Three-hop chains left over from previous redesigns are one of the most common finds in migration audits.
Prioritise ruthlessly. Any URL with clicks, external links, or revenue is non-negotiable. A long-tail page with zero traffic and zero links can 404 without consequence. The map exists to protect the pages that earn.
Staging checks: what to validate before go-live
Validate on staging before the world sees anything. Crawl the staging environment and check the things that break silently: canonical tags pointing at the right final URLs, internal links updated to new paths rather than routing through redirects, structured data intact, meta robots correct on every template.
Test a sample of the redirect map end to end, covering each URL pattern rather than a random handful. Compare page speed against the current site too, because launching slower is its own ranking problem and it hides inside redesigns easily.
One deliberate check before cutover: confirm the staging site is still blocked from indexing, and confirm there is a written step to unblock the production site at launch. Both directions of that mistake happen constantly, and both are expensive.
Launch day: the order of operations for a safe cutover
Launch is an order of operations, not an event. Redirects go live first, then the cutover itself. Immediately after: verify robots.txt on production allows crawling, confirm the noindex tags are gone, and submit the new sitemap in Search Console.
Keep the old sitemap available temporarily so Google recrawls the legacy URLs and processes their redirects faster. For a domain change, file the change of address in Search Console the same day, not the same week.
Then crawl the live site before the day ends and spot-check the priority redirects by hand. Finding a broken pattern at hour six costs an evening. Finding it at week three costs rankings you spent years earning.
Post-migration: what to watch in Search Console for 90 days
The first weeks are turbulent by design. Google is recrawling the site, reprocessing redirects, and re-evaluating everything it thought it knew about you. Expect movement, and judge it against your benchmark rather than your nerves.
Watch four things in Search Console: index coverage on the new URLs, the 404 report for redirect gaps you missed, impressions by page against the benchmark, and crawl stats for signs Google is struggling with the new setup. Fix any 404 with traffic or links the week it appears.
Full settling takes longer than most stakeholders expect, the same way SEO timelines generally do. If organic revenue dips during the window, paid search can hold the line short term; the trade-offs are the same ones covered in SEO versus Google Ads.
Shopify-specific migration issues: URLs, collections, and canonicals
Shopify enforces its URL structure: /products/, /collections/, /pages/. Migrating onto the platform means almost every URL changes, which makes the redirect map mandatory rather than optional. Shopify's native redirect tool handles the volume, and it auto-creates redirects when handles change, but verify rather than trust.
Watch collection paths specifically. The /collections/name/products/handle pattern canonicalises to the bare product URL, and tag-filtered collection pages generate URL variants you should exclude from the map rather than redirect individually. Collection pages carry the commercial rankings, so map them first: they are your best SEO asset and the costliest thing to break.
Across our managed SEO accounts, the results compound only when the technical foundation survives every site change: the surf brand that grew organic clicks 86% and the modest fashion store that grew impressions 144% both held their foundations steady throughout. Planning a migration? The free 48-hour audit will flag the risks before you commit.