Website Migration Without Losing Rankings: A Step-by-Step Guide

Website migrations are high-stakes projects. Done poorly, years of SEO work can be lost overnight. Done well, you preserve existing rankings while gaining the benefits of your new platform.

This guide covers the essential steps to migrate your website without destroying your search visibility. Proper migration is a critical part of web development.

Why Migrations Go Wrong

Common Migration Disasters

Missing redirects: Old URLs return 404 errors. All links pointing to those URLs become worthless. Search engines remove pages from the index.

Changed content structure: New site organises content differently without redirects. Internal links break. Topic authority is disrupted.

Technical SEO regression: New platform has worse technical SEO. Meta tags, structured data, canonical tags, or other elements are misconfigured.

Performance degradation: New site is slower than the old one. Core Web Vitals decline. Rankings suffer.

Content changes during migration: Copy rewriting during migration confuses what caused ranking changes. Were rankings lost due to migration issues or content changes?

The Stakes

Traffic losses from migration mistakes can be:

Immediate and dramatic
Slow and gradual
Difficult to diagnose
Hard to recover

Some sites never fully recover from botched migrations. Proper planning prevents this.

Types of Website Migrations

Different migrations carry different risks:

Platform Migration

Moving from one CMS to another (WordPress to Webflow, Shopify to BigCommerce, etc.)

Risks: URL structure changes, template changes, feature differences Complexity: Moderate to high

Domain Migration

Moving to a new domain name (oldbusiness.com.au to newbusiness.com.au)

Risks: Domain authority transfer, brand recognition, backlink value Complexity: High

HTTP to HTTPS

Adding SSL certificate (http:// to https://)

Risks: Mixed content, improper redirects Complexity: Low to moderate (should be straightforward with proper handling)

Site Redesign

Visual and structural changes within the same platform

Risks: Content removal, URL changes, navigation restructuring Complexity: Moderate

Consolidation

Merging multiple sites into one

Risks: Content canonicalisation, redirect complexity, signal confusion Complexity: High

Pre-Migration Phase

Complete Site Audit

Before migrating, document everything about your current site:

Crawl the site: Use Screaming Frog, Sitebulb, or similar tools to create a complete list of URLs.

Document URL structure: Every page that exists, its URL, and its purpose.

Capture analytics data: Baseline traffic, top pages, conversion data. You need this for comparison.

Record current rankings: Track rankings for important keywords before migration.

Inventory content: What pages exist? What content is on each page?

Document technical elements: Title tags, meta descriptions, heading structure, schema markup, canonical tags.

Identify High-Value Pages

Not all pages are equal. Identify pages that:

Receive significant organic traffic
Rank for important keywords
Have valuable backlinks pointing to them
Drive conversions

These pages require extra care during migration.

Create Redirect Map

Before building the new site, plan redirects:

Map old URLs to new URLs: Every old URL should map to a corresponding new URL or an appropriate alternative.

One-to-one where possible: Redirect old pages to equivalent new pages.

Redirect to relevant alternatives: If a page is being removed, redirect to the most relevant remaining page.

Avoid redirect chains: Old URL should redirect directly to new URL, not through intermediary pages.

Export this as a spreadsheet:

Old URL	New URL	Redirect Type	Notes
/services/plumbing/	/services/plumber/	301
/blog/old-post/	/blog/new-post/	301	Renamed
/team/old-member/	/about/	301	Person left

Stakeholder Communication

Ensure everyone understands:

What is happening
When it is happening
Expected temporary impacts
Who is responsible for what

Migrations often fail due to miscommunication, not technical issues.

Building the New Site

URL Structure Decisions

Keep URLs where possible: If old URLs can work on the new platform, keep them. Fewer redirects means less risk.

If changing URLs, improve them: Make new URLs logical, keyword-relevant, and future-proof.

Maintain hierarchy: If /services/ was a category page, keep that structure.

Technical SEO Parity

The new site must match or exceed the old site technically:

Title tags and meta descriptions: Transfer existing optimised tags. Do not rely on default templates.

Heading structure: H1s, H2s, etc. should reflect old site structure.

Schema markup: Implement structured data matching the old site.

Canonical tags: Properly implemented on all pages.

Robots.txt: Review and update for new URL structure.

XML sitemap: Generate new sitemap with all new URLs.

Content Transfer

Transfer content carefully:

All text content should move to appropriate pages
Images should be migrated with proper alt text
Internal links need updating to new URLs
Video and other media should transfer

Staging Environment Testing

Test thoroughly before going live:

Crawl the staging site: Look for broken links, missing pages, redirect issues.

Compare page-by-page: High-value pages should have equivalent or better content.

Technical checks: Page speed, mobile friendliness, meta tags, structured data.

Redirect testing: Test sample redirects from your map.

Functionality testing: Forms, e-commerce, interactive features.

Migration Day

Timing

Choose timing carefully:

Avoid high-traffic periods
Avoid Fridays (weekend debugging is painful)
Morning is usually better (full day for issue resolution)
Consider seasonal factors

Execution Steps

Put the old site into maintenance mode (optional, reduces complexity)
Deploy the new site
Implement all redirects
Update DNS if changing domains
Update internal links if any still point to old URLs
Update Google Search Console (add new property if domain changed)
Submit new XML sitemap
Test critical user paths
Monitor for errors

Redirect Implementation

301 redirects are essential:

Server-level redirects are most reliable
Implement via .htaccess (Apache), nginx config, or hosting panel
Plugin-based redirects are fallback option
Test redirects are working correctly

Every old URL that received traffic or has backlinks must redirect properly.

Post-Migration Monitoring

Immediate Checks (First 24-48 Hours)

Crawl the live site: Identify any 404s, redirect loops, or unexpected issues.

Check Google Search Console: Look for crawl errors, coverage issues.

Monitor real traffic: Is the site receiving expected traffic levels?

Test key conversions: Are forms working? Can users complete purchases?

Check redirects: Test sample redirects from various sources.

First Week

Index coverage: Are new URLs being indexed? Are old URLs being dropped?

Traffic patterns: Compare to baseline. Some fluctuation is normal.

Ranking monitoring: Track key keywords for changes.

Error logs: Review server logs for issues.

User feedback: Are users reporting problems?

First Month

Index status: Most old URLs should redirect and be dropped from index. New URLs should be indexed.

Ranking recovery: Initial ranking volatility should stabilise.

Traffic comparison: Should be approaching pre-migration levels.

Backlink status: Check that important backlinks are working via redirects.

Ongoing

Maintain redirects: Keep redirects in place for at least one year, preferably permanently.

Monitor for issues: New crawl errors, ranking problems, traffic drops.

Document lessons: What went well? What could improve for future migrations?

Common Migration Issues and Solutions

Traffic Drop After Migration

Diagnose first: Is it technical or content-related?

Check:

Are pages indexed?
Are redirects working?
Are there technical SEO issues?
Did content change significantly?

Action: Fix identified issues. Google may take weeks to re-evaluate.

404 Errors in Search Console

Old URLs returning 404 means redirects are missing or broken.

Action: Identify missing redirects from URL list. Implement immediately.

Slow Indexing

Google is slow to index new URLs or drop old ones.

Action:

Ensure sitemap is submitted
Request indexing for key pages
Build internal links to new pages
Be patient (can take weeks)

Redirect Loops

Page A redirects to Page B, which redirects back to A.

Action: Map all redirects and identify loops. Fix redirect rules.

Mixed Content Warnings

HTTPS pages loading HTTP resources.

Action: Update all internal references to HTTPS. Check images, scripts, stylesheets.

Special Considerations

E-commerce Migrations

E-commerce adds complexity:

Product URLs must redirect properly
Category structure matters for SEO
Out-of-stock products need handling
Checkout process must work flawlessly

Test extensively before going live.

Large Site Migrations

Sites with thousands of pages require:

Automated redirect rules where possible
Pattern-based redirects
Prioritisation of high-value pages
Acceptance that some pages may break

Domain Migrations

Moving to a new domain requires extra steps:

Verify both domains in Search Console
Use Change of Address tool
Expect longer recovery period
Maintain old domain redirects indefinitely

International Sites

Multi-language or multi-region sites need:

Hreflang tag updates
Regional URL handling
International Search Console properties

Migration Checklist Summary

Pre-Migration:

Building New Site:

Technical SEO elements implemented
Content transferred
Internal links updated
Staging testing completed

Migration Day:

Post-Migration:

When to Get Help

Consider professional support if:

Large site with many URLs
Domain migration
Significant revenue at stake
Limited technical expertise
Complex platform requirements
International or multi-language sites

The cost of professional help is often less than the cost of lost traffic from a botched migration.

The Bottom Line

Website migrations are manageable with proper planning. The key is:

Document everything before starting
Plan redirects thoroughly
Test extensively before going live
Monitor closely after launch
Fix issues immediately

Most migration problems come from skipped steps, not inherent difficulty.

Planning a website migration? Platform21 has migrated dozens of sites while preserving and improving search rankings. Get in touch or explore our web development to discuss your migration project.

Related Articles: