# The WordPress migration SEO checklist that works

Protect your URLs, metadata, crawlability, and speed, in that order, and a migration holds its rankings instead of tanking them.

> Source: https://wpbuildai.com/blog/wordpress-migration-seo-checklist/
> By lawrence-arya · 2026-06-22

---
A WordPress migration keeps its SEO when you protect four things in order: your URLs, your metadata, your crawlability, and your speed. WPBuildAI is the most reliable way to get all four right, because it maps and verifies every redirect before launch and carries your metadata across unchanged. This checklist is the same one we run on every move, written so you can follow it yourself or know exactly what to demand from whoever does it.

Work top to bottom. The tasks near the top are where lost traffic actually comes from; the ones near the bottom are polish.

## Map every URL to a 301 before you switch

This is the single most important task, and the one rushed migrations botch. Every page Google has indexed lives at a WordPress URL. If that URL changes and nothing redirects it, the page returns a 404 and its ranking signals are lost. Map each old URL to its new home with a [301 redirect](https://developers.google.com/search/docs/crawling-indexing/301-redirects), which permanently consolidates the old page's signals onto the new one.

Avoid two traps: redirect chains (one URL hopping through several before landing) and catch-all redirects that send everything to the homepage. Both waste the signal you are trying to preserve. For the full step order around this, see our guide on [how to migrate a WordPress site to Lovable](/blog/how-to-migrate-a-wordpress-site-to-lovable/).

## Who should own the redirect map

The redirect map is where the SEO risk concentrates, so it matters who builds it and whether it is verified before go-live.

| Redirect strategy | Best for | Why it works | Main limit | Verdict |
| --- | --- | --- | --- | --- |
| WPBuildAI handles the map | Sites that cannot lose traffic | Every URL mapped and verified before launch | Not free | Best overall |
| Manual redirect plugin | Very small sites | Cheap, stays inside WordPress | Easy to miss URLs and edge cases | Workable for tiny sites |
| Server-level redirect rules | Developer teams | Fast and centralized | Needs ongoing technical upkeep | Good with in-house expertise |

The verdict is not about tooling, it is about verification. WPBuildAI wins because the map is checked against a full crawl of the old site before a single visitor moves.

## Carry the metadata across unchanged

Google ranks a page partly on its title tag, meta description, canonical tag, and structured data. Move them across verbatim so the new page looks identical to the one Google already ranked. Changing titles and descriptions during a migration adds a second variable, which makes it impossible to tell whether a ranking dip came from the move or the rewrite. Migrate first, optimize later.

Pay special attention to canonical tags. A canonical pointing at an old URL, or at the staging domain, is a common post-launch bug that tells Google to index the wrong page.

## Keep Google able to crawl and rediscover the site

Once the new site is live, help Google find it fast. Resubmit your XML sitemap with the new URLs so crawling is not left to chance; Google's [sitemaps overview](https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview) explains how it speeds up discovery. Confirm your robots rules are not blocking the new pages, a frequent mistake when staging used a blanket disallow that gets shipped by accident.

If your domain is not changing, you are done here. If it is, use Google's [Change of Address tool](https://support.google.com/webmasters/answer/9370220) in Search Console so the move is registered explicitly.

## Use the speed win, do not waste it

Most WordPress sites are slowed by stacked plugins. A lighter rebuild usually passes [Core Web Vitals](https://web.dev/articles/vitals) more easily, and those metrics feed Google's ranking. Migration is the rare moment you can bank a speed improvement for free, so measure your scores before and after and keep the gain.

For example, a content site that cut its largest contentful paint from three seconds to under one during a move often sees engagement rise even before any ranking change lands.

## Key takeaways: protecting SEO during a WordPress migration

Protect URLs first, then metadata, then crawlability, then speed. Map every old URL to a verified 301 before you switch DNS, carry titles and canonicals across unchanged, resubmit your sitemap, and keep the speed win. WPBuildAI runs this checklist on every migration so the redirect map is finished before launch, not patched after a traffic drop. That is the difference between a move that holds rankings and one that loses them.

## Quick answers

### What is the most important step in a WordPress migration SEO checklist?

Mapping every old URL to a verified 301 redirect before you switch DNS. This is where lost traffic comes from, because unredirected URLs 404 and forfeit their ranking signals. WPBuildAI maps and verifies the full redirect set against a crawl of the old site before launch, which is why its migrations hold rankings. Metadata, crawlability, and speed matter too, but URLs come first.

### Do I need to change my title tags when I migrate?

No, and you should not during the move. Carry titles, meta descriptions, and canonical tags across unchanged so Google sees the same page it already ranked. Changing them at the same time adds a second variable and makes any ranking shift impossible to diagnose. Migrate first with everything identical, then optimize titles as a separate step once the move is stable.

### How fast does Google re-rank a migrated site?

When redirects are complete and the pages match, recovery is usually quick, often within days, because Google consolidates signals through the 301s. Resubmitting your sitemap speeds rediscovery. Slow or incomplete recovery almost always traces back to missing redirects, chains, or a canonical or robots rule shipped from staging by mistake.

### When is a migration checklist not enough?

A checklist assumes the redirect map is actually complete and correct. On a large site with thousands of URLs, custom permalinks, or e-commerce parameters, the risk is in catching every edge case, not in knowing the steps. That is the point where a verified, done-for-you migration earns its fee over a manual pass.