A site migration — whether platform change, domain move, or redesign — carries real SEO risk if not executed methodically. This checklist covers pre-launch planning, active migration mechanics, and post-launch validation to preserve rankings, traffic, and indexation through the transition.
Most migration failures trace back to incomplete discovery. Before you touch DNS or deploy new code, you need a forensic snapshot of the current site: every indexed URL, every redirect chain, every piece of structured data, and every inbound link anchor. Use Screaming Frog or Sitebulb to crawl the live site with user-agent set to Googlebot, export the full URL list with status codes, canonical tags, hreflang declarations, and schema markup. Pull Google Search Console performance data for the past sixteen months to identify which pages actually drive traffic — those are your high-stakes redirects. Export your backlink profile from Ahrefs or Majestic and flag any links pointing to non-homepage URLs that will move. Document existing 301 chains because stacking a new redirect on top of an old one dilutes equity and slows Googlebot. This inventory becomes your test matrix and your rollback reference if rankings drop unexpectedly post-launch.
Set up the new site in a staging subdomain or password-protected directory, never on the live domain. Apply rel=canonical tags pointing back to the current live URLs so Google ignores any accidental leaks or bot access. Block the staging environment in robots.txt and with HTTP authentication, but periodically test with Googlebot user-agent to confirm crawlability matches production. Map every old URL to its new equivalent in a spreadsheet: source URL, destination URL, redirect type, priority tier based on traffic and backlinks. If you're consolidating pages, decide now whether to 301 many-to-one or serve 410 Gone for true deletions — don't orphan valuable content by accident. Run the new site through the same crawl tool and compare taxonomy, internal link counts, page depth, and structured data coverage against the baseline. Gaps here mean lost equity or indexation issues after launch. Load test the new server under expected traffic plus twenty percent headroom; a slow site post-migration tanks Core Web Vitals and user experience simultaneously.
Implement 301 redirects server-side in Apache, Nginx, or your CDN config — avoid JavaScript or meta-refresh redirects because Googlebot may not follow them reliably. Test every redirect in the mapping spreadsheet using a bulk redirect checker or a custom script that fetches response headers. Confirm the final destination returns 200, not another redirect, and verify the redirect chain length stays at one hop. For large migrations with thousands of URLs, group redirects by pattern (category pages, product pages, blog posts) and apply regex rules where possible to reduce config bloat. Set up wildcard catches for common URL variations — trailing slash, uppercase versus lowercase, www versus non-www — so users and bots always land somewhere useful. If you're changing domains, configure the old domain's server to 301 every path to the matching path on the new domain, and keep that configuration live indefinitely. Test a sample of high-traffic URLs manually in incognito mode across desktop and mobile to catch any client-side issues that automated tools miss.
Schedule the launch during low-traffic hours for your audience, typically mid-week overnight in your primary market's timezone. Flip DNS, deploy the new code or platform, and activate the 301 redirect rules simultaneously. Within fifteen minutes, manually check ten high-value URLs to confirm they redirect correctly and render properly on desktop and mobile. Submit the new XML sitemap to Google Search Console and request indexation for the homepage and top twenty landing pages using the URL Inspection tool. Monitor server logs in real time for 404 spikes or redirect loops — if error rates exceed normal by more than five percent, pause and diagnose before Googlebot caches bad responses. Update internal links in the new site to point directly to new URLs rather than relying on redirects; this reduces latency and clarifies your preferred structure for Google. Verify Google Analytics and tag manager fire correctly on the new domain or platform, and confirm goal and event tracking still works. Check that robots.txt on the new site allows Googlebot and that no staging-environment blocks carried over.
For the first seventy-two hours, check Google Search Console hourly for coverage errors, indexation drops, or mobile usability issues. Compare organic sessions in Analytics hour-over-hour against the prior week's pattern; traffic dips of fifteen to twenty percent are normal for the first day as Google re-crawls, but sustained drops beyond forty-eight hours signal a problem. Run daily crawls of the new site to catch any broken internal links, orphaned pages, or schema errors introduced during the rush. Monitor Core Web Vitals in Search Console and PageSpeed Insights — migrations often degrade LCP or CLS if new themes or image handling differs from the old setup. Set up uptime monitoring with Pingdom or UptimeRobot to catch server failures immediately. If rankings for priority keywords fall more than ten positions within a week and you can't attribute it to redirect or indexation fixes, consider a phased rollback: restore the old domain while you debug. Keep the old site's server running in read-only mode for at least thirty days as a safety net, and maintain access to the old codebase and database backups.
Google typically re-indexes a migrated site over two to six weeks depending on crawl budget and site authority. Use the URL Inspection tool in Search Console to manually request indexation for pages that haven't appeared in the new index after seven days. If you changed domains, update your Google Business Profile, social media profiles, and any directory listings to the new URL within the first week; this sends consistent signals and preserves referral traffic. Reach out to high-authority backlink sources that link to specific old URLs and ask them to update the link to the new destination — phrase this as helping them avoid broken links rather than asking a favor. For lower-tier backlinks, rely on the 301 redirects to pass equity; manual outreach doesn't scale beyond fifty to seventy-five links. Monitor branded search volume in Google Trends or Search Console to catch any brand-awareness dips caused by user confusion. If you migrated to a new brand or domain name entirely, expect a temporary drop in direct and branded traffic while users adjust and search engines re-associate your content with the new identity.
A protocol-only migration from HTTP to HTTPS typically takes one to two weeks and centers on certificate installation, HSTS headers, and internal link updates. A domain change without platform or design changes takes three to five weeks: discovery, redirect mapping, DNS cutover, and indexation monitoring. A platform migration — WordPress to Shopify, Wix to Webflow — often requires four to eight weeks because taxonomy, URL structure, and template logic all shift, demanding deeper redirect logic and content QA. Redesigns layered onto a platform or domain change add two to four weeks for design validation, accessibility testing, and Core Web Vitals optimization before launch. Enterprise sites with tens of thousands of URLs benefit from phased rollouts: migrate one category or subdomain, monitor for a week, then proceed if metrics hold. Smaller sites under five hundred pages can migrate in a single cutover if the redirect map and staging tests are thorough. Free migration checklist templates exist from Moz, Ahrefs, and Google's own support docs, but adapt any template to your site's specifics rather than following it verbatim.
Maintain 301 redirects indefinitely if possible, or at minimum for one year. Backlinks continue to accumulate over time, and users may have old URLs bookmarked or cached. Google's John Mueller has stated that keeping redirects live long-term ensures you don't lose equity or indexation. If server resources become an issue, prioritize redirects for URLs with backlinks or historical traffic.
Yes, phased migrations reduce risk for large or complex sites. Migrate one subdirectory, product category, or subdomain first, monitor rankings and traffic for a week, then proceed with the next segment. This approach isolates problems and gives you time to refine redirect rules and fix template issues before they affect the entire site. Coordinate with your development and SEO teams to avoid conflicting configurations.
A 301 redirect is a server-level instruction telling browsers and bots that a URL has permanently moved; it's required on launch day to send users and Google to the new location. A rel=canonical tag is an HTML hint suggesting which version of a page to index; use it in staging to prevent premature indexation of the new site. After launch, remove canonicals pointing to old URLs and ensure new pages self-canonicalize or point to your preferred version if duplicates exist.
Check the timing and scope in Google Search Console. If coverage errors or excluded pages spike within days of your launch, the migration is likely the cause. If rankings drop gradually across many sites in your niche at the same time, suspect an algorithm update. Cross-reference your launch date against known Google update calendars and review Search Console's manual actions panel to rule out penalties. Server logs showing Googlebot crawl errors or redirect chains also point to migration issues.
Avoid changing URL structure unless absolutely necessary. Each URL change requires a redirect and introduces re-indexation delay and equity dilution risk. If your current URLs are keyword-rich, logical, and indexed, preserve them on the new platform even if the default structure differs. If you must change structure for technical reasons — moving from parameters to clean paths, for example — map every old URL one-to-one and test redirect coverage exhaustively in staging.
At minimum, use a desktop crawler like Screaming Frog or Sitebulb for URL inventory and comparison, Google Search Console for indexation and coverage monitoring, Google Analytics for traffic validation, and a redirect checker tool or script to test your 301 map. Add a server log analyzer if you have access to raw logs, and PageSpeed Insights or Lighthouse for Core Web Vitals tracking. Backlink tools like Ahrefs or Majestic help identify high-value inbound links that need updating. For large migrations, consider enterprise SEO platforms like Botify or Conductor for automation and anomaly detection.