Leaving WordPress Without Losing Your Rankings

The fear is always the same, and it's the thing that keeps people on a stack they've outgrown: "If I rebuild the site, won't I lose everything I've ranked for?" It's a reasonable fear, because it happens. People migrate, traffic craters, and the story travels. But the crash isn't caused by leaving WordPress. It's caused by leaving one specific discipline behind during the move. Keep that discipline and the rankings come with you. Skip it and they don't. That's the whole thing.

So let me tell you where the rankings actually live, because once you see it, the fear resolves into a checklist.

Your rankings aren't in your platform

They're in three places, and none of them is WordPress.

They're in your URLs — the specific web addresses Google has crawled, indexed, and attached ranking signals to. Every link pointing at your site, every position you hold, is tied to an address like /services/roof-repair, not to the software that happens to render it.

They're in your content — the words on the page that earned the relevance in the first place. Text is the most portable thing there is. It doesn't care what serves it.

And they're in your history — the accumulated trust of a domain that's existed and been crawled for years. You keep the domain, you keep the history.

Notice what's missing from that list: the platform. WordPress was the machine that produced the URLs and served the content. Swap the machine while preserving its output, and Google sees the same site at the same addresses with the same words. Nothing to re-earn.

The one discipline: preserve URL identity

Here's the rule that separates a clean migration from a horror story. Every URL that currently ranks must resolve to the same content after the move — either at the identical address, or via a permanent redirect from the old address to the new one, with no chain, no guesswork, no dropped page.

That means, before anything gets rebuilt, you inventory every indexed URL. Every one. Then you map each to its destination on the new site. Pages that keep their address, you keep. Pages that move, you 301-redirect old-to-new. Pages that are being retired, you redirect to the nearest living relative, not to the homepage and not to a 404. The redirect map is the single most important artifact in the entire project, and it's the one most rushed migrations never build. That omission — not the technology — is the crash.

The horror stories are all the same story: someone rebuilt on a new platform, let the URLs change because the new system named things differently, and shipped without a redirect map. Overnight, every ranking URL became a dead end. Google found 404s where it expected pages, the link equity had nowhere to land, and the traffic that took years to build evaporated in a week. Preventable, completely, with one discipline nobody wanted to spend the hours on.

How I run it

Every cutover I do is URL-identity-preserving by default — the redirect map comes before the design, not after the launch. The sites I've moved from WordPress kept their addresses, kept their content, and kept their positions, because keeping them was the first requirement, not a hoped-for outcome. You can see the kind of work that comes out the other side. The discipline is unglamorous and it's the entire game.

The other half of doing this right is making sure you actually control the domain and the DNS you're migrating — because a migration you don't have the keys to isn't a migration, it's a negotiation. That's a separate conversation about who owns your website, and it's worth having before you move anything.

If you're thinking about leaving WordPress, don't commit to a rebuild until someone's audited what you'd be moving. I'll do the migration audit first — the URL inventory, the redirect map, the honest read on risk — before you sign onto anything. That's the step that turns the fear into a plan. Inquire about a project →