Migrating off WordPress without losing your SEO

Every serious WordPress migration runs into the same wall of fear: if we get this wrong, we lose the rankings we spent years building. It’s a rational fear. A site that’s been indexed for a decade carries enormous search equity: equity that lives in URLs, redirects, internal links, and structured data that a careless migration quietly destroys. Get it wrong and you don’t just ship a new website; you reset your traffic to zero.

The good news is that ranking loss in a migration is almost never inevitable. It’s the result of specific, avoidable mistakes. Here’s how we avoid them.

SEO equity is mostly about URLs

Search engines rank pages, identified by URLs. The number one cause of post-migration ranking collapse is changing those URLs without telling Google where the content went.

Before touching anything, we export a complete map of every indexed URL on the existing site, every post, page, category, tag, author archive, and paginated list. The source of truth isn’t the CMS; it’s reality. We pull from the live sitemap, from Google Search Console’s indexed-pages report, and from a full crawl. Anything that gets organic traffic or has backlinks pointing at it goes on the list.

For each old URL, we make a deliberate decision:

• Keep the same path. The safest option. If the new site can serve /2019/the-best-way-to-age-a-cigar/ at the same address, do it.
• 301 redirect. If the structure has to change, a permanent redirect tells Google the page moved and passes the ranking signal along. One-to-one redirects, never a blanket redirect to the homepage.
• Retire intentionally. Thin or duplicate pages can be dropped, but that’s a decision, not an accident.

The deliverable is a redirect map: every old URL paired with its new home. This is the document the whole migration hangs on.

Preserve the metadata, not just the words

Content isn’t only body text. Each page carries a title tag, meta description, canonical URL, Open Graph data, and often structured data (Article, Breadcrumb, FAQ). All of it influences how the page appears and ranks. A migration that copies the prose but regenerates titles and drops schema is throwing away signal.

We carry it over deliberately: titles and descriptions migrate with the content, canonicals point to the new URLs, and structured data is rebuilt to match, often better than the original, because a modern stack makes per-page JSON-LD trivial.

Don’t cut over all at once

The riskiest possible migration is the big-bang launch: flip DNS one night and hope. If something’s wrong, you find out from a traffic graph a week later, after the damage is done.

We stage it instead. The new site runs in parallel, fully built, on a staging domain. We crawl it, diff it against the old site, and verify parity, every redirect resolves, every page renders, every title and canonical is correct, before it goes live. Only when the new site is provably at parity do we cut over. And we keep the old site reachable as a reference until we’re certain.

Watch the right things after launch

The first two weeks post-launch are the ones that matter. We watch:

• Crawl errors and 404s in Search Console, every one is a redirect we missed.
• Index coverage, are the new URLs getting indexed at the rate the old ones drop out?
• Rankings for the top queries, a small temporary wobble is normal as Google re-crawls; a sustained drop is a problem to chase down immediately.

Because the redirect map was complete and the cutover was staged, “chasing down a problem” is usually a five-minute fix, not a crisis.

The pattern, not the platform

None of this is WordPress-specific. The same discipline applies migrating off any legacy CMS, any hand-rolled PHP site, any platform you’ve outgrown. The platform you move to matters far less than the rigor of how you move. We tend to land on a headless CMS with a static front end, it’s fast, cheap to host, and a pleasure to edit, but the migration method is what protects your rankings.

If you’re sitting on years of content in a CMS that’s slowing you down, the fear of losing your SEO is the thing keeping you stuck. It shouldn’t be. Done properly, a migration is an upgrade Google rewards, not a gamble.

This is most of what our modernization work is, including migrations of long-running, heavily indexed publications where the rankings were the whole ballgame. If you’re staring down a migration like this, tell us about it.