A website migration — changing platforms, redesigning the structure, or moving to a new domain — is one of the few moments in a business’s digital life where years of accumulated SEO rankings can be wiped out in a single afternoon by a mistake that’s completely preventable. It happens more often than it should, usually because migration is treated as a design or development task rather than the technical SEO project it actually is.

This checklist walks through exactly what needs to happen before, during, and after a website migration to protect existing rankings — written for Indian business owners who are about to migrate, or considering it, and want to understand what their developer or agency should be doing.

Before Migration: Building the Full URL Inventory

The single most important pre-migration step is creating a complete inventory of every existing URL on the site that has any search visibility, along with its current ranking keywords, traffic level, and backlinks pointing to it. Skipping this step is the root cause of most migration disasters, because it’s impossible to properly redirect pages nobody remembered existed.

This inventory typically pulls from Google Search Console’s indexed page list, Google Analytics’ top-traffic pages, and a full site crawl using a tool like Screaming Frog, cross-referenced against each other to catch anything that might be missed by relying on a single source.

301 Redirects: The Single Most Critical Technical Step

Every old URL that had search visibility must 301-redirect to its most relevant equivalent new URL — not to the homepage as a blanket catch-all, which is one of the most common and most damaging migration mistakes. A blanket homepage redirect tells Google that a specific, previously ranking page about a specific topic no longer exists in any meaningful form, and the ranking signal built up for that page is largely lost.

Redirect mapping should be one-to-one wherever a genuinely equivalent new page exists, and should be implemented and tested before the new site goes live, not scrambled together afterward once someone notices traffic dropping.

Preserving On-Page SEO Elements

It’s surprisingly common for a redesign to unintentionally strip or rewrite title tags, meta descriptions, header structure, and internal linking that were quietly doing SEO work on the old site — because a design or development team focused on visual refresh isn’t necessarily thinking about preserving the SEO value embedded in that content structure.

The safest approach is treating existing high-performing pages’ core SEO elements — primary keyword placement in the H1 and title tag, existing internal links pointing to and from the page — as

requirements to preserve, not incidental content that can be freely rewritten during the redesign process.

The Launch Window: What to Monitor Closely

In the days immediately after a migration goes live, close monitoring matters far more than usual. Search Console’s Coverage and Performance reports should be checked daily for the first one to two weeks, watching specifically for a spike in 404 errors (indicating missed redirects), a sudden crawl error increase, or an unexpected drop in indexed page count.

It’s normal to see some short-term ranking fluctuation as Google recrawls and reprocesses the migrated site — the concerning pattern is a sustained drop in a specific page’s rankings correlating with a missing or broken redirect for that exact URL, which is fixable quickly if caught early but compounds if left unaddressed for weeks.

Common Migration Mistakes That Tank Rankings

Beyond blanket homepage redirects, the most damaging repeat mistakes include: migrating without any pre-migration URL inventory at all, launching the new site with noindex tags accidentally left on from staging, changing URL structures unnecessarily (a migration is not the moment to also restructure the entire site architecture unless absolutely required), and failing to update the XML sitemap to reflect the new URLs immediately at launch.

Domain changes specifically — moving from one domain to another entirely — carry additional risk and should use Search Console’s dedicated Change of Address tool alongside the redirect strategy, since this signals the domain-level change explicitly to Google rather than relying on redirects alone to communicate the domain-level change.