How to Switch Your Blog from WordPress, Ghost, or Medium to inblog

Why Companies Switch Their Blog Platform

You launched your blog on WordPress, Ghost, or Medium. It worked fine at first. But now you're dealing with plugin updates, security patches, slow page speeds, or paying $200/month just to host your blog on a subdirectory.

Sound familiar? You're not alone. We've helped dozens of companies migrate their blogs to inblog — and the reasons they switch follow a clear pattern.

This guide covers why companies switch, how the migration works step-by-step, and what results they see after. Whether you're on WordPress, Ghost, Medium, or Webflow, we've got you covered.

The Top 5 Reasons Companies Switch to inblog

1. Subdirectory hosting without the headache

Hosting your blog on yoursite.com/blog/ instead of blog.yoursite.com or an external platform concentrates your domain authority. This is one of the most impactful SEO decisions you can make.

The problem? Setting up subdirectory hosting on most platforms is painful:

Carat, an AI content platform with 2.6M users, switched from Ghost to inblog specifically for this reason — and saw their traffic grow 13x in a single quarter.

2. SEO is built in, not bolted on

WordPress requires Yoast or RankMath plugins. Ghost has basic SEO. Webflow needs manual meta tag management. With inblog, SEO is native:

• Lighthouse score 90+ out of the box

• Semantic HTML structure that AI search engines can parse

• Meta tags, canonical URLs, and structured data — no plugins needed

• Google Search Console integration built in

3. Lead generation without extra tools

Most blog platforms treat lead capture as an afterthought. You need third-party form tools, popup plugins, or expensive marketing suites.

inblog includes form builders and CTA buttons on every plan — including Free. Mochaclass used this to quadruple their monthly inquiries to 130 per month without any additional tools.

4. No maintenance burden

WordPress users spend hours on updates, security patches, and plugin conflicts. Ghost requires managing a server (or paying $199+/month for managed hosting). With inblog, there's nothing to maintain — it's fully managed.

5. AI-ready content structure

As AI search engines like ChatGPT, Perplexity, and Google AI Overview become major traffic sources, your content needs to be structured for AI citation. inblog's semantic HTML output is optimized for both traditional and AI search from day one.

Migration Guide: Step by Step

Switching platforms sounds intimidating, but the actual process is straightforward. Here's how it works for each platform:

From WordPress

1. Export content — Use WordPress's built-in export (Tools → Export → All Content) to get an XML file

2. Prepare HTML — Convert your posts to clean HTML. WordPress exports include shortcodes and plugin-specific markup that need cleaning

3. Upload to inblog — Use the inblog API or CLI to bulk-create posts. The CLI supports --content-file for HTML uploads with automatic image CDN migration

4. Set up redirects — Create 308 redirects from old URLs to new slugs using inblog's redirect manager

5. Connect domain — Point your subdirectory to inblog (one-time DNS configuration)

6. Verify in Search Console — Confirm indexing and monitor for any 404 errors

From Ghost

1. Export content — Ghost Labs → Export → Download JSON. Ghost's export includes all posts, tags, and metadata

2. Convert format — Ghost uses Mobiledoc format. Convert to HTML for inblog import

3. Upload via API — Use inblog's REST API to create posts with titles, slugs, tags, and HTML content

4. Migrate images — inblog automatically uploads external image URLs to its CDN during import

5. Set up redirects — Map Ghost URLs to inblog slugs

From Medium

1. Request data export — Settings → Security and apps → Download your information

2. Convert HTML files — Medium exports posts as HTML files. Clean up Medium-specific styling

3. Upload to inblog — Create posts via API or CLI

4. Set canonical URLs — If keeping Medium posts live, set canonical URLs in inblog to avoid duplicate content

From Webflow

1. Export CMS items — Webflow allows CSV export of CMS collections

2. Convert rich text — Webflow's rich text fields export as HTML — mostly compatible with inblog

3. Upload and map fields — Match Webflow CMS fields to inblog post attributes (title, slug, content, tags)

4. Update reverse proxy — If using a Cloudflare Worker for subdirectory routing, update it to point to inblog instead

Automation Tip: Bulk Migration with inblog CLI

For large migrations (50+ posts), the inblog CLI makes it fast:

# Create a post from an HTML file
inblog posts create --title "Your Post Title" --slug "your-slug" --content-file ./post.html --json

# Bulk upload with a script
for file in ./posts/*.html; do
  title=$(basename "$file" .html)
  inblog posts create --title "$title" --content-file "$file" --json
done

The CLI handles image migration automatically — local file paths and external URLs are uploaded to inblog's CDN.

What Happens After You Switch

Here's what inblog customers experienced after migrating:

SEO Checklist: Preserving Rankings During Migration

The biggest risk in any platform switch is losing search rankings. Follow this checklist to protect your SEO:

Ready to Switch?

Migration doesn't have to be a weekend-long project. Most inblog migrations are completed in a few hours — and you can start with a free plan to test everything before going live.

1. Start free — Create an inblog account and set up your blog

2. Test with 5 posts — Migrate a small batch to verify formatting and SEO settings

3. Go live — Once verified, migrate all content and set up redirects

4. Monitor — Watch Search Console for 2 weeks to ensure smooth transition