Migrating Off WordPress Without Losing Your Rankings

Migrations go wrong in a very specific way, and it is almost never the new framework's fault.

A business rebuilds its site, the new one is faster and better looking, and six weeks later the enquiries have dried up. Somebody blames the rebuild. The actual culprit is usually a spreadsheet nobody made.

Rankings live on URLs, not on sites

This is the thing to internalise before anything else.

Google does not rank "your website." It ranks individual addresses. Ten years of accumulated authority sits on /services/plumbing-tripoli, not on your domain in some general sense. If the rebuild moves that page to /services/plumbing and nothing tells Google the two are the same, the old address returns a 404 and everything attached to it — the rankings, the backlinks, the traffic — has nowhere to go.

WordPress makes this worse than average, because it generates addresses nobody would choose deliberately: /?p=42, /2019/03/12/our-services/, /category/uncategorized/. Any sane rebuild wants cleaner URLs. That instinct is right and it is exactly what causes the damage if the mapping is skipped.

The first deliverable is a spreadsheet, not a design

On a migration I take on, nothing gets built until this document is agreed:

Three columns do the work. Old URL comes from a crawl plus Search Console, because a crawl alone misses pages nothing links to any more that still get traffic. Clicks tells you which rows are worth arguing about. New URL is the decision.

The fourth column matters more than people expect. Not every old page deserves a redirect — a genuinely dead page should return 410 Gone rather than being pointed at the homepage. Redirecting everything to the homepage is a classic mistake: Google treats a mass redirect to an irrelevant page as a soft 404 and ignores it, so you get the worst of both outcomes.

What else quietly goes missing

The URL map gets the attention. These are the things that vanish silently in a rebuild that only copies the visible text:

• Title tags and meta descriptions — often better written on the old site than anyone remembers
• Image alt text — years of it, and it is why some pages get image traffic
• Internal links between posts — the structure that told Google which of your pages matter
• Canonical tags — get these wrong on the new site and you can deindex working pages
• Structured data — if the old theme output any, and the new site does not, you lose whatever it earned

Retyping content by hand is where all of this gets lost. It should be migrated, not rewritten, unless you have specifically decided to rewrite it.

What you actually gain

Assuming it is done properly, the win is real and it is mostly speed.

A typical WordPress business site is a theme framework, a page builder, and a stack of plugins that each add their own scripts — then three caching plugins bolted on to hide the result. The rebuild sends finished HTML from the server with no theme to download and no plugins fighting each other. On a phone over mobile data in Lebanon, which is most of your traffic, that is not a subtle difference.

The second win is that you stop renting your own website. No plugin subscriptions, no builder licence, nothing that breaks on a Sunday because it auto-updated.

When not to do it

Plainly: if your WordPress site is a simple brochure, nobody edits it, and it loads acceptably on a phone, a migration is money spent on something your customers will never notice. I would rather say that than take the work.

The case is strong when the site is genuinely slow, when you are paying for plugins you did not choose, when editing it is painful enough that you have stopped, or when it needs to grow into something — bookings, accounts, a real catalogue — that WordPress will fight you on.

The short version

Rankings survive migrations when somebody writes the URL map first and tests every redirect before launch. They do not survive when the design gets all the attention. Expect a small wobble in the first week or two while Google re-crawls; expect it to recover.

The full process, what it costs and what carries over is on the WordPress to Next.js page. Most of this work comes from businesses in Tripoli sitting on a site somebody built for them years ago and then stopped answering about.