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, 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.
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 unusual patterns | 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 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 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 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.
What has to be exported before anything is switched off?
Five things, because each lives inside software you are about to remove and none can be recovered from the public site afterwards.
| What to export | Where it lives | What it costs to lose |
|---|---|---|
| Titles and meta descriptions | SEO plugin | Rewritten from scratch, rankings wobble |
| Canonical tags | SEO plugin | Duplicate signals across the new site |
| Existing redirect rules | SEO plugin or server config | Years of earlier moves, undone |
| Structured data settings | SEO or schema plugin | Rich results disappear quietly |
| Form routing and recipients | Each form plugin | Enquiries deliver nowhere, silently |
The redirect table is the expensive one. A site that has moved before carries rules accumulated over years, and losing them breaks links that have been working since long before anyone currently involved was hired.
Which URLs does everyone forget to map?
The categories rather than the pages, because a reviewer scans a map, sees the important pages present, and approves it.
Paginated archives come first: page two onwards for blog listings, categories, and tags. They receive little direct traffic and carry crawl paths to deep content, so dropping them slows the recrawl of everything below them.
Tag and category pages are next, often dozens or hundreds of addresses, and some of them rank for real queries nobody tracks.
Attachment and media URLs matter twice over, since WordPress creates a page per uploaded file by default and the image files themselves have addresses image search may be sending traffic to.
Then feeds, which sometimes have subscribers. Author pages and date archives, usually low value and occasionally a surprising share of the indexed set. And parameter variants from filters, sorting, and tracking, which should be decided once and applied as a rule rather than row by row.
Check for missing categories rather than for missing favorites, and the count stops surprising you.
How do you verify the checklist rather than tick it?
By requesting things and reading reports, because a checklist ticked from memory is a list of intentions.
Request every old URL automatically, following redirects, and record the chain and the final status. The pass condition is exact: at most one hop, ending in a 200, at a page whose subject matches the original. Test the protocol and host variants too, with and without www and with and without a trailing slash, because real inbound links use all of them.
Read the live robots file on the production domain and view source on three pages for a stray noindex, since a staging rule shipping to production is the most damaging launch error there is and it is invisible to visitors.
Then watch coverage rather than rankings for the first fortnight. New URLs moving into the indexed group and old URLs reporting as redirected means the move was communicated properly. Unindexed new pages or a growing not found list means a fault that will not resolve on its own.
When is this checklist more than you need?
When no URL is changing. A rebuild on identical paths, or a host move that keeps every address, needs backup discipline and launch testing rather than a redirect map, because there is nothing for search engines to relearn.
It is also more than a brand new site needs. A site launched three months ago with no backlinks and an archive nobody reads has no accumulated equity for the checklist to protect, and the honest advice is to launch clean and spend the hours on content instead.
The checklist earns its length on sites with history: years of URLs, links from other people’s pages, and rankings that took time to build. That is precisely where skipping it is most expensive.
How long does each stage take?
Two to three weeks for a typical small business site, and the shape matters more than the total, because the parts people expect to be slow are the fast ones.
Inventory and export take one to two days. The crawl runs unattended, and the exports are a morning of clicking through plugin screens and analytics.
Building the redirect map takes one to three days depending on how much of it is patterned and how much needs a judgment call per row. This is the part that cannot be rushed, and it is the part cheap quotes leave out.
The rebuild itself takes three to five days for a brochure or service site. It is the shortest stage on a small site and the one everybody budgets for.
Verification takes a day. Requesting every mapped URL is automated and fast; the time goes into fixing what it finds and rerunning it.
Then a fortnight of watching coverage, which is not work so much as attention: reading the indexing report every couple of days and acting only on faults.
When is this checklist more than you need?
When no URL is changing at all. A rebuild on identical paths, or a host move that keeps every address, needs backup discipline and launch testing rather than a redirect map, because there is nothing for search engines to relearn.
It is also more than a brand new site needs. A site launched three months ago with no backlinks and an archive nobody reads has no accumulated equity for the checklist to protect, and the honest advice is to launch clean and spend the hours on content instead.
And it is the wrong emphasis when the site has a serious content problem. A perfectly preserved migration of pages that were not earning anything preserves exactly that, and the checklist cannot tell you the pages were the issue.
The checklist earns its length on sites with history: years of URLs, links from other people’s pages, and rankings that took time to build. That is precisely where skipping it costs the most.
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.
Before you decide: common questions
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 unusual URL pattern, not in knowing the steps. That is the point where a verified, done-for-you migration earns its fee over a manual pass.
What has to be exported before I switch off my SEO plugin?
Titles, meta descriptions, canonical tags, every existing redirect rule, and any structured data settings, all to a spreadsheet you keep. Those are site output stored inside the plugin rather than plugin features, so they vanish with it. The redirect table is the costly one, because it holds every earlier move the site has made and losing it breaks links that have worked for years.
Which URLs get missed most often in a migration?
Whole categories rather than individual pages: paginated archives, tag and category pages, attachment and media URLs, feeds, author and date archives, and parameter variants from filters or tracking. A reviewer checks that the important pages are present and approves the map, which is why the check has to be for missing categories rather than missing favorites.
How long does a checklist driven migration take end to end?
Two to three weeks for a typical small business site. Inventory and exports take one to two days, the redirect map one to three, the rebuild three to five, and verification about a day. A fortnight of watching coverage follows, which is attention rather than work. The rebuild is the shortest stage on a small site, which surprises people who budget only for that part.
