How to Move Off WordPress Without Losing Your Google Rankings
The number one fear about leaving WordPress isn't speed or cost. It's this: "I've spent years getting these pages to rank on Google. If I move the site, will I lose all of it?" It's a fair worry, and it's the reason a lot of owners stay on a platform they've outgrown. The good news is that ranking loss after a migration is almost always avoidable. It comes from a handful of specific mistakes, and every one of them has a fix.
This is a plain, non-technical walkthrough of how to move off WordPress while protecting your rankings, and what to check before, during and after. It pairs with our broader guide on how to migrate WordPress to a static site, and on the hard lessons we learned doing exactly this in 10 lessons migrating WordPress to code.
Why rankings actually drop after a move
Google ranks individual pages at specific web addresses. When you migrate, you can accidentally break the link between "the page Google ranked" and "where that page now lives." Rankings fall for four reasons, in rough order of how often they cause real damage:
- URLs change with no redirect. The old address returns a 404, Google drops the page, and any backlinks pointing to it lose their target. This is the big one.
- Titles and descriptions get lost. Your carefully written page titles and meta descriptions don't carry over, so Google sees different, weaker signals.
- Content or structure quietly changes. Headings, body text or internal links go missing in the move, so the page Google re-crawls isn't the page it ranked.
- The new site is slower or not mobile-friendly. Less common when moving to static, but a rebuild that ignores speed can hurt.
Notice that none of these are caused by "leaving WordPress." They're caused by losing information during the move. Keep the information, keep the rankings.
Step 1: Map every URL before you touch anything
Start with a complete list of the pages you have today. Export your URLs from your sitemap, from Google Search Console, or from an SEO plugin like Yoast. You want one master list of every page and post that exists, especially the ones that get search traffic.
For each URL, note whether it will keep the same address on the new site or move to a new one. The goal is to keep addresses identical wherever you can, because a URL that doesn't change needs no redirect and carries zero risk. Aim to change as few as possible.
Step 2: Keep the same URLs wherever you can
The safest migration is one where most pages live at exactly the same address afterward. If your blog post was
at /blog/my-article, it should still be at /blog/my-article on the new site. When the
address is unchanged, Google barely notices anything happened.
Sometimes a few URLs have to change, for example if WordPress added a date or a category folder you want to drop. That's fine, as long as every one of those changes gets a redirect, which is the next step.
Step 3: Set a 301 redirect for every URL that changes
A 301 redirect is a permanent instruction that says "this page has moved here for good." It sends visitors to the new address automatically, and it tells Google to transfer the old page's ranking and backlinks to the new one. It is the single most important tool for protecting rankings in a move.
The rule is simple: every old URL that changes must 301-redirect to its closest new equivalent. Not to the homepage, to the specific matching page. A redirect to the homepage is treated like a soft 404 and loses the ranking anyway. Build the redirect list from your URL map in Step 1, so there are no gaps.
Step 4: Carry over titles, descriptions and schema
Each page's title tag and meta description are part of why it ranks and why people click it in search results. Bring them across exactly. If you used structured data (schema) for things like articles, FAQs, products or reviews, recreate that on the new pages too, because it feeds rich results and AI answers.
While you're at it, preserve the page content itself: the headings, the body text, the images and their alt text, and the internal links between pages. The page Google re-crawls should look like the page it already trusted.
Step 5: Rebuild the sitemap and prepare canonical tags
Generate a fresh XML sitemap listing every live URL on the new site. Make sure each page has a correct
canonical tag pointing to itself, so Google knows which version is the real one and you avoid
duplicate-content confusion. If your site is multilingual, keep the hreflang links between language
versions intact so the right page shows in the right country.
Step 6: Launch, then verify in Search Console
Once the new site is live and redirects are in place, go to Google Search Console and do four things:
- Submit the new sitemap so Google starts crawling the new pages quickly.
- Use URL Inspection on a few important pages to confirm Google can fetch and index them.
- Spot-check redirects by visiting old URLs and confirming they land on the right new page.
- Watch the Coverage and 404 reports over the next couple of weeks for any old URL that slipped through without a redirect, and add the missing redirect when you find one.
Expect a little short-term wobble while Google re-crawls and processes the redirects. That settles. What you're watching for is any page returning a 404 that used to rank, because that's the one thing to fix immediately.
The pre-launch checklist
| Check | Why it matters | Done? |
|---|---|---|
| Full list of current URLs exported | Nothing gets forgotten in the move | ☐ |
| URLs kept identical where possible | Unchanged URLs carry zero risk | ☐ |
| 301 redirect for every changed URL | Transfers ranking and backlinks, kills 404s | ☐ |
| Titles and meta descriptions carried over | Preserves ranking and click signals | ☐ |
| Schema / structured data recreated | Keeps rich results and AI citations | ☐ |
| Fresh XML sitemap + canonical tags | Helps Google find and trust the new pages | ☐ |
| hreflang preserved (if multilingual) | Right language shows in the right country | ☐ |
| Search Console verified after launch | Catches any missed redirect early | ☐ |
How ShiftPress handles this for you
The reason migrations go wrong is that the steps above are easy to skip and tedious to do by hand. ShiftPress is built to do them as part of the move. When it migrates your WordPress site, it keeps your existing URLs, generates the 301 redirects for anything that has to change, carries over your titles, meta descriptions and schema, and produces a fresh sitemap with correct canonical and hreflang tags. The result is a faster site at the same addresses, which is the combination Google rewards.
And because the new site is clean static code rather than a database and a plugin stack, the speed improvement tends to help rankings recover, not just hold.
Move off WordPress without the ranking risk
ShiftPress keeps your URLs, sets your redirects, preserves your titles, descriptions and schema, and ships a faster site at the same addresses. We're onboarding in small batches. Join the waitlist for a free look at your site.
Join the waitlist ↗Frequently asked questions
Will moving off WordPress hurt my Google rankings? +
What's the biggest cause of lost rankings after a migration? +
How long until Google settles after a move? +
The bottom line
Leaving WordPress does not cost you your rankings. Losing information during the move does. Keep your URLs, redirect what you must change, carry over your titles, descriptions and schema, submit a fresh sitemap, and verify in Search Console. Get those right and the move is invisible to Google, except that your pages now load faster, which is one of the few things that can quietly push your rankings up rather than down.