---
title: "Site Migration SEO Checklist: Redirects, Indexing, Rollback"
url: https://hostmy.blog/site-migration-seo-checklist/
date: 2026-10-25
modified: 2026-10-26
lang: en
author: "Aditya Sharma"
description: "The search half of a WordPress migration: the URL map, the staging settings that sink launches, redirects, indexing and a rollback plan, built on Google's site move guide."
categories:
  - "WordPress"
image: https://hostmy.blog/wp-content/uploads/2026/10/hmb-card-2617-1024x538.jpg
word_count: 1564
---

# Site Migration SEO Checklist: Redirects, Indexing, Rollback

A site migration can lose search traffic without anything visibly breaking. The pages load, the design looks right, and weeks later the traffic chart has a step down in it. Often, the cause is something that was on nobody's list: redirects that were missed, a setting left over from staging, or a sitemap that still names the old addresses. This site migration SEO checklist walks through each of them.

This checklist is the search half of a migration. It does not cover the server or host steps, which are in [the WordPress migration checklist](/how-to-migrate-wordpress-site/). Everything here is built on Google's own documentation for site moves, and on the same lessons as the checklist we already publish. If you are moving platforms and not only hosts, the questions in [WordPress vs Squarespace for a blog that needs to earn](/wordpress-vs-squarespace-blog/) and [WordPress vs Wix for bloggers](/wordpress-vs-wix-blog/) apply first.

## What a move puts at risk

| Risk | What goes wrong | Where to look |
| ---- | --------------- | ------------- |
| URLs change with no redirect | Old addresses return 404 and their search traffic stops | The URL map and the redirect rules |
| Indexing blocks left on | A staging setting makes the new site invisible | Settings, robots.txt and response headers |
| Signals still point at the old site | Canonicals and internal links name the old addresses | The page source of the new site |
| Sitemap names the old URLs | Search engines are told to crawl pages that redirect | The sitemap and Search Console |
| The content itself changed | Titles and headings differ, so the page is not the same page | A before and after comparison |
| The server cannot cope | Crawling rises after a move and the site slows or errors | Server logs and response times |

None of these is exotic. A migration goes wrong when one of them is left to chance, and the list above is short enough to check each one on purpose.

## What Google says to expect

Google's [guide to site moves with URL changes](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) sets honest expectations. It says to expect temporary fluctuation in rankings during the move. For a medium-sized site, it can take a few weeks or more for Google to gradually start showing the new URLs. Googlebot has to visit every old and new URL at least once for the move to count as complete, and there is no fixed crawl schedule.

Two more points from the same page save people effort. The Change of Address tool in Search Console is only for moving to a new domain or subdomain. It is not needed for a switch from http to https, from www to non-www, or for path changes inside the same domain. And Google says to keep redirects in place for generally at least one year, so that signals can be passed on.

## Before the move: build the URL map

A URL map is a list of every old address and where it goes. Google's guide suggests building it from several sources, because no single one is complete: your sitemaps, your server logs, your analytics and your content management system. Include images, videos, scripts and stylesheets, since each one is a URL that something may link to.

`old URL | new URL | redirect type | status after launch | checked by
/best-coffee-grinders-2025/ | /best-coffee-grinders/ | 301 | 200 after one hop | name
/category/gear/ | /gear/ | 301 | 200 after one hop | name
/old-landing-page/ | (none) | 410 | 410 | name`

The simplest redirect is the one you do not need. If the URLs can stay the same, keep them. When they cannot, map each old URL to the page that best replaces it. Google says not to send many old URLs to one unrelated page, such as the new homepage, and the same logic applies to your readers. [How to safely change WordPress permalinks](/change-wordpress-permalinks/) covers the case where the structure itself is changing.

## The settings that sink launches

The most common migration failure is not a missing redirect. It is a setting carried over from the staging copy. A staging site is usually told to keep search engines out, and if that instruction travels to the live site, the new site is invisible.

| Left over from staging | How to spot it | Where it is |
| ---------------------- | -------------- | ----------- |
| Search engine visibility switched off | A noindex tag appears in the page source | Settings, Reading, in WordPress |
| A robots.txt that blocks everything | The file says Disallow: / | The robots.txt at the web root, or your SEO plugin |
| A noindex header | An X-Robots-Tag header on the response | The server configuration or a plugin |
| Canonicals pointing at staging | The canonical names the staging domain | Your SEO plugin, or a database value |
| A password or login wall | Crawlers receive a 401 or a login page | The host, or a maintenance plugin |

Three commands show most of this in seconds. Run them on the live site as soon as it is switched over.

`curl -s https://yourdomain.com/ | grep -io '<meta name="robots"[^>]*>'
curl -sI https://yourdomain.com/ | grep -i 'x-robots-tag'
curl -s https://yourdomain.com/robots.txt | head -20`

You want a robots tag that allows indexing, no X-Robots-Tag header that says otherwise, and a robots.txt that does not block the whole site. [WordPress robots.txt: what to allow, block and test](/wordpress-robots-txt/) explains how to read the third result.

## Redirects and how to test them

Google recommends server-side permanent redirects, a 301 or 308, and says client-side redirects are a last resort. Redirect each old URL directly to its final destination, because chains slow the page down and make the path harder to follow. Where to put them, in a plugin or in the server, is the subject of [WordPress redirect plugin or server rule: which to use](/wordpress-redirect-plugin-or-server-rule/).

Test them from a list, not from memory. This reads a file of old URLs and prints the status code and the place each one points.

`while read u; do curl -sI -o /dev/null -w "%{http_code} %{redirect_url} $u\n" "$u"; done < old-urls.txt`

Every line should show a 301 or 308 and a destination from your map. A 200 on an old address means no redirect exists. A 404 means the page was lost. Fix those before anything else, because they are the ones that cost traffic.

## Tell search engines about the new site

Submit the new sitemap. Google's guide says removing the old one is optional, and its advice for monitoring a move is to keep both submitted for a while. Check that the new sitemap lists only the new addresses, and that none of them redirect. In Search Console, watch the Page indexing report and the sitemap report in the days after launch. A rise in pages that are discovered but not indexed is normal at first, and a rise in errors is not.

Keep an eye on the server too. Google notes that it temporarily crawls more heavily after a migration, so check that the new host has room for it. Your access log shows Googlebot's visits and the status codes it received, and [reading your server log by hand](/read-server-log-ai-crawlers/) shows the method.

## A rollback plan

A rollback plan is a decision made before launch, when you are calm, about what you will do if the move goes badly. Write down three things: what counts as bad, who decides, and what you will do.

Pick signals you can measure for what counts as bad. One is the share of your top pages returning errors. Another is a robots or noindex setting that cannot be fixed within an hour. A third is the site failing under load. Keep the old site intact until the new one has been checked, and keep a full backup you have tested, as in [the WordPress backup that did not restore](/wordpress-backup/). If the decision is to roll back, the usual step is to point the domain back at the old site and switch the new redirects off. Decide who does that, and make sure they have the access.

## Do not change everything at once

A redesign, a change of URLs and a rewrite of the content in the same week make any drop impossible to explain. If traffic falls, you will not know which change caused it. Where you can, change one thing at a time. The reasoning is the same as updating plugins one major version at a time, which is set out in [what a WordPress maintenance month actually contains](/wordpress-maintenance-service/).

## After launch: the first month

`Day 1: robots tag, headers, robots.txt, and a sample of old URLs redirecting
Day 3: new sitemap submitted, old one kept for now, errors in the Page indexing report
Week 1: server log for Googlebot, status codes, response times
Week 2: top pages indexed and returning 200, internal links pointing at new URLs
Week 4: traffic compared with the same weeks before, redirects still in place
Month 12: redirects reviewed, not removed early`

The last line is a reminder, not a task for now. Google's guidance is to keep redirects for at least a year, so do not remove them just because traffic looks settled.

Last checked against Google's documentation in October 2026. Guidance on site moves can change, so read the linked guide again before a real move.

## Where Host My Blog fits

The checklist above is free and works whoever does the move. When we take on a blog, the same questions come first, and they are part of [what we check before taking on a client blog](/what-we-check-before-taking-a-client-blog/). If you would rather have someone else own the list on moving day, [our care for bloggers](/for-bloggers/) is built for that.

If your site moved tomorrow, which of the six risks in the first table could you check today?