Interactive Website Migration Risk Assessor
Audit your website migration plan across URL structures, 301 redirect mappings, canonical continuity, and DNS cutover to prevent organic ranking drops.
Essential Pre-Launch Migration Safeguards
Every legacy URL is mapped to its exact new equivalent via 301 redirects, with zero redirect chains or unmapped 404s.
Rel=canonical tags and index/follow directives match legacy versions without accidental noindex tags from staging.
Organization, Article, Product, and Breadcrumb structured data schemas are retained on corresponding pages.
Analytics snippets, eCommerce purchase events, and ad conversion tags fire accurately on the new platform.
DNS TTL was lowered to 5 minutes 24-48 hours before migration to allow near-instant DNS cutover and rollback.
New XML sitemaps are prepared and ownership verified across both www and non-www domain protocols.
- Schema.org JSON-LD Structured Data Continuity: Organization, Article, Product, and Breadcrumb structured data schemas are retained on corresponding pages.
- Pre-Cutover DNS TTL Reduction (300 Seconds): DNS TTL was lowered to 5 minutes 24-48 hours before migration to allow near-instant DNS cutover and rollback.
- Google Search Console Verification & Sitemap Submission: New XML sitemaps are prepared and ownership verified across both www and non-www domain protocols.
The Complete Website Migration SEO Playbook
📌 On this page
1. Why website migrations tank SEO rankings
Search engines rank URLs, not domains or brands — every ranking signal (backlinks, click-through history, indexed content) is attached to a specific URL. A migration that changes URL structure, platform, or hosting without carefully preserving that URL-level continuity effectively asks Google to re-earn trust in a set of "new" pages from scratch. The good news: when redirects and technical signals are preserved correctly, search engines generally transfer ranking signals to the new URLs within weeks — migrations don't have to hurt rankings, they just require discipline most teams underestimate.
2. Building a proper 1-to-1 redirect map
Every indexed legacy URL needs an explicit 301 (permanent) redirect to its single best-matching new URL — not a blanket redirect-everything-to-homepage rule, which discards the specific relevance signals search engines associated with each page. Pull your full list of indexed URLs from Google Search Console's coverage report and your server logs (not just your sitemap, which may miss orphaned-but-still-ranking pages), then map each one individually. Watch for redirect chains (A→B→C) which waste crawl budget and dilute link equity — always redirect directly to the final destination.
3. Canonical and robots directive continuity
A shockingly common migration failure is launching with staging-environment noindex meta tags or robots.txt disallow rules still active in production — effectively telling Google not to index the new site at all. Before and immediately after cutover, verify robots.txt allows crawling, meta robots tags don't carry a stray noindex, and canonical tags point to the correct new-domain URLs (not leftover staging or legacy-domain canonicals, which can confuse which version Google should treat as authoritative).
4. The DNS cutover sequence, step by step
24-48 hours before cutover, lower your DNS TTL (Time to Live) to 300 seconds so any DNS resolver caching your records worldwide picks up the change quickly once you flip the switch. On cutover day: deploy and fully test the new site on a staging URL first, update DNS records to point to the new infrastructure, monitor propagation using a DNS checker tool, and keep the old infrastructure running (don't decommission it) for at least 1-2 weeks as a safety net in case you need to roll back.
5. Post-launch monitoring checklist
In the first 48 hours: verify Google Search Console shows the new property, check that Analytics and conversion tracking are firing correctly, and spot-check your highest-traffic legacy URLs to confirm their redirects work. In the following weeks: watch the Coverage report for crawl errors, monitor the Performance report for impression/click trends by page, and check server logs for 404s that indicate a missed redirect mapping. Set a calendar reminder to review these at 1 week, 4 weeks, and 8 weeks post-launch.
6. Having a rollback plan
Even a well-planned migration can surface an unexpected issue only visible in production traffic — a redirect rule that behaves differently at scale, a tracking script that silently breaks, or a critical page that wasn't in your URL inventory. Keep the old environment intact and DNS-ready to revert for at least the first 1-2 weeks, and document the exact rollback steps in advance (who has DNS access, how long propagation takes, what "success" looks like) so a rollback decision under pressure is executed quickly rather than improvised.
Frequently Asked Questions
Will migrating a WordPress website to a static edge platform cause SEO ranking drops?
When URL paths, canonical tags, heading structures, and 301 redirect mappings are strictly preserved, SEO rankings do not drop. In fact, improving Core Web Vitals to sub-100ms speeds typically increases organic search rankings and crawl efficiency.
Why is lowering DNS TTL critical before website migration?
Lowering the DNS Time to Live (TTL) to 300 seconds (5 minutes) ensures that global ISPs update their DNS cache immediately during cutover. If any issue arises, rolling back takes minutes rather than 24-48 hours.
What is the most common reason websites lose organic traffic after a migration?
The #1 cause of post-migration traffic loss is broken or missing 301 redirects, where legacy ranking URLs return 404 Not Found errors, permanently destroying accumulated backlink equity.
How is the readiness score calculated?
Each of the six checklist items has a fixed risk weight (25 for redirect mapping down to 10 for Search Console setup) reflecting how much organic-traffic risk that item typically carries if skipped. The score is the sum of completed items' weights divided by the total possible weight, expressed as a percentage. This weighting is a general industry heuristic, not a mathematical certainty — a site with unusually heavy reliance on structured data for rich results, for example, might weight that item higher for its specific situation.
Does checking all six boxes guarantee a zero-risk migration?
No. These six items cover the most common, highest-impact migration failure modes, but they are not an exhaustive list. Site-specific risks — custom URL rewrite rules, hreflang tags for multilingual sites, paginated content, faceted navigation with URL parameters, or third-party integrations tied to specific URL patterns — aren't covered here and should be part of your own migration checklist if they apply to your site.
How long after migration should I monitor before considering it "safe"?
Plan to actively monitor Google Search Console's Coverage and Performance reports, server logs for crawl errors, and organic traffic trends for at least 4-6 weeks post-migration. Google typically needs time to re-crawl and re-index a site's URLs even with correct redirects in place, so a temporary dip in reported impressions during the first 1-2 weeks is common and not necessarily a sign of a problem — a sustained decline past that window is the real warning sign to investigate.