The Ultimate Site Migration Checklist (Without Losing Rankings)

Migrating a website is one of the most sensitive and risky operations in SEO. It’s the digital equivalent of moving a store to a new address: if the signs aren’t updated, customers won’t find you — and in the online world, “customers” also include Google’s crawlers.

Over the last decade, I’ve participated in dozens of migrations, from local businesses refreshing their brand to large enterprises shifting entire ecosystems. Some were smooth, others turned into nightmares. What separates success from failure is planning and execution. Without it, months or even years of SEO work can vanish in a matter of weeks.

In 2025, migrations are more complex than ever. It’s not just about moving content. You must consider structured data, Core Web Vitals, JavaScript rendering, hreflang for international setups, redirects at scale, and AI discoverability. A successful migration today requires technical precision, stakeholder alignment, and proactive monitoring.

Why Migrations Fail

According to Pink and Brain’s SEO Lab, the majority of failed migrations share the same pitfalls:

• Redirects not properly mapped, leading to 404s.
• Crawl waste due to long redirect chains.
• Loss of structured data in the new templates.
• Inconsistent canonical tags.
• Broken internal linking.
• Lack of benchmarking before launch.

A migration without a checklist is like flying a plane without a flight plan.

Césinha

Types of Website Migrations

Not all migrations are equal. Here are the most common categories:

Type	Description	SEO Risk Level
Domain Change	Moving from olddomain.com → newdomain.com	High
Protocol Change	HTTP → HTTPS	Medium
Subdomain/Subfolder Shift	blog.site.com → site.com/blog	Medium
Platform/CMS Migration	WordPress → Headless CMS	High
URL Structure Redesign	/products/item → /store/item-name	High
Full Redesign	New design, templates, codebase	Medium–High

The Ultimate Checklist

A migration should be treated like a project with distinct phases: pre-migration, migration, and post-migration.

Pre-Migration (Planning & Benchmarking)

• Full crawl of the existing site (Screaming Frog, Sitebulb).
• Export all URLs, metadata, and structured data.
• Benchmark KPIs: traffic, rankings, indexed pages, conversions.
• Map all old URLs → new URLs in a redirect spreadsheet.
• Audit internal links and anchor texts.
• Create staging environment and test redirects.
• Prepare XML sitemaps for new site.
• Align with DevOps, Product, and Marketing stakeholders.

Migration (Execution)

• Implement 301 redirects (avoid chains and loops).
• Deploy canonical tags aligned with new URLs.
• Upload updated XML sitemaps in GSC.
• Validate robots.txt (ensure no accidental disallow).
• Preserve structured data in templates (test in staging).
• QA site speed and Core Web Vitals on new setup.
• Monitor server logs for crawl behavior.

Post-Migration (Monitoring & Optimization)

• Daily check of Google Search Console (coverage, errors).
• Validate redirects with tools (HTTPStatus.io, Screaming Frog).
• Compare traffic and rankings weekly.
• Monitor crawl stats with log file analysis.
• Update internal links in bulk (via database if possible).
• Submit new sitemap in Bing Webmaster Tools and GSC.
• Keep redirects live for at least 12 months.

Redirects: The Backbone of Migration

Redirects are the most critical aspect of migration. They ensure that link equity and user trust are preserved.

Best Practices

• Always use 301 (permanent) unless there’s a temporary scenario.
• Avoid redirect chains (A → B → C). Go directly (A → C).
• Never redirect everything to the homepage (causes soft 404s).
• Map redirects logically: old product → new product.
• Use Regex for scalable redirects (e.g., /old-category/(.*) → /new-category/$1).

A single broken redirect in a high-value page can cost thousands of visits overnight.

Césinha

Internal Linking and Navigation

One of the most overlooked parts of migration is updating internal links. If they still point to old URLs (even if redirected), you’re wasting crawl budget.

Instead of fixing links manually, consider bulk database updates. For example, in WordPress you can run a MySQL query like:

UPDATE wp_posts
SET post_content = REPLACE(post_content, 'olddomain.com', 'newdomain.com');

This approach updates links sitewide, ensuring that Google crawlers only see the final version of the URL.

Structured Data and Schema

In 2025, structured data is no longer optional. During migration:

• Validate that all schema (NewsArticle, Product, FAQPage, etc.) is preserved.
• Ensure @id values remain consistent (stable identifiers).
• Test with Google’s Rich Results Test.
• Implement entity-based linking (isPartOf, about, sameAs).

Remember: AI Overviews rely heavily on structured data. Losing schema during migration means losing visibility in generative search.

Common Mistakes to Avoid

• Launching without redirects fully tested.
• Blocking crawlers accidentally via robots.txt.
• Ignoring hreflang in international setups.
• Not monitoring logs to confirm Googlebot behavior.
• Changing URL structures unnecessarily.
• Deleting old pages without redirecting to equivalents.

Monitoring Success

After migration, monitor relentlessly for at least 90 days:

• Search Console → coverage, crawl stats, mobile usability.
• GA4 → compare pre- and post-launch sessions and conversions.
• Log files → confirm Googlebot hitting new URLs, not wasting on old ones.
• Rank tracking tools (Semrush, Ahrefs) → benchmark keywords weekly.

Final Migration Checklist

• ✅ Crawl old site & export all data.
• ✅ Benchmark rankings, traffic, conversions.
• ✅ Map redirects (spreadsheet + Regex rules).
• ✅ Test staging with redirects + schema.
• ✅ Launch 301 redirects.
• ✅ Validate robots.txt and canonicals.
• ✅ Submit new XML sitemaps.
• ✅ Monitor daily via GSC.
• ✅ Update internal links (DB-level if possible).
• ✅ Maintain redirects for 12+ months.

Website migrations are high-stakes operations. They can unlock new growth or devastate years of SEO work. The difference comes down to preparation, execution, and monitoring.

By following this checklist, you ensure that users, crawlers, and AI-driven search systems all transition seamlessly from the old structure to the new one.