Skip to content

How to migrate off WordPress without losing rankings

A practical UK guide for owners leaving WordPress. How to export cleanly, preserve every ranking, keep email running, and stop paying for hosting you no longer need.

01 / WordPress is portable. The question is what to port it to.

The export is easy. The rebuild is the interesting part.

WordPress has one clear advantage over every hosted builder when it comes to leaving: the content is yours, the database is yours, the uploads folder is yours, and all of it exports cleanly with a few clicks. Migration off WordPress is rarely blocked by the platform itself.

What slows most WordPress migrations down is the layer that sits on top of the content. Page builders, premium themes, shortcodes, membership plugins and SEO plugins all leave their fingerprints on the pages, and those fingerprints do not port to a hand-coded site. The practical answer is usually to treat the export as a content library and to rebuild the site fresh, keeping the URL structure so the SEO value carries over.

Beyond the rebuild, the things that matter are the 301 redirect map, the email continuity, the timing of the hosting cancellation and the Search Console handover. The rest of this page walks through each in the order they matter.

02 / What to plan for

Six things that matter in a WordPress migration

Which WordPress you are on, what exports, URL preservation, hosting economics, email, and the cancellation timeline.

WordPress.com versus self-hosted WordPress

The two are different products and the migration looks different for each. WordPress.com is a hosted subscription where you have limited access to the underlying files. Self-hosted WordPress (WordPress.org) runs on hosting you control, often through cPanel, SiteGround or WP Engine, and gives you full access to the database and the uploads folder. We handle both, but the first thing we check is which one you are on.

Export is the easy part

WordPress has an excellent export story. The built-in Tools > Export produces a WXR file with every post, page, custom post type and comment. The uploads folder holds every image and document. A full database dump holds everything else. For a migration off WordPress, the content is almost never the problem. What to do with it on the other side is.

URL structure and the 301 map

WordPress permalink structures are usually tidy (/about, /services/plumbing, /blog/post-title) and worth preserving on the new site to keep the SEO benefit of years of internal and external links. Where a structure has to change (for example, moving from /?p=123 style permalinks to tidy slugs), every old URL needs a 301 redirect to its new home. The redirect map is the single most important artefact of the migration.

Hosting, and why leaving it is usually a relief

Most self-hosted WordPress sites are on shared hosting (SiteGround, Bluehost, 123-reg) or on a WP host (WP Engine, Kinsta, Flywheel). In either case, the ongoing cost of the hosting plus the SSL plus the backup plugin plus the security plugin plus the theme licence plus the page builder licence adds up to more than most owners realise. A managed subscription on modern infrastructure usually costs less once all the line items are accounted for.

Email continuity

Email on a WordPress domain almost always runs through Google Workspace or Microsoft 365 (or, less commonly, through the web host's built-in mail). Moving the site does not move the email: only the A and CNAME records change on the DNS side, while the MX records stay pointed at whoever runs the inbox. If your email is on your web host's mail server, we usually migrate it to Workspace or Microsoft 365 as part of the move, because host-based mail is fragile.

Cancellation timing on hosting and plugins

Do not cancel the WordPress hosting on cutover day. Keep it alive for at least two weeks, and ideally a full month, so that Google can follow the 301 redirects from old URLs to new ones. Premium plugin licences (Yoast, ACF, Elementor Pro, WP Rocket) can be cancelled earlier because they only matter while the old site is serving traffic, but the hosting keeps doing silent work long after you stop looking at it.

03 / How we run it

From export to archived hosting

01

Audit and export

We export the WXR file, pull the uploads folder, take a database backup, and list every indexed URL in Google Search Console. The WordPress site stays live throughout. If it is self-hosted, we take an archive for cold storage in case anything needs checking later.

02

Rebuild hand-coded

We design and build the new site on staging, pulling content from the export where useful and rewriting where the WordPress copy has aged. No plugins, no page builder, no theme updates to chase in six months. One modern codebase on fast infrastructure.

03

Redirect map and DNS cutover

We build a one-to-one 301 redirect map from every live WordPress URL to its new home. DNS switches over in a single planned window, usually outside working hours. MX records for email are preserved exactly, so inboxes continue to flow.

04

Search Console and the slow cancel

New sitemap submitted to Search Console on the same day as the cutover. We monitor coverage for two to three weeks, confirm rankings have stabilised, and only then cancel the WordPress hosting and any premium plugin licences. The old site gets archived before anything is switched off.

FAQ

Common questions

Will I lose my WordPress SEO when I migrate?

Not if the redirect map is complete. WordPress sites usually have substantial accumulated SEO value, and most of that value sits in the URL structure and the inbound links pointing at specific pages. If every old URL redirects to its new equivalent with a 301, Google forwards the authority within a few weeks and rankings are usually stable or better after the move. Sites that lose SEO in a WordPress migration almost always lost it because URLs changed without redirects.

Can you import all my WordPress content?

Yes. WordPress's built-in export produces a thorough WXR file with every post, page and custom post type. Uploads come across as files, and a database dump covers anything structured that the XML misses. That said, for most rebuilds we use the export as a content source rather than a direct import, because WordPress content is often full of shortcodes and page-builder markup that do not translate cleanly. The rebuild ends up cleaner for it.

Do I need to keep my WordPress hosting running after we move?

Yes, for at least two weeks and ideally a full month. Google needs time to crawl every old URL, follow the 301 redirect, and update its index. During that window the old site continues to serve redirects but no real content. Once Search Console confirms the new URLs are indexed and the old ones are redirecting cleanly, the WordPress hosting can be cancelled. Archiving a copy of the site first is a sensible precaution.

What about my Elementor or Divi page builder content?

Page builder content is the hardest thing to migrate off WordPress because the layout information lives in builder-specific markup, not in clean HTML. We export the text content and the images, look at the pages in the browser to capture the layout intent, and rebuild the pages hand-coded on the new site. The result is usually faster, cleaner and easier to update than the builder version it replaces.

Will my email survive the move?

If your email runs through Google Workspace or Microsoft 365, yes, without any interruption. The MX records in DNS stay untouched while the A and CNAME records change to point at the new host. If your email runs on your WordPress web host's built-in mail server (common on shared hosting), we migrate it to Google Workspace as part of the move, which is usually overdue anyway.

Is a managed subscription cheaper than self-hosted WordPress?

Once everything is counted, usually yes for a small-business site. A realistic WordPress setup costs the hosting, the SSL if not included, a backup plugin, a security plugin, a theme licence, a page builder licence, an SEO plugin, and the owner's time dealing with updates. Add those up over a year and most sites are spending £40 to £80 a month on WordPress already, without counting the time cost. Our Starter and Standard plans roll all of that into one managed fee with changes included.

Ready to leave WordPress behind?

Plans from £39/mo. We export, rebuild, redirect, and keep the WordPress hosting running just long enough to hand over cleanly to Google.