Ranking loss during a migration isn’t unique to any one platform switch. Whether you’re moving to a new CMS, a new host, a new domain, or a full redesign, the underlying risks and the fixes for them are largely the same. Here’s the platform-agnostic checklist.
Every migration risk to rankings comes down to one thing: does Google still recognize this as the same content it already trusted, just at a new address?
Primo Collab
Build a complete URL inventory before touching anything
Crawl the existing site and list every indexed URL. This is the single most important pre-migration step, and the one most often skipped or rushed. You cannot redirect what you haven’t inventoried, and any URL left off the list is a URL that will 404 once the old site goes down.
Map every old URL to its new equivalent, specifically
Every changed URL needs a 301 redirect to its specific new equivalent, not a blanket redirect to the homepage. Search engines read a homepage catch-all as a signal that the original content no longer exists, which forfeits the page-specific authority that URL had built up. This step takes real time to do properly and is the one most commonly cut short under deadline pressure.
Carry over metadata, not just visible content
Title tags, meta descriptions, header structure, and image alt text are direct ranking and click-through signals. It’s easy to migrate the visible page copy while losing this metadata in the process, especially when moving between platforms with different default handling.
Preserve internal linking structure
Internal links distribute authority across a site and signal which pages matter most. A migration that changes navigation structure or drops old internal links without rebuilding equivalent ones can quietly undermine pages that were ranking well, even if those pages themselves migrated fine.
Submit an updated sitemap immediately at launch
Don’t wait for organic discovery. Submit the new sitemap to Google Search Console the moment the new site is live, so re-indexing of the correct URLs starts as early as possible.
Monitor daily for the first few weeks, not weekly
Coverage errors, unexpected 404 spikes, and crawl anomalies are fast to fix on day 2 and much more expensive to fix on day 30 after they’ve already affected rankings. Daily Search Console checks during the transition window catch problems while they’re still cheap to fix.
Resist making unrelated changes during the transition
It’s tempting to also refresh content, restructure navigation, or update page titles while everything’s already in motion. If rankings shift during the transition, isolating the migration as the cause gets much harder when several changes happened simultaneously.
The mistake to avoid
Treating SEO as a cleanup step after the migration is technically finished, rather than a requirement built into the migration plan from day one, is the single biggest cause of avoidable ranking loss. The redirect map and metadata carryover need to exist before the new site goes live, not get reconstructed afterward once traffic has already dropped.