A website redesign can improve structure, content and usability, but it can also remove pages that earn traffic, change valuable URLs or break internal links. SEO migration planning is the work that connects the old site to the new one.

No checklist can guarantee unchanged rankings. Search engines still need to crawl, interpret and evaluate the new site. A disciplined migration reduces avoidable mistakes and makes post-launch problems easier to diagnose.

Start with an inventory of the current site

Before deciding what the new site should contain, collect the current URLs, titles, descriptions, canonical targets, crawl status, internal links, organic landing-page data and backlinks where available. This establishes what already exists and which pages deserve closer review.

  • Keep pages that answer a useful search intent and still support the business.
  • Consolidate overlapping pages only when the new destination genuinely covers their purpose.
  • Remove weak pages deliberately rather than letting them disappear during design.
  • Record files, images and downloadable assets that have their own URLs or external links.

Map every old URL to a clear outcome

A migration map should give each old URL one outcome: keep the URL, move it to a new equivalent, consolidate it into a stronger page, or return a genuine not-found response. Redirecting every removed page to the homepage hides the problem and creates a poor user path.

Google recommends preparing an old-to-new URL mapping and using permanent server-side redirects when URLs change. The new destination should be the closest useful equivalent, not merely a convenient page.

Preserve the search intent, not just the old copy

A redesign is a chance to improve a page, but the new version should still satisfy the reason people found it. If a page ranks for a commercial service query, replacing it with a short brand statement can remove the information that supported its visibility.

  • Retain the primary topic and user job.
  • Carry over useful evidence, examples, FAQs and decision criteria.
  • Improve headings and structure without forcing exact-match keywords into every line.
  • Keep content that earns qualified traffic even if it is not prominent in the new visual direction.

Update technical signals on the new site

The new pages need self-consistent technical signals. Canonical URLs should use the production domain and final paths. Internal links should point directly to those paths instead of relying on redirects. Indexing directives, metadata, structured data and sitemap entries should match the intended public state.

Canonical and domain consistency

Choose one production hostname and use it consistently in canonicals, sitemaps, hreflang annotations and internal links. Preview and staging hosts should not compete with production.

Titles and descriptions

Migration is not a reason to copy every old title unchanged, but important pages still need unique titles and descriptions that reflect their actual purpose. Check the rendered HTML rather than assuming a CMS field reached the page.

Structured data

Carry over only structured data that remains accurate and visible on the redesigned page. A new visual system does not justify unsupported reviews, organization details or offers.

Test redirects before changing the domain

Redirects should be tested as a complete set. Check that each important old URL reaches the intended new URL in one permanent hop, that redirect rules do not conflict, and that no new internal link still points to an old path.

Webflow supports individual, folder-based and imported 301 redirect rules. The implementation tool matters less than the verified result returned by the public URL.

Launch with a measurement plan

  • Verify the production domain and sitemap in Google Search Console.
  • Confirm analytics and conversion events on the final domain.
  • Crawl the public site and check status codes, canonicals, robots directives and internal links.
  • Test representative forms, booking paths and integrations.
  • Keep the old URL inventory so unexpected 404s can be compared against the migration plan.

Monitor the first weeks after launch

Watch indexing, crawl errors, submitted sitemap status, organic landing pages and conversion paths. Some movement is normal while search engines process the change. Investigate patterns rather than reacting to one daily fluctuation.

A successful SEO migration is not a promise that nothing will move. It is a controlled change with clear mappings, testable signals and enough evidence to diagnose what happens next.

Frequently asked questions

Should every old URL be redirected?

No. Redirect URLs that have a useful equivalent. A removed page with no relevant replacement can return a proper not-found response.

Can I change the platform and domain at the same time?

It is possible, but changing several systems together increases the number of variables. If the project allows it, separating major changes can make testing and diagnosis easier.

How long should redirects remain?

Treat important permanent redirects as durable infrastructure. Removing them too early can break old links and bookmarks that still send visitors.