How to migrate Ghost to WordPress (without losing SEO)

01Why move from Ghost to WordPress

Ghost is genuinely excellent at what it does: a fast, focused, beautiful publishing platform with built-in newsletters and memberships. If that's all you need, it's a fine home. This isn't a story about escaping a bad platform — it's about outgrowing a focused one.

People move to WordPress when they want more than Ghost is built to do. WordPress has tens of thousands of plugins and themes, which means almost any feature — complex e-commerce, directories, custom post types, niche integrations — is an install away rather than a custom build. The breadth is the whole draw.

What WordPress gives you that Ghost doesn't

• A vast plugin ecosystem. Whatever you want to add, something likely already does it — versus Ghost's deliberately lean, code-it-yourself approach.
• Thousands of themes. Far more design choice and far more page-builder options than Ghost's curated theme model.
• A bigger talent pool. WordPress developers and support are everywhere, so help is easier to find when you need it.
• Both are yours to own. Ghost and WordPress are open-source and self-hostable — you're trading one ownable platform for a more flexible one, not leaving rented land.

Be honest with yourself about the trade, though. WordPress's flexibility is also more weight and more maintenance; Ghost's speed and simplicity are real strengths. Move because you need what WordPress offers, not because Ghost did anything wrong.

02What moves cleanly and what breaks

Because both platforms are open and Ghost exports cleanly, this is a true content migration. A few things still need attention — especially anything tied to Ghost's membership and newsletter features, which have no direct WordPress equivalent out of the box.

Your editorial content — posts, pages, tags, and most images — comes across through Ghost's JSON export and a WordPress importer that reads it. That's the heavy lifting handled. Tags usually map to WordPress categories or tags, and authors transfer in most cases.

The genuine gap is Ghost's members and newsletter system. WordPress doesn't have that built in, so if you run paid memberships or send newsletters from Ghost, plan to rebuild those with a membership plugin and an email tool — and export your member and subscriber lists before you leave.

03Pre-flight checklist before you start

Ghost's membership features make the prep here more important than a plain blog move. Run this list first so nothing — especially subscriber data — gets stranded on the old platform.

• Export your content as JSON from Ghost's Labs settings — this single file holds your posts, pages, tags, and structure.
• Export your members and subscribers separately if you use Ghost's membership or newsletter features; that data isn't in the content JSON in usable form.
• Inventory your post URLs. Note your slug structure so you can match or redirect it on WordPress.
• Decide your domain, hosting, and permalinks. Where will WordPress live, and what URL structure keeps your links closest to Ghost's?
• Plan replacements for Ghost-only features — a membership plugin and an email tool if you need them.

The subscriber export is the easy thing to forget and the painful thing to lose. Ghost lets you export members as a CSV; do that before you cancel anything, because once the Ghost site is gone, rebuilding that list from scratch is the kind of setback you can't redirect your way out of.

04The step-by-step on a staging copy

Do the entire move on a staging site first, then promote it once it's verified. Here's the sequence that keeps the JSON import predictable and the membership rebuild from being rushed.

• Install WordPress on your host via a one-click installer or your host's setup help.
• Set your permalink structure first, under Settings, Permalinks, to sit as close to Ghost's slugs as possible.
• Install a Ghost importer plugin and upload your Ghost JSON export file.
• Verify posts, pages, and tags imported and that tags mapped sensibly to categories or tags.
• Check and reupload images so nothing hotlinks back to the old Ghost install.
• Rebuild membership and newsletter features with your chosen WordPress plugin and email tool, importing your subscriber CSV.

The content import is usually straightforward — Ghost's clean structure imports well. The time sink, if you have it, is rebuilding members and newsletters, because there's no one-click bridge. Treat that as its own mini-project on the staging copy rather than an afterthought on launch day.

When the staging site's content matches your inventory and any membership setup works in test, you're ready to handle URLs and redirects before going live.

05Preserving your SEO: URLs, redirects, and canonicals

This is the step that protects your search traffic, and it matters here because Ghost and WordPress structure URLs differently. Ghost typically puts posts right at the root — yourdomain.com/post-slug/ — while WordPress may insert a category or date prefix unless you tell it not to.

So your first move is to set WordPress's permalinks to match Ghost's root-level slugs as closely as you can. If you can make the URLs identical, you barely need to redirect anything — which is the cleanest possible outcome and worth a few minutes in the Permalinks settings.

Mapping and redirecting what changes

• Match permalinks to Ghost's slug structure first, so the maximum number of URLs stay identical and need no redirect at all.
• Map every URL that still changes to its new WordPress address, and set a 301 for each — a redirect plugin like Redirection does this without code.
• Watch tag and author archive URLs, which differ between the two platforms and can quietly 404 if you forget them.
• Rebuild your sitemap and canonicals with an SEO plugin (Yoast or Rank Math), then submit the sitemap in Google Search Console after launch.

The same domain stays with you throughout, so this is a within-domain URL move, not a domain change — which keeps the SEO risk lower than a cross-platform jump. Match what you can, redirect the rest, and watch Search Console for 404s in the first weeks.

06The tools that help

The core move runs on free tools — Ghost's export and a WordPress importer. The membership rebuild is where you'll choose paid tools, so know what each part does before you commit.

• Ghost's JSON export (in Labs) is the source file for all your editorial content.
• A Ghost importer plugin for WordPress reads that JSON and creates your posts, pages, and tags.
• A redirect plugin (Redirection, or your SEO plugin's manager) turns any URL changes into 301s code-free.
• An SEO plugin (Yoast or Rank Math) rebuilds your sitemap, canonicals, and metadata.
• A membership plugin and email tool replace Ghost's built-in members and newsletter, if you used them.
• Managed WordPress hosting with one-click install and free staging removes the only technical setup step.

On hosting: Cloudways is the managed cloud host we point readers to here, mainly for the free staging on every app. That matters more than usual on a Ghost move, because rebuilding members and newsletters takes real testing — staging lets you do all of it on a private copy and push live in one move. Several hosts offer staging; this is the one we lean on.

Staging turns the membership rebuild from a launch-day gamble into a rehearsal. You can break it, fix it, and confirm a test subscriber flows through correctly before a single real reader is affected.

07Common pitfalls and a hosting note

The mistakes on a Ghost move cluster around members and URLs. Here's what catches people most often, and how to stay clear of each.

• Forgetting to export subscribers. Pull the members CSV before you cancel Ghost — it isn't recoverable afterward.
• Assuming WordPress has built-in memberships. It doesn't; budget time to rebuild that with a plugin and an email tool.
• Letting permalinks default. Match Ghost's root-level slugs first, or you'll redirect URLs you never needed to change.
• Ignoring tag and author archives. Those URLs differ between platforms and quietly 404 if you skip them.
• Underestimating WordPress's weight. It's more flexible but heavier than Ghost — choose a lean theme so you keep the speed you valued.

On hosting, the decision that shapes the rest is where WordPress lives. A managed host that installs WordPress, keeps backups, and offers staging covers the technical setup so you can spend your energy on the membership rebuild — the part that actually needs your judgment, not your sysadmin skills.

08FAQ

Can I import Ghost content into WordPress automatically?

Largely, yes. Ghost exports all your content as a JSON file from its Labs settings, and WordPress has importer plugins built to read that format. Your posts, pages, tags, and most images come across. You'll still want to verify images imported and check that tags mapped sensibly to WordPress categories or tags.

Will my Ghost members and newsletter transfer?

Not automatically — WordPress has no built-in equivalent to Ghost's membership and newsletter system. Export your members as a CSV before leaving Ghost, then rebuild the functionality with a WordPress membership plugin and an email tool, importing that subscriber list into your new setup.

Will moving from Ghost to WordPress hurt my SEO?

Only if you let URLs change without redirecting them. Ghost and WordPress structure URLs differently, so match your WordPress permalinks to Ghost's slugs first, then 301-redirect anything that still changes. Since you keep the same domain, the SEO risk is lower than a platform-and-domain move combined.

Is WordPress better than Ghost?

Neither is simply better — they're built for different priorities. Ghost is faster, leaner, and has memberships built in; WordPress is heavier but vastly more flexible thanks to its plugin and theme ecosystem. Move to WordPress when you need that flexibility, not because Ghost fell short at what it does.

This is general, experience-based guidance from running a theme shop, not financial or professional advice for your specific site. Platform features and tools change, so verify the current details with Ghost, your chosen host, and the plugins before you rely on them — and if your site carries real revenue, consider professional help.