Website Migration Checklist: Avoid SEO and Downtime Pitfalls

Website migration — whether changing domains, switching hosting providers, restructuring URLs, or moving from HTTP to SSL/TLS проверку — is one of the riskiest operations in web management. Done poorly, it can destroy search engine rankings, break incoming links, and cause extended downtime. This checklist covers every phase of a successful migration with minimal disruption to users and search visibility.

Types of Website Migration

Migration Type	Risk Level	SEO Impact	Example
Domain change	Very High	Major — all domain authority must be transferred	oldsite.com → newsite.com
Protocol change	Medium	Moderate — search engines must reindex	HTTP → HTTPS
URL restructuring	High	Significant — all internal and external links affected	/blog/post-slug → /articles/category/slug
Hosting/server change	Low-Medium	Minimal if done correctly	AWS → GCP, shared → VPS
CMS change	High	Significant — URL patterns often change	WordPress → custom PHP
Design/content overhaul	Medium	Variable — depends on structural changes	Full redesign with new page structure

Phase 1: Pre-Migration Planning

Audit the Current Site

• Crawl the entire site and export all URLs with their HTTP status codes
• Document all pages that receive organic search traffic (use Google Search Console)
• List all pages with inbound links from external sites (use Ahrefs, Moz, or Search Console)
• Record current rankings for target keywords
• Export XML sitemap and verify it matches crawl results
• Screenshot key pages for visual comparison after migration

Create the Redirect Map

The redirect map is the most critical document in any migration. It maps every old URL to its corresponding new URL:

# redirect_map.csv
old_url,new_url,priority
/blog/my-post,/articles/my-post,high
/services/web-design,/services/design,high
/about-us,/about,medium
/old-page-no-equivalent,,low  # Will return 410 Gone

Rules for redirect mapping:

• Every page with traffic or inbound links must have a redirect
• Map to the most relevant equivalent page — not the homepage
• Use 301 (permanent) redirects, not 302 (temporary)
• Avoid redirect chains (A → B → C); each old URL should redirect directly to the final destination
• Pages with no equivalent should return 410 Gone (tells search engines the page is intentionally removed)

DNS Preparation

• Lower DNS TTL to 300 seconds (5 minutes) at least 48 hours before migration
• Document all current DNS records (A, AAAA, CNAME запись, MX, TXT, SPF, DKIM, DMARC)
• Prepare new DNS records but do not publish them yet
• Verify that email delivery will not be disrupted (MX records, SPF, DKIM)

# Lower TTL 48 hours before migration
@ 300 IN A 93.184.216.34    # Was 3600, now 300

# Verify current records
dig +noall +answer example.com ANY
dig +noall +answer example.com MX
dig +noall +answer example.com TXT

Phase 2: Migration Execution

Server and Hosting Setup

• Provision the new server and verify it matches or exceeds old server specs
• Install and configure SSL/TLS certificates on the new server
• Deploy the application and verify it works using hosts file or a temporary domain
• Test all critical user journeys: forms, authentication, checkout, search
• Compare page load times — the new server should be equal or faster

Implement Redirects

# Nginx redirect map
map $request_uri $redirect_target {
    /blog/my-post         /articles/my-post;
    /services/web-design  /services/design;
    /about-us             /about;
}

server {
    listen 80;
    server_name oldsite.com;

    if ($redirect_target) {
        return 301 https://newsite.com$redirect_target;
    }

    # Default redirect for unmapped URLs
    return 301 https://newsite.com$request_uri;
}

# Apache .htaccess
RewriteEngine On
RewriteRule ^blog/my-post$ /articles/my-post [R=301,L]
RewriteRule ^services/web-design$ /services/design [R=301,L]
RewriteRule ^about-us$ /about [R=301,L]

DNS Switch

• Update DNS records to point to the new server
• Monitor DNS propagation benchmark across multiple regions
• Keep the old server running until propagation is complete (24-48 hours)
• Verify SSL certificate is working on the new server for all domains

Phase 3: Post-Migration Verification

Immediate Checks (First Hour)

• Verify the site loads correctly on the new server
• Test all redirects from the redirect map
• Check SSL certificate validity and HSTS headers
• Submit the updated sitemap to Google Search Console
• Monitor server error logs for 404s and 500s
• Test forms, login, search, and other interactive features

Short-Term Monitoring (First Week)

• Monitor Google Search Console for crawl errors daily
• Track organic traffic trends compared to pre-migration baseline
• Check server access logs for missed redirects (404 pages with significant traffic)
• Verify Google is crawling and indexing new URLs
• Monitor Core Web Vitals for performance regressions

Long-Term Monitoring (First 3 Months)

• Track keyword rankings weekly and compare to pre-migration data
• Monitor organic traffic recovery — expect a temporary dip of 10-20%
• Update internal links throughout the site to use new URLs directly
• Reach out to high-value external sites to update their links
• Monitor backlink profile for lost links

Common Migration Mistakes

Mistake	Consequence	Prevention
No redirect map	Massive 404 errors, lost rankings	Map every URL before migration
Using 302 instead of 301	Search engines do not transfer authority	Always use 301 for permanent moves
Redirect chains	Diluted link equity, slow page loads	Each URL redirects to final destination directly
Forgetting robots.txt	New site blocks crawlers accidentally	Verify robots.txt allows crawling
DNS TTL not lowered	Users hit old server for hours/days	Lower TTL 48 hours before switch
No monitoring after migration	Issues go undetected for weeks	Set up alerts for 404s, traffic drops, errors

SEO-Specific Checklist

• 301 redirects for all pages with traffic or backlinks
• Updated XML sitemap submitted to search engines
• Canonical tags pointing to new URLs
• Meta robots tags allow indexing (no accidental noindex)
• Hreflang tags updated for multilingual sites
• Structured data (Schema.org) updated with new URLs
• Google Search Console: Change of Address tool (for domain changes)
• Internal links updated to avoid unnecessary redirects
• Open Graph and social meta tags updated

Summary

Website migration is a high-stakes operation that requires careful planning, precise execution, and thorough post-migration monitoring. The redirect map is the most critical artifact — every URL that has traffic or backlinks must be accounted for. Lower DNS TTL before switching, keep the old server running during propagation, and monitor search console and analytics closely for at least three months after migration. With proper preparation, you can migrate without losing traffic, rankings, or uptime.