For UK Creators

🇬🇧 UK

Move your blog to Substack: the complete guide for UK writers

Whether you're on WordPress, Ghost, Blogger, or a self-hosted setup, moving your blog to Substack means trading infrastructure maintenance for writing time. Here's how to do it without losing your content, your SEO, or your readers.

No credit card required. Audit ranking URLs before changing a live site.

Inventory
Export URLs, traffic, and backlinks before moving
Staged
Review important articles before the next batch
Protected
Keep ranking URLs stable until redirects are mapped
7 days
Trial with no credit card required

The problem

The manual version gets old fast.

Running a self-hosted blog in the UK means dealing with hosting bills, plugin updates, security patches, and the creeping anxiety that one bad WordPress update will break everything. Writers who set up a blog five years ago to focus on their writing have often spent more time on technical maintenance than actual content.

The appeal of Substack is obvious: no hosting, no plugins, no CDN configuration, built-in email delivery, and a monetisation layer that works out of the box. But the migration itself is the barrier. UK bloggers have years of published content, email subscribers who have specific GDPR consent records, and search rankings that took years to build — all of which feel at risk when moving platforms.

The SEO concern is the most legitimate. A blog that ranks on Google for a collection of long-tail keywords is generating consistent search traffic. Move that content to a new domain without proper canonical handling and you can lose years of ranking equity in weeks.

Which blog platforms import most cleanly to Substack

Ghost provides exports for posts and member data, but the exact migration path depends on the formats currently accepted by the destination. Verify a small sample of articles, images, embeds, dates, and subscriber fields before moving a full publication.

WordPress is the most common blog platform for UK writers and has a reasonable Substack import path. WordPress exports an XML file (WXR format) that Substack's importer can process. The main issues are formatting inconsistency (especially with custom blocks from Gutenberg or page builder plugins), images stored on external CDNs, and custom post types that Substack doesn't have equivalents for.

Blogger (Google's platform) is still used by a significant number of UK writers who started blogging in the 2008–2012 era. Blogger exports an Atom XML file which requires conversion before Substack can import it. The content is usually clean HTML, but the conversion step adds friction. For Blogger migrators, the manual approach (copy-paste the most important posts) is often faster than fighting the import process for older, simpler content.

Self-hosted platforms like Jekyll, Hugo, or custom CMSs require manual preparation — exporting to Markdown or HTML and cleaning the output before import. The effort is proportional to how non-standard your original setup was.

  • Before importing, run a content audit: identify your top 20 posts by traffic (using Google Search Console or your analytics) and prioritise importing those first.
  • Check which posts have inbound links from other sites — those are your most valuable SEO assets and need the most careful canonical handling after migration.
  • For WordPress sites, install the 'Redirection' plugin before migrating and set up 301 redirects from your old post URLs to the new Substack URLs.
  • Export your Google Analytics data for the past 12 months before migrating — you'll lose historical data visibility once traffic starts going to the new Substack domain.

Preserving your search rankings during the migration

SEO preservation is the single biggest technical concern for UK bloggers moving to Substack. The core principle: never delete your old content without a plan for the ranking equity it holds.

If your blog is on a custom domain, preserve the URLs wherever possible. When URLs must change and you control the old site, map each valuable source URL to its closest destination and apply a permanent redirect only after the destination preserves the useful content and search intent.

If you do not control redirects from the old platform, avoid assuming a canonical change will transfer performance on a predictable schedule. Keep valuable originals stable, publish only meaningfully adapted versions, and monitor both properties before consolidating anything.

The most important thing to preserve: posts that rank on page one of Google for any keyword with meaningful search volume. These are your SEO assets. Import them to Substack first, set up the canonical or redirect relationship, and monitor their rankings in Google Search Console for 90 days after migration.

  • Use Google Search Console to export a list of your top-performing blog posts by impressions and clicks before migrating.
  • Set canonical URLs on all migrated Substack posts pointing to the original blog URLs if you're keeping the old site live.
  • Alternatively, add a 301 redirect on the old blog to the new Substack URL for each migrated post.
  • Submit your new Substack sitemap to Google Search Console immediately after migration to accelerate re-indexing.
  • Monitor rankings weekly for 90 days post-migration — most migrations show some initial drop followed by recovery as Google processes the canonical relationships.

Migrating UK blog subscribers under UK GDPR

If your blog has an email subscriber list, the migration to Substack involves transferring those email addresses to a new platform. Under UK GDPR (which post-Brexit mirrors EU GDPR in substance), you need a lawful basis for this transfer.

The correct lawful basis cannot be inferred from the fact that someone once subscribed. Document how the list was collected, what people were told, which providers will process it, and how opt-outs and data rights will be handled. Check current ICO guidance or obtain advice for the specific transfer.

A conservative approach is to notify subscribers before the transfer, explain the new processor and purpose, preserve consent records, and provide a clear opt-out or re-confirmation path. Check current ICO guidance or obtain legal advice for your specific list and lawful basis rather than relying on a generic migration rule.

Do not import purchased, scraped, or otherwise unpermissioned addresses. Retain an audit trail of the source, consent status, notices, and suppression requests for the addresses you are entitled to process.

  • Send at least two migration announcement emails to your existing list — one when you announce the move, one as a final reminder before you stop using the old platform.
  • Include a clear, prominent 'Subscribe on Substack' button in both emails.
  • Keep records of which subscribers actively re-subscribed on Substack versus which were passively migrated — this matters for GDPR accountability.
  • Do not import email addresses harvested through methods that wouldn't pass Substack's permission standards (purchased lists, co-registration lists, etc.).

Using your blog archive to build a Substack publishing queue

Once you've migrated, your old blog posts don't have to sit as a static archive. Every well-written blog post is potential raw material for Substack Notes — short, punchy content that drives engagement in the Substack feed without requiring readers to click through to a full article.

Narrareach's AI repurposing feature reads any article URL and generates a Substack Note from it. For UK bloggers with large archives, this means you can create months of Substack Note content from posts you wrote years ago, scheduled to go out automatically.

This approach serves two purposes: it gives new Substack subscribers exposure to your best older work, and it keeps you active in the Substack feed during the period when you're rebuilding your publishing rhythm after the migration.

  • Start with a small group of evergreen posts, generate Note drafts, and review each one for current facts and a useful standalone point before scheduling it.
  • Prioritise repurposing evergreen content over time-sensitive posts — a guide to personal finance fundamentals is as relevant now as it was three years ago.
  • Add a line at the end of each repurposed Note: 'Originally published on [your blog] — now archived here on Substack.' This provides context for long-time readers and makes the transition explicit.

How Narrareach solves it

Keep the publishing system close to the writing.

Bulk blog post import Import your full blog archive in batches rather than copying posts one by one — including WordPress, Ghost, and Blogger exports.

AI repurposing from URL Turn any blog post URL into a Substack Note automatically — converting your archive into a scheduling queue for ongoing distribution.

Cloud-based scheduling Queue repurposed blog content as Substack Notes and let Narrareach publish them on a schedule, without manual posting.

Cross-posting to LinkedIn UK bloggers with LinkedIn audiences can cross-post every Substack Note to LinkedIn automatically — reaching both audiences from one action.

Subscriber attribution Identify migrated and repurposed posts associated with subscriber gains, then test whether related content shows the pattern again.

Timezone-aware scheduling Set UK or global posting times to reach your audience at peak engagement windows — particularly useful for UK bloggers with international readerships.

Move your blog to Substack and stop managing infrastructure

No credit card required. Audit ranking URLs before changing a live site.

Questions UK creators ask

Can I import a WordPress blog to Substack?

Yes. WordPress exports an XML file (WXR format) that Substack's importer can process. The import handles basic post content well but may struggle with custom blocks, page builder content, or posts with complex media embeds. Review imported posts for formatting issues before publishing.

Does moving my blog to Substack hurt my Google rankings?

It can when valuable URLs are removed, redirected to weak matches, or republished without a clear primary version. Export current clicks, impressions, backlinks, canonicals, and internal links first. Preserve ranking URLs where possible and monitor any one-to-one redirects after deployment; Google does not guarantee a transfer timeline.

Can I use my existing domain with Substack?

Yes. Substack supports custom domains on paid plans, so your blog can remain at yourname.co.uk or yourname.com while being served by Substack. This is the cleanest SEO migration path as it preserves your domain authority.

Is it legal to move my email subscriber list to Substack under UK GDPR?

You need a documented lawful basis, appropriate processor information, and a way to honour opt-outs and data rights. The correct treatment depends on how the addresses were collected and what subscribers were told. Consult current ICO guidance or legal counsel before transferring a production list.

What happens to my Ghost subscribers when I move to Substack?

Ghost has a dedicated Substack export that includes subscriber email addresses. Ghost paid subscribers can be migrated directly. You'll need to notify subscribers of the platform change under UK GDPR principles and give them an opt-out option before completing the migration.

How long does a blog-to-Substack migration take?

It depends on archive size, formatting, media, subscriber permissions, domain control, and the number of ranking URLs that need individual review. Run a small import first, then schedule the remaining work from what that test reveals rather than relying on a generic timeline.

Can I keep my blog live while also running Substack?

Yes, many UK writers run both in parallel during a transition period. The key is to set canonical URLs so Google knows which version is the authoritative one, and to gradually shift your publishing focus to Substack over time rather than abandoning the blog abruptly.

How do I use my old blog posts to grow my new Substack?

Narrareach can use a publicly accessible blog post as context for an editable Substack Note draft. Review the result for accuracy, permissions, voice, and current facts before adding it to a publishing queue.

Narrareach LLM connector

Connect Claude, ChatGPT, or any MCP-compatible agent to read drafts, schedule posts, and automate Substack, Medium, LinkedIn, X, Bluesky, and Threads workflows.

Read the docs