SEO Migration Strategy: A Step-by-Step Plan That Keeps Rankings

What an SEO migration is

An SEO migration is any website change that can move, rename or remove URLs that already rank: a new domain, a move to HTTPS, a new URL structure, a new platform, or two sites merged into one. Search engines do not care about your launch date. They care whether every old URL still leads somewhere useful, whether the new pages carry the same content and signals that earned the rankings, and whether they can crawl the new site. A migration strategy answers those three questions before launch, not after traffic falls.

Google's guidance sets the tone: change only one thing at a time, split a large move into smaller steps where you can, and expect temporary fluctuation during the move. A redesign, a domain change and a URL restructure launched together hide which change caused a drop.

Step 1: Decide what kind of move this is

Google separates moves into two kinds, and the work follows from the answer. A move with URL changes covers domain changes, HTTP-to-HTTPS moves, changed paths and domain consolidations. A move without URL changes covers a hosting change or a move to a CDN where every visible URL stays the same. The second kind has no redirect map, because there is nothing to redirect, but it still needs a crawl and performance check.

Write the answer down in one sentence before you plan anything else. For example: "This is a domain change from oldsite.com to newsite.com, with the same URL paths." That sentence decides whether you need a redirect map, the Change of Address tool, or both.

Step 2: Inventory the old site before you touch it

You cannot protect what you have not listed. Build the inventory at least two weeks before launch, so you have a baseline.

1. Crawl the live site and export every URL, its status code, its title, its canonical tag and its internal links.
2. Export the sitemap and compare it with the crawl. Pages in the sitemap but missing from the crawl, and pages found by the crawl but missing from the sitemap, both need attention.
3. Pull Search Console data for the last 90 days: which pages get impressions and clicks, which queries bring them, and which pages have indexing errors.
4. Pull analytics data for the same period: sessions, conversions and revenue by landing page, so you know which pages pay for the site.
5. List every backlink you can find, and note the pages other sites link to most. Those pages matter even if their own traffic is low.
6. Record server logs for a week if you can. Logs show URLs that real visitors and crawlers request, including old pages that no longer appear in your sitemap.

Save it all in one dated folder. It becomes the redirect map and the testing list.

Step 3: Build the redirect map, one URL to one page

The redirect map is a table with one row per old URL. Each row has the old URL, the new URL, the redirect type and a note on why that destination was chosen. Map every valuable old URL to its closest new equivalent. A blog post about pricing goes to the new pricing post, not to the blog home page. A discontinued product goes to the closest current product, or to its category page if no close match exists.

Google warns against redirecting many old URLs to one irrelevant destination, such as the home page. That wastes the ranking signals those pages earned. Consolidating several old pages into one related new page is fine, and the map should say so.

A page with no traffic, no links and no indexation can return a 404. Decide that deliberately, row by row, rather than by accident on launch day.

Step 4: Prepare the new site and test it before launch

Test the new site on a staging address that search engines cannot reach. Check that every page in the map exists, that titles and headings match the old pages, and that the content a page ranked for is still on the page.

Check these basics on staging:

• The new site has a valid TLS certificate if it moves to HTTPS.
• The robots.txt file on the new site allows crawling of the pages you want indexed.
• Internal links point to new URLs, not old ones that then redirect.
• Canonical tags point to the new URLs.
• Structured data, hreflang and pagination tags, if you use them, match the new addresses.

Crawl staging and compare it with the old-site inventory. Every page that should exist must return a 200 status code, and every page that should not exist must return a 404.

Step 5: Launch the redirects, then tell Google

Launch day has a fixed order. First, put the new site live. Second, turn on the redirects. Use server-side permanent redirects, 301 or 308, wherever possible, and point each old URL directly at its final destination. Avoid chains, where an old URL redirects to an intermediate URL that redirects again. Google can follow up to 10 hops, but its guidance is to redirect straight to the final page.

Third, submit the new XML sitemap in Search Console, and keep the old sitemap available so you can watch the old URLs drop out of the index. Fourth, if the move changes the domain or subdomain, submit a Change of Address in Search Console from the old property. You do not need that tool for an HTTP-to-HTTPS move, a www change, or a path change within the same domain.

Fifth, update the links you control: internal links, social profiles, email templates and listings you manage. External links will keep pointing at old URLs for months, which is why the redirects stay up for at least a year.

A worked example: a 240-page site moves domains

A small business site has 240 indexed pages and moves from oldsite.com to newsite.com with the same URL paths. The inventory shows 38 pages bring 80 percent of organic clicks, and 12 of those are product pages that also earn most of the site's backlinks.

The team maps all 240 URLs one to one, because the paths do not change, and adds 301 redirects for the whole domain. They keep the page titles and headings identical on the new site and move the content unchanged. They submit the new sitemap on launch day and the Change of Address the same morning.

In the first week, Search Console shows the old URLs falling and the new URLs rising, with a dip in clicks of about a fifth for three days. By week four, clicks are back to the pre-move level, and by week six the new URLs carry the old rankings. The team keeps the redirects live for the full year.

The example is illustrative, not a promise. A move that also redesigns pages or changes URL paths will take longer to settle.

The first six weeks after launch: what to check, and when

Keep a short log of what you checked. If rankings fall in week three, that log is the difference between a fast fix and a guessing game.

Common mistakes that cost rankings after a migration

• Redirecting everything to the home page. Google names this error directly in its guidance.
• Launching a redesign at the same time. Changing the design, the content and the URLs together hides the cause of any drop.
• Forgetting internal links. Links that still point at old URLs force every visitor and crawler through a redirect.
• Leaving the old site live without redirects. Two live copies of the same content split the ranking signals between them.
• Blocking the new site in robots.txt. A staging robots.txt file copied to the live site by mistake can remove the whole site from search in a day.
• Removing redirects too early. A redirect removed after three months breaks every external link that still points at the old URL.
• Not checking the sitemap. A new sitemap that lists old URLs, or misses new ones, sends Google the wrong map of the site.

Your pre-launch checklist

• [ ] Inventory exported: crawl, sitemap, Search Console, analytics and backlinks.
• [ ] Redirect map complete: one row per old URL, with a named destination.
• [ ] New site tested on staging: every mapped page returns 200, titles and content preserved.
• [ ] Internal links and canonical tags updated to new URLs.
• [ ] Robots.txt and TLS certificate checked on the new site.
• [ ] Launch order written down: new site live, redirects on, sitemaps submitted, Change of Address filed if needed.
• [ ] Monitoring plan set: who checks Search Console each day, and what counts as a problem.
• [ ] Redirects scheduled to stay live for at least a year, with the date written in the calendar.

Where to go next

Before you start, read the comparison of Google Search Console vs Google Analytics so you know which tool shows the migration and which shows the traffic that follows it, and the guide to how to monitor website traffic for the baseline numbers your inventory needs. If the move follows a redesign, the product landing page guide covers the page-level checks that keep conversions intact. Adziq's SEO service page describes how this work is run for a client, and the signs your Google Ads are wasting money guide is worth reading if paid traffic has to carry the site while organic traffic settles.

Common questions

Sources

• Site moves and migrations (Google Search Central)
• About Search Console (Google Search Console Help)

Adziq sells marketing services and does not accept payment for placement in its articles. See our editorial policy.