A website redesign or replatforming project is supposed to make things better. Yet many large organizations launch a beautiful new site and then watch organic traffic slide for months. The platform is rarely to blame. Rankings drop because of details: URLs that changed without redirects, content that quietly disappeared, metadata that didn't migrate, or a staging "noindex" tag that made it to production. This playbook walks through how to migrate a large website step by step while protecting the search visibility it took years to earn.
- Most post-migration traffic losses come from missing redirects, removed content and lost on-page signals, not from the new platform
- Benchmark everything before you change anything, so you can prove what moved
- Map every important old URL to its closest new equivalent with a single 301 redirect
- Test the staging site the way a search engine sees it, not just the way a browser shows it
- Monitor closely for 90 days and fix issues within days, not quarters
Why Rankings Drop After a Migration
Search engines rank individual URLs, built up over time through content, internal links and links from other sites. When a migration changes those URLs, removes pages or strips their signals, much of that accumulated value is put at risk. The usual culprits:
- Changed URLs with no redirects, or redirects pointing to irrelevant pages
- Pages with traffic or backlinks deleted because they "looked outdated"
- Title tags, meta descriptions, headings and structured data not carried over
- Internal links still pointing to old URLs, creating redirect chains
- A noindex tag or robots.txt block left over from staging
- A slower or JavaScript-heavy new site that search engines struggle to render
The good news is that every one of these is preventable with a disciplined process.
Phase 1: Benchmark Before You Touch Anything
You can't protect what you haven't measured. Before design or development starts, capture a full baseline:
- A full crawl of the current site: every URL, status code, title, meta description, H1, canonical tag and internal link.
- Your top pages by organic traffic and conversions from Google Search Console and your analytics platform, ideally covering at least 12 months to account for seasonality.
- Pages with external backlinks. These carry authority from other sites and must never be lost.
- Keyword rankings for your most valuable terms.
- Performance data, including Core Web Vitals, so you can confirm the new site is at least as fast.
Store this snapshot somewhere safe. After launch, it's the only objective way to show what changed and why.
Phase 2: Decide What Happens to Every Piece of Content
Large sites accumulate years of pages: old campaigns, duplicate service pages, outdated news. A migration is the right moment to clean up, but decisions must be based on data, not on how a page looks.
| Decision | When to use it | What happens to the old URL |
|---|---|---|
| Keep | Page performs well and is still accurate | Same URL if possible, or a 301 redirect to the new URL |
| Merge | Several thin or overlapping pages cover the same topic | All old URLs redirect to the single, stronger combined page |
| Rewrite | Page has traffic or links but outdated content | Keep or redirect the URL; refresh the content |
| Retire | No traffic, no links, no business value | Return a 404 or 410, or redirect only if a genuinely relevant page exists |
Phase 3: Build the URL Map and Redirect Plan
The URL map is the single most important document in any migration. It lists every old URL that matters and its exact new destination.
- Redirect one-to-one wherever possible. Send each old page to the closest matching new page, not to the homepage.
- Use permanent (301) redirects for permanent moves. Google explains how it handles each redirect type in its guide to redirects and Google Search.
- Avoid redirect chains. Old URL A should go straight to new URL C, not via B.
- Use pattern rules carefully. Regular-expression redirects are efficient for large sections, but test them against your full URL list to catch unintended matches.
- Keep redirects in place long-term. Other sites, bookmarks and old emails will keep sending visitors to old URLs for years.
Phase 4: Preserve Every On-Page SEO Signal
A new design shouldn't mean new, untested SEO. For every kept or rewritten page, carry over or deliberately improve:
- Title tags and meta descriptions
- H1 and heading structure
- Body content, especially the sections that earn rankings
- Canonical tags, following Google's guidance on consolidating duplicate URLs
- Structured data such as Organization, Product, FAQ and Article markup
- Hreflang tags for international and multi-language sites
- Image alt text and descriptive file names
- Internal links, updated to point directly at new URLs
Phase 5: Test Staging the Way Search Engines See It
Your staging site should be protected from indexing with a password or noindex, but it should still be tested as if it were live:
- Crawl staging and compare it with the Phase 1 baseline: missing pages, changed titles, broken links, unexpected noindex tags.
- Test every redirect in the URL map automatically and confirm each returns a single 301 to the right destination.
- Check rendering. If the new site relies on JavaScript, confirm that important content and links appear in the rendered HTML.
- Measure performance on key templates and compare with the old site.
- Review accessibility and mobile layouts for the highest-traffic templates.
This is the same staging-and-QA discipline I use on every project, described in my delivery process and in detail in From Brief to Launch: My 5-Phase Delivery Process.
Phase 6: Launch Day Checklist
| Check | Why it matters | How to verify |
|---|---|---|
| Remove staging noindex and password | Otherwise the new site can drop out of search results | Inspect page source and robots.txt on live pages |
| Deploy and test all redirects | Protects rankings and backlinks of old URLs | Run the full URL map through a redirect checker |
| Submit the new XML sitemap | Helps search engines discover new URLs quickly | Submit in Search Console; see Google's sitemaps overview |
| Verify analytics and conversion tracking | Without it, you can't measure the migration's impact | Test key goals and events in real time |
| Spot-check top pages | Your most valuable pages deserve a manual review | Review titles, content, canonicals and structured data |
If the migration also changes your domain, follow Google's guidance for a site move with URL changes and use the Change of Address tool in Search Console.
Phase 7: Monitor for 90 Days
Some ranking fluctuation after a large migration is normal while search engines re-crawl and re-evaluate the site. What matters is spotting real problems quickly:
- Daily for the first two weeks: crawl errors, 404s and indexing reports in Search Console.
- Weekly: organic traffic and conversions for the top pages from your baseline, compared page by page.
- Ongoing: rankings for priority keywords, Core Web Vitals and any new redirect chains.
When a page underperforms, check it against the baseline: Did the redirect work? Did content or internal links disappear? Most issues can be traced and fixed within days.
Enterprise-Specific Risks to Plan For
- Many stakeholders, many sections. Product, regional and legal teams each own content. Assign a named owner to each section of the URL map.
- International sites. Hreflang, regional redirects and country-specific content multiply the complexity. Migrate one market at a time if you can.
- Legacy integrations. Store locators, product feeds and gated resources often have their own URLs that get forgotten. Inventory them early.
- Governance after launch. Without rules, a large site drifts back into duplicate pages within a year. Agree on URL conventions and content ownership up front.
- Phased rollouts. Migrating section by section or region by region reduces risk and makes problems easier to isolate.
For Mid-Sized and Smaller Sites
The same steps apply to a 50-page site, just faster. Export your top pages from Search Console, map every URL that gets traffic or links, set up 301 redirects, carry over titles and descriptions, and watch Search Console closely after launch. Whether you're moving to WordPress, Webflow or a custom build, the platform choice matters far less than the migration discipline. If you're still choosing, see WordPress vs Webflow vs Shopify.
The Bottom Line
A migration doesn't have to cost you rankings. Benchmark first, decide deliberately what happens to every page, map and test every redirect, preserve on-page signals, and monitor closely after launch. Done that way, a migration becomes a chance to grow organic traffic, not just protect it. You can see examples of large redesigns and rebuilds in my work, and if you're planning a migration or replatforming project, let's review your plan together before launch day.
Frequently Asked Questions
Will I lose SEO rankings when I redesign my website?
Not if the migration is planned properly. Rankings usually drop because of missing redirects, removed content or lost on-page signals. With a URL map, tested 301 redirects and preserved metadata, most sites see only short-term fluctuation and then hold or improve their positions.
How long does it take for rankings to recover after a website migration?
For a well-executed migration, search engines typically re-crawl and settle within a few weeks, though very large sites can take longer. If traffic is still significantly down after a couple of months, something specific is usually broken and should be investigated page by page.
Should I redirect all old pages to my homepage?
No. Redirect each old page to the most relevant new page. Mass redirects to the homepage can be treated as soft 404s, which means the value of those pages isn't transferred. If no relevant page exists, a proper 404 or 410 is the better choice.
How long should I keep 301 redirects in place?
As long as possible, ideally permanently. Backlinks from other websites, bookmarks and old emails keep sending visitors to old URLs for years, and removing redirects throws that traffic and authority away.
Do I need to tell Google that my website has moved?
If your domain changes, use the Change of Address tool in Google Search Console alongside 301 redirects. If only URLs change on the same domain, redirects plus an updated XML sitemap submitted in Search Console are usually enough.
What is the biggest mistake companies make during a website migration?
Treating SEO as a post-launch task. The most damaging problems, such as missing redirects, deleted high-value pages and leftover noindex tags, are all decided before launch. Building the URL map and SEO checks into the project plan from day one prevents nearly all of them.