SEO-safe site migrations

Migration means far more than moving domains. Any of these counts, and each carries SEO risk: changing platform (WooCommerce to Shopify, for instance), redesigning with new templates and URLs, restructuring your site architecture, moving to HTTPS, or consolidating several sites into one. The common thread is change to URLs, content or structure at scale — and Google has to re-learn all of it.

Why migrations lose traffic

Rankings are attached to specific URLs and the equity — links, history, relevance signals — they have accumulated. When URLs change without proper handling, that equity is stranded: old pages 404, links point nowhere, and Google drops the rankings until it works out what replaced what. Most migration disasters are not caused by the new site being worse; they are caused by the transition being botched. The single most important principle is that every URL that had value must lead search engines and users to its new equivalent.

Plan before you touch anything

Good migrations are won in preparation. Before launch, establish a baseline you can measure against and a complete inventory of what exists:

• Crawl the entire current site and export every indexable URL
• Pull top pages by traffic, rankings and backlinks so you know what must be protected
• Record baseline metrics — organic sessions, impressions, key rankings — to compare after launch
• Export current Search Console and analytics data before anything changes
• Identify pages with valuable backlinks; those are non-negotiable to preserve

The URL mapping document

The heart of any migration is a mapping that pairs every old URL with its new destination, one to one wherever possible. Map like to like: a product page to the equivalent product page, a category to its closest category. Where a page genuinely has no equivalent, map it to the most relevant parent rather than dumping it on the homepage — a mass redirect to the homepage is read by Google as a soft 404 and passes little value. This document is tedious to build and it is exactly what protects your traffic.

301 redirects: getting them right

Redirects are how equity transfers from old URLs to new ones. Use permanent 301 redirects, not temporary 302s, so signals consolidate on the new URL. Watch for the details that quietly leak value:

• Redirect in a single hop — avoid chains where A points to B points to C, which dilute equity and slow crawling
• Make sure redirects resolve to live 200 pages, not to other redirects or error pages
• Do not rely on meta refresh or JavaScript redirects for SEO-critical paths; use server-level 301s
• Preserve HTTPS and canonical consistency through the redirect

If the migration also involves moving to HTTPS, treat that with the same care — our HTTPS and SEO guide covers the redirect and mixed-content pitfalls specific to that switch.

Test on staging first

Never migrate blind. Build and validate the new site on a staging environment, and make sure that environment is blocked from indexing — via authentication rather than a stray noindex or robots.txt rule that could survive into production and deindex the live site. On staging, crawl for broken links, verify the redirect map behaves as designed, confirm titles, meta descriptions, headings, structured data and canonical tags carried over, and check that your XML sitemap and robots directives are correct. Our robots and sitemap guide is worth a pass here, since a misconfigured robots file is one of the most common ways a launch goes wrong.

Launch and the critical days after

Launch during a low-traffic window and move straight into monitoring — the first days decide the outcome. Immediately after go-live:

• Submit the new XML sitemap in Search Console and, for a domain change, use the Change of Address tool
• Crawl the live site to catch 404s, redirect chains and broken internal links
• Watch indexation, crawl stats and error reports daily for the first weeks
• Keep the old redirect rules in place indefinitely — they do not expire safely
• Track rankings and organic traffic against your pre-launch baseline

Expect some short-term fluctuation even in a clean migration; Google needs time to recrawl and reassign signals. What you are watching for is a sharp, sustained drop, which points to a redirect or indexing fault to fix fast. If you would rather not run a large migration alone, our technical SEO team in Miami plans and supervises them end to end.