Website Migration SEO Checklist: How to Move Your Website Without Losing Google Rankings

A website migration is the process of making significant changes to a website's domain, platform, URL structure, design, or infrastructure. These changes can affect how search engines crawl, index, and evaluate your website, making careful planning essential to preserve organic visibility and ensure a smooth transition. This includes: - Moving to a new domain (rebranding, acquisition, ccTLD consolidation) - Switching CMS platforms (WordPress to Shopify, custom build to WordPress, etc.) - Redesigning the site structure, navigation, or URLs - Moving from HTTP to HTTPS - Consolidating multiple sites into one - Changing hosting providers or server infrastructure Each of these changes can influence your website's search performance. When multiple changes such as a new domain, a CMS migration, and a website redesign are introduced at the same time, the complexity increases significantly. A well-planned migration strategy helps reduce risks, preserve rankings, and maintain organic traffic throughout the transition.

Search engines build trust and relevance signals around specific URLs over time. When those URLs change, disappear, or get restructured without a plan, Google must rediscover and re-evaluate your entire site. Here's what typically goes wrong: - Broken redirects send both users and search bots to 404 pages - Lost internal linking structure weakens the pages that used to pass authority to your key landing pages - Duplicate content appears when old and new URLs are both live and indexable - Missing meta data on new pages leaves Google guessing what a page is about - Slower Core Web Vitals on the new site can quietly suppress rankings even if content is untouched None of this is permanent damage if it's caught early. The problem is that most teams only notice after traffic has already dropped, which is weeks too late.

Migration usually gets triggered by a business decision, not an SEO one. Common scenarios include: - A rebrand that requires a new domain name - Outgrowing a CMS that can't support new features - A design refresh after several years on the same look - Merging two brands or product lines into a single site - Moving from a subdomain structure to subfolders (or vice versa) - Expanding into ecommerce and needing a platform switch In each case, the SEO plan needs to be built alongside the design and development plan, not bolted on afterward.

This is the core of your SEO migration framework. Treat it as a working document your whole team can check off, not a one-time read. Pre-Migration Phase - Technical audit — Crawl the existing site and document every indexable URL, its ranking keywords, organic traffic, and backlinks. You cannot protect what you haven't measured. - Backup — Take a full backup of the current site, database, and files before any changes go live. This is your safety net if something breaks post-launch. - URL mapping — Create a spreadsheet mapping every old URL to its new equivalent. This single document is the foundation for your entire redirect strategy. - Redirect mapping — Turn the URL map into 301 redirects. Every old URL that had traffic, rankings, or backlinks needs a direct, one-to-one redirect, not a blanket redirect to the homepage. - Internal links — Update internal links to point to new URLs directly, rather than relying on redirects to carry the weight. Redirect chains slow crawling and dilute link equity. - Canonical tags — Make sure every new page has a self-referencing canonical tag, and that no page accidentally points to an old or staging URL. - Meta data — Carry over optimized title tags and meta descriptions from top-performing pages, rather than letting a CMS auto-generate new ones. - XML sitemap — Generate a fresh sitemap reflecting the new URL structure and prepare it for submission at launch. - Robots.txt — Check that the new robots.txt file doesn't accidentally block important sections and doesn't carry over a staging-site "disallow all" rule. - No index issues — Confirm no live pages carry a no index tag left over from staging or testing. - Core Web Vitals — Test loading speed, interactivity, and layout stability on the migrated website before launch. A slower site can offset SEO gains from a better design. - Schema markup — Recreate structured data (organization, breadcrumbs, product, FAQ, etc.) that existed on the old site, since it often gets lost in a rebuild. - Image optimization — Compress images, retain descriptive file names, and carry over meaningful alt text rather than generic placeholders. - Content preservation — Keep your best-performing content intact. Migration is not the time to quietly cut pages that are ranking well. - Analytics backup — Export historical data from your current analytics setup so you retain a clean before-and-after comparison. - Google Search Console — Verify the new property (or domain) in Search Console ahead of launch, so tracking starts immediately. - GA4 setup — Confirm GA4 tracking is correctly installed and firing on staging, not just production, before launch day. - Staging testing — Run the entire migration validation process against the staging environment first, including a crawl to catch broken links, missing redirects, and indexing issues. Launch Process - Push redirects live before the new site goes public - Submit the new XML sitemap in Search Console - Use the Change of Address tool in Search Console if the domain changed - Monitor server response codes in real time during launch - Re-crawl the live site immediately after launch to catch anything missed in staging Post-Migration Action List - Rank tracking — Track keyword positions daily for the first two to four weeks. Expect some fluctuation; watch for sustained drops. - 404 monitoring — Check Search Console and server logs for 404s daily in the first two weeks. - Crawl errors — Watch the Search Console coverage report for spikes in errors or excluded pages. - Redirect validation — Spot-check redirects regularly to confirm they still resolve correctly and haven't been overwritten by a CMS update. - Performance tracking — Recheck Core Web Vitals a week or two after launch, once real user data populates. - Index coverage — Confirm new URLs are being indexed, and old ones are dropping out of the index gradually, not abruptly. - Traffic monitoring — Compare organic sessions and conversions against your pre-migration baseline weekly. - Recovery plan — Have a documented rollback or fix-forward plan ready in case a critical issue surfaces after launch.

Each of these is predictable, and each is avoidable with a plan: - Redirecting everything to the homepage — Loses page-specific relevance and confuses users. - Launching without a redirect map — Leads to mass 404s and lost link equity. - Forgetting to update internal links — Search engines rely on internal links to understand site structure. - Skipping a pre-launch crawl of staging — Issues get discovered in production instead of before launch. - Ignoring Core Web Vitals on the new build — A slower site can offset content and structure improvements. - Not exporting historical analytics data — Makes it impossible to measure the real impact of the migration. - Treating migration as a one-day event — Recovery and optimization take weeks, not hours.

The gap between a DIY migration and a professionally managed one shows up across five factors: - Redirect mapping — DIY: often incomplete or generic. Professional: built from a full URL and traffic audit. - Timeline — DIY: reactive, fixes happen after traffic drops. Professional: planned in phases with pre-launch testing. - Monitoring — DIY: ad hoc, usually after a drop is noticed. Professional: structured daily validation for weeks post-launch. - Tools used — DIY: basic CMS plugins. Professional: crawlers, log file analysis, Search Console API. - Risk of ranking loss — DIY: higher, especially on domain changes. Professional: minimized through a structured SEO migration process. DIY migration can work for small, low-traffic sites with a simple structure. Larger sites with meaningful organic traffic carry more risk, and that risk scales with every additional URL.

Every site migration plan we run starts with a full crawl and traffic audit of the existing site, so nothing gets missed in the redirect map. From there, the team builds out redirects, meta data, and schema alongside the development team, rather than treating SEO as a final step before launch. Post-launch, tracking runs daily for the first few weeks; ranking positions, crawl errors, index coverage, and traffic are all compared against the pre-migration baseline. If something looks off, it gets flagged and fixed before it turns into a real drop. This approach reflects the same site migration best practices used across the agency's SEO, website development, and CRO work, where technical execution and search visibility are planned together instead of separately.

A domain migration SEO project or a full site redesign doesn't have to cost you rankings. Most of the damage seen after migrations comes from missing a handful of predictable steps, redirects, canonical tags, internal links, or post-launch observation, not from some unavoidable Google penalty. Build your process before development starts, test everything on staging, and keep watching the data for weeks after launch. That's the difference between a website redesign SEO project that grows traffic and one that quietly loses it. If you're planning a redesign, CMS switch, or domain change and want a second set of eyes on your redirect map before launch, Pulse n Pixels' SEO team can review your migration plan and flag risks before they become ranking losses.