Migrating WordPress without losing your SEO
A platform migration is the easiest way to undo years of search equity in an afternoon. Here is the process I use to move WordPress sites — to a rebuild, a new host, or headless — without the rankings tanking.
Most migration disasters are not caused by the new site being worse. They are caused by URLs changing silently, redirects being forgotten, and content quietly disappearing. The good news is that every one of those failure modes is preventable with a dull, methodical process.
Map every URL before you write a line of code
The first deliverable on any migration is a URL inventory — every indexable address on the old site, where it is going on the new one, and what its redirect status will be. Crawl the old site, export it, and work from that spreadsheet religiously. If a page exists today, it must have a destination tomorrow: either a one-to-one match, a redirect to a relevant replacement, or a deliberate decision to retire it with a 410.
This is the unglamorous part nobody sees, and it is the single biggest thing that protects rankings.
Preserve the signals that matter
URLs are only the start. Title tags, meta descriptions, headings, internal links, image alt text, and structured data all carry weight, and all of them are easy to lose in a rebuild. Carry the important ones across deliberately rather than regenerating them and hoping for the best.
XML sitemaps and robots rules should be ready on day one of the new site, not added in week two. And if you are moving to headless, make sure your metadata is genuinely rendered server-side — a client-rendered title tag is no tag at all, as far as some crawlers are concerned.
Redirects, then watch
Implement redirects before the new site goes live, not after. Use 301s for permanent moves, chain them as little as possible, and keep the old sitemap around for a while so you can spot anything that slipped through. Then watch the search console like a hawk for the first few weeks — crawl errors, dropped impressions, and coverage reports will tell you fast if something is wrong.
Done this way, a migration is rarely the scary event people fear. The sites I have moved this way have held their traffic through the cutover and grown afterwards — because the rebuild finally let them move, rather than spending their equity.
