For UK Creators
🇬🇧 UKMove 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.
Free plan available. No credit card required.
- WordPress
- Most common UK blog platform for Substack migration
- Ghost
- UK-founded platform, strong native Substack export
- 6 months
- Typical Google ranking transfer timeline after migration
- £0
- Cost to start importing with Narrareach
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 has the best native Substack export — Ghost is a UK-founded company and the two platforms have made interoperability a priority. If you're on Ghost, the export is clean, preserves metadata, and handles image migration properly. Ghost paid subscribers can also be migrated with their email addresses intact.
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 (yourname.co.uk or yourblog.com), you have two options. Option one: point your custom domain at Substack (Substack supports custom domains on paid plans), keep your URL structure as similar as possible, and the transition is minimal from Google's perspective. Option two: keep your old domain live with 301 redirects pointing to your Substack URLs, which transfers ranking equity over 3–6 months.
If your blog is on a platform subdomain (yourname.wordpress.com, yourname.blogspot.com), you can't control redirects from that subdomain. In this case, keeping the old posts live on the old platform and setting canonical URLs pointing to Substack is the best available option. Google will gradually shift credit to the Substack versions over time.
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 lawful basis most UK bloggers can rely on is legitimate interest: subscribers signed up to receive your content, you're continuing to provide that content, and the transfer to a new delivery platform is a technical change that doesn't alter the nature of what subscribers consented to. This is a reasonable interpretation but not a guaranteed safe harbour — document your reasoning.
The safest approach, which also produces better list quality: email your current subscribers to tell them you're moving platforms, explain what will change, and ask them to re-subscribe on Substack. This re-confirmation resets consent unambiguously and typically results in a smaller but more engaged list. Writers who re-confirm consistently report higher open rates and paid conversion rates on the migrated list.
Subscribers who don't re-subscribe after a reasonable period (typically 30–60 days) should be removed from any Substack import rather than migrated without fresh consent.
- 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.
- Identify 30 of your best blog posts and add them to Narrareach's repurposing queue — that's 6 weeks of daily Notes without writing anything new.
- 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 which migrated and repurposed posts are driving new Substack subscribers, so you know which archive content to promote most.
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.
“I'd been running a WordPress blog for eight years and the hosting and maintenance had become a genuine burden. The move to Substack took a weekend. Narrareach let me turn my best old posts into a Notes queue that kept me active while I was rebuilding my publishing routine. I haven't thought about a plugin update since.”
Andrew C., Personal finance blogger, Leeds
Move your blog to Substack and stop managing infrastructure
Free plan available. No credit card required.
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 if you don't handle the transition carefully. If you keep your old blog live and set canonical URLs pointing to your Substack posts, Google transfers ranking equity over time (typically 3–6 months). If you 301 redirect old URLs to Substack URLs, the transfer is faster. Deleting your old blog without redirects will lose ranking equity entirely.
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?
Under UK GDPR, you need a lawful basis for the transfer. Legitimate interest covers most cases where subscribers signed up specifically for your content and you're continuing to deliver it on a new platform. The safest approach is to notify subscribers and give them a chance to re-confirm — this also produces a higher-quality, more engaged Substack 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?
The technical import typically takes a day or two for most blog sizes. The full migration — including redirects, canonical URLs, subscriber notification, and rebuilding your publishing routine — usually takes 2–4 weeks to complete properly. Rushing the SEO preservation steps is the most common mistake.
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's AI repurposing feature converts any blog post URL into a Substack Note. You can queue these repurposed Notes to publish over time, giving new subscribers exposure to your best work without writing new content. This is one of the most effective ways to maintain a consistent Substack presence during the migration period.
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.