Moving a website to a new platform — whether from WordPress to Webflow, a custom build to Shopify, or a legacy system to a headless CMS — carries a genuine risk of SEO disruption. Rankings can drop, organic traffic can stall, and backlinks can break if the migration is handled carelessly. The good news is that a disciplined, phased approach lets you migrate website without losing SEO, and many sites end up performing better afterward. This guide walks through every step, from the audit that establishes your baseline to the post-launch checks that protect your rankings.

Why website migrations carry real SEO risk

Search engines treat a platform change as a significant event. When URLs change, content moves, or server infrastructure shifts, Google and other engines must re-crawl and re-index your entire site. If 301 redirects are missing, meta descriptions disappear, page speed drops, or the new architecture sends confusing signals, that re-crawl can produce ranking losses that take months to recover from. Even a migration executed with good intentions — launching a cleaner, faster site — can backfire if the transfer of SEO equity is incomplete. Understanding which signals matter to search engines, and how to preserve each one, is the foundation of a successful migration.

Start with a full pre-migration SEO audit

Before touching a single file or signing a new hosting contract, capture where your site stands today. This baseline is your reference point for everything that follows, and skipping it makes it impossible to know whether the migration helped or hurt.

Run a complete crawl of your current site using a tool like Screaming Frog, Sitebulb, or Ahrefs Site Audit. Export every URL, its status code, title tag, meta description, heading structure, canonical tag, and indexation directive. Note every page returning a 3xx, 4xx, or 5xx status. Simultaneously, pull organic performance data from Google Search Console for the last sixteen months — this gives you the rolling average that normalises seasonal fluctuations. Record your top-performing landing pages by clicks and impressions, because those are the pages you cannot afford to disrupt. Also export your backlink profile from a tool like Ahrefs, Moz, or Google Search Console’s link report. Every external link pointing to a URL that will change needs a redirect waiting for it on day one of the new site going live.

Choose a platform that supports, rather than fights, SEO

Not all platforms handle SEO equally well, and the choice you make will shape how much custom work you need after launch. At our website development service, we evaluate platforms against a set of SEO-critical criteria before recommending one to a client.

The platform should allow full control over title tags, meta descriptions, canonical URLs, and structured data. It should generate clean, readable URL structures without forcing dynamic parameters or session IDs into the path. It should produce valid HTML markup and allow you to edit the head section for schema, Open Graph tags, and hreflang attributes. It should render pages server-side or via static generation rather than relying entirely on client-side rendering, which can delay or prevent search engines from indexing content. And it should support a robust redirection system so that legacy URL patterns can be mapped to new ones cleanly.

A platform that scores poorly on these criteria will require expensive workarounds after launch, and some SEO deficits — like client-side rendering on a content-heavy site — can be very difficult to fix once you have committed to a build.

Map your URLs before you build anything

URL mapping is the single most important technical task in a migration. Every old URL must have a defined destination on the new site. Start by exporting the full URL inventory from your pre-migration crawl. For pages that will keep the same path on the new platform, the mapping is a one-to-one match. For pages being consolidated, retired, or renamed, decide the target URL now and document the decision.

Document your complete URL map in a spreadsheet with columns for old URL, new URL, redirect type, and any notes. A 301 redirect is the correct choice for permanent URL changes; it passes the majority of link equity from the old URL to the new one and signals to search engines that the move is permanent. Temporary redirects — 302s — should be reserved for genuinely temporary situations and should not be used for permanent URL changes.

Consider the scale of redirects you are managing. A small site with a few hundred URLs can handle a flat list of individual redirect rules. Larger sites with thousands of legacy URLs may benefit from pattern-based redirect rules that match URL segments and rewrite them systematically. Be careful with wildcard rules — test them exhaustively before going live, because a misconfigured pattern can redirect URLs to unintended destinations and create indexation problems that are hard to unwind.

We handled a structured redirect and category-based site architecture project for Pt Demolition, where dedicated service pages and a portfolio organised by industry required precise URL mapping to preserve search visibility across a broad set of legacy pages.

Platform comparison checklist

The table below compares common migration destinations against the SEO capabilities that matter most. Use it as a starting point for your own evaluation, then validate against your specific content types and technical requirements.

No single platform is universally best. The right choice depends on your content volume, team size, budget, and how much custom functionality your business needs. For complex projects involving multiple content types, user roles, and integrations — such as the custom learning management system we built for KV School of Psychology — a tailored platform approach often delivers the best long-term SEO outcomes because the architecture can be built around your content from the ground up.

Preserve every element of on-page SEO during content transfer

Moving content from one CMS to another often strips metadata if the process is manual or poorly configured. Title tags, meta descriptions, heading structures, image alt text, canonical tags, and Open Graph data all need to survive the transfer intact. The safest method is to export your content with full metadata from the old system and import it into the new one using a structured format — JSON, CSV, or XML — rather than copy-pasting through a visual editor. This preserves the markup fields that visual editors often discard.

Review every canonical URL after import. A common migration mistake is canonical tags pointing to the old domain or to URLs that no longer exist, which can cause search engines to de-index your new pages entirely. Check that internal linking structures are consistent — breadcrumbs, related-content modules, and footer navigation should all resolve to the correct new URLs. Images are another frequent source of loss. Verify that image file names, alt text, and surrounding contextual content have transferred correctly, because image search can be a meaningful traffic source that disappears overnight if images are re-uploaded without their original optimisation.

Lock down the technical foundations on the new server

Technical SEO is not a one-time setup — it needs to be verified after migration as thoroughly as it was on the old site. Start with an SSL certificate. Every page on the new domain must serve over HTTPS with a valid, non-expired certificate. Mixed content — where HTTPS pages load insecure HTTP resources — will trigger browser warnings and can affect rankings.

Review your robots.txt file. A default or accidentally overwritten robots.txt on the new server can block search engine crawlers from indexing your entire site. Check that no production-blocking noindex tags remain from staging or development environments. These are among the most common post-migration disasters, and they are entirely preventable with a pre-launch checklist.

XML sitemaps should be regenerated for the new URL structure and submitted to Google Search Console and Bing Webmaster Tools as soon as the site goes live. This accelerates the re-crawl process. If your old sitemap included hreflang annotations, video sitemaps, or image sitemaps, rebuild those too. Also update the sitemap reference in your robots.txt file to point to the new location.

Page speed is a confirmed ranking factor, and a new platform will not automatically inherit the performance profile of the old one. Run Google PageSpeed Insights or Lighthouse on a representative sample of pages before launch. Address issues with render-blocking resources, uncompressed images, and caching headers. A migration that trades a fast legacy site for a slow new build can produce measurable ranking declines even when every redirect is correct.

For healthcare and professional practices, where trust signals and page speed both influence search visibility, we have seen how a technically sound build supports long-term organic performance. The practice website we developed for Dr Raj Palaniappan prioritises responsive cross-device performance alongside content architecture that supports both patient conversion and search visibility.

Monitor, validate, and react after launch

The migration is not complete the moment the new site goes live. The first four to eight weeks after launch are the most critical period for monitoring. Set up daily checks in Google Search Console for crawl errors, coverage issues, and manual actions. Watch the URL Inspection tool for individual pages that are not being indexed as expected.

Track organic traffic in Google Analytics or your analytics platform of choice. Compare daily and weekly sessions against the same period from the previous year — year-over-year comparisons are more reliable than month-over-month during a transition, because they smooth out seasonal patterns. Expect a brief dip in the first week or two as search engines process the redirects and recrawl the new structure. A dip that persists beyond three weeks signals a problem that needs investigation.

Monitor your top-performing landing pages individually. If any of your highest-traffic pages show a significant ranking drop, investigate the specific URL — check that its redirect is in place, that its meta tags transferred correctly, and that it is not blocked by robots.txt or a noindex tag. Spot-check external backlinks using your link report to confirm that the redirects are passing equity. Tools like Ahrefs or Moz will show you whether redirect chains are forming, which can dilute link equity over time.

Once the new site has stabilised — typically after sixty to ninety days of consistent monitoring — run a fresh full crawl and compare it against your pre-migration baseline. Verify that the total number of indexable pages is consistent, that redirect chains are minimal, and that no orphaned pages have appeared. This comparison report is also valuable documentation for stakeholders who want to see what the migration achieved.

Common migration mistakes that hurt rankings

Several errors appear so frequently across migrations that they are worth calling out specifically. Blocking the new site in robots.txt is perhaps the most damaging — it prevents indexing entirely and can go unnoticed for weeks if nobody checks the file after launch. Forgetting to set up redirects for every changed URL is a close second; orphaned pages with no inbound redirect lose all the equity they have built and disappear from search results. Changing URL structures without updating internal links creates redirect chains that slow crawling and dilute equity. Launching without regenerating and submitting an XML sitemap delays the re-crawl unnecessarily. And migrating content without carrying over heading structures, alt text, and schema markup strips away the contextual signals that help pages rank for their target terms.

A structured, phased approach catches most of these issues before they reach production. A well-executed migration for a complex platform, such as the one we delivered for The Roots Company, requires careful coordination between content structure, URL mapping, and technical configuration to ensure that every page’s SEO value transfers cleanly to the new environment.

When to bring in specialists

Small migrations on simple sites — a handful of pages with no complex functionality — can be managed with the steps above and careful attention to detail. Larger migrations involving thousands of pages, multi-regional hreflang setups, e-commerce faceted navigation, or migration from a heavily customised legacy system benefit from specialist involvement. An experienced team will audit your current SEO performance, build the URL map, configure the redirects, validate the technical setup, and monitor post-launch, reducing the risk of a ranking event that takes months to recover from.

If you are planning a platform change and want to make sure your organic traffic is protected throughout the process, our web design and development team can support the full migration workflow from audit through to validated launch.

Frequently asked questions

How long does it take for rankings to recover after a website migration?

There is no fixed timeline. Most sites see rankings stabilise within four to eight weeks if redirects are correct and technical SEO is intact. More complex sites with thousands of pages or significant content restructuring may take twelve weeks or longer. The key variables are the completeness of your 301 redirect map, the speed at which search engines recrawl the new structure, and whether any technical issues — like noindex tags or broken canonical URLs — need fixing after launch. Monitor Search Console weekly and compare organic traffic year-over-year to get an accurate picture of recovery progress.

Will a 301 redirect pass all of my SEO value to the new page?

A 301 redirect passes the majority of link equity from the old URL to the new one, which is why it is the correct choice for permanent URL changes during a migration. It does not pass 100 percent in every case — some equity can be lost in the transfer, particularly if the new page has significantly different content or a weaker internal linking profile. The best way to minimise equity loss is to redirect each old URL to the most contextually relevant new URL, maintain strong internal linking on the new site, and ensure the redirected page delivers equivalent or better content than the original.

Should I keep my old URLs on the old platform during the migration?

No. Once the new site is live and 301 redirects are confirmed working, the old site should be taken down or its domain should be configured to redirect everything to the new domain. Running two live versions of the same content creates duplicate content issues and splits the signals search engines use to evaluate authority. Take the old site offline promptly after validating that every redirect resolves correctly, and update any external links you control — Google Business Profile, social media profiles, directory listings — to point to the new URLs.

What happens to my backlinks after a migration?

Backlinks pointing to your old URLs will continue to pass equity as long as those URLs return a 301 redirect to the correct new destination. Search engines follow 301 redirects and transfer most of the link equity through them. However, it is worth auditing your highest-value backlinks after launch to confirm that the redirects are in place and not forming redirect chains. If a high-authority site links to a URL that is not redirecting correctly, that equity is effectively lost. Reach out to webmasters of important referring domains if you discover broken links, and ask them to update the destination URL.

Can I migrate in phases instead of all at once?

Phased migrations — moving sections of a site incrementally rather than launching everything at once — are a valid strategy for large sites and can reduce risk. The key requirement is that each phase must include its own set of 301 redirects, updated sitemaps, and Search Console notifications. You cannot migrate section A, leave section B on the old platform, and expect search engines to treat the transition cleanly. Phased migrations require more project management overhead than a single launch, but they give you the ability to validate each section before moving on to the next, which can be safer for very large or complex sites.

How do I know if the migration was successful?

Define success criteria before you launch. A successful migration means that the new site retains or improves upon the pre-migration baseline for organic traffic, indexing coverage, and rankings on priority keywords. Measure against the data you captured during the pre-migration audit — not against the weeks immediately before launch, because seasonal effects can distort short-term comparisons. Key signals to watch are: total indexed pages in Search Console, organic session trends in analytics, rankings for your top twenty to thirty priority keywords, and the volume of crawl errors. If all of these are stable or improving after ninety days, the migration has been successful.

Planning a platform change and want to make sure your organic visibility stays intact? Our team handles the full migration workflow — from pre-launch audits and redirect mapping to technical validation and post-launch monitoring. Reach out at info@monkcreatives.com and we will walk you through the process.