How to Migrate from WordPress to Superblog (Step-by-Step)

Migrating from WordPress doesn't have to take weeks. With Superblog, you can move your entire blog, preserve your SEO rankings, and go live in 10-15 minutes.
This guide walks you through the migration process, domain setup, and post-migration verification.
Why migrate from WordPress?
WordPress started as a blogging platform. Over two decades, it evolved into a general-purpose CMS. That evolution came with baggage: plugin conflicts, security patches every month, performance degradation.
Business blogs need three things: fast pages that rank, reliable uptime, and zero maintenance overhead. WordPress delivers none of these out of the box.
If you're migrating because WordPress feels bloated, slow, or too technical, you're not alone. Over 200 teams have moved to managed platforms built specifically for business blogging.
What you need before starting
Before migrating, confirm these items:
- WordPress REST API is enabled (it's on by default for most WordPress installations)
- Access to your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.) for DNS changes
- Your Google Analytics tracking ID (if you want to keep the same property)
That's it. No export files to download. No plugins to install. No content cleanup required.
Step 1: Import your WordPress content to Superblog
Superblog pulls content directly from your WordPress site via its REST API. No export files needed.
Create your Superblog account
- Go to write.superblog.ai
- Sign up with your work email
- Start your 7-day free trial (no credit card required)
- Create a new site
Run the import
- From your Superblog dashboard, go to the Data section
- Select WordPress as your migration source
- Enter your WordPress installation URL (e.g.,
https://yoursite.comorhttps://yoursite.com/blog) - Click Import
The import runs automatically. For most blogs, this takes 2-5 minutes.
What gets migrated automatically
Superblog handles everything:
- Posts: All content with formatting preserved
- Images: Featured images and inline images are downloaded and re-hosted on Superblog's CDN
- Categories and tags: Full taxonomy structure preserved
- Authors: Author names and attribution
- Publish dates: Original dates preserved
SEO preservation: URL slugs remain identical. A post at /my-post-title/ on WordPress will be at /my-post-title/ on Superblog. Your existing rankings are not impacted.
No manual cleanup required. Superblog handles WordPress content automatically.
Step 2: Choose your hosting setup
Where your blog lives matters for SEO.
Hosting option comparison
Subdirectory hosting (yoursite.com/blog):
- Best for SEO (keeps all rankings under your main domain)
- Requires routing configuration on your main site
- Worth the setup for long-term traffic gains
Subdomain hosting (blog.yoursite.com):
- Simpler DNS setup (just a CNAME record)
- Google treats subdomains as separate sites
- Fine if your blog is secondary to your product
Root domain hosting (yoursite.com):
- Your entire site becomes your blog
- Only works if blogging is your primary business model
For most businesses, subdirectory hosting wins. It's what we recommend at Superblog and what we use for our own blog.
Step 3: Configure your domain
For subdirectory hosting (yoursite.com/blog)
Subdirectory setup requires routing rules on your main site. Superblog provides configuration snippets for most platforms.
If your main site runs on Vercel, Netlify, or Cloudflare Pages:
- In Superblog settings, go to Domain → Subdirectory Setup
- Copy the provided configuration snippet
- Add it to your
vercel.json,netlify.toml, or_redirectsfile - Deploy your main site
Example for Vercel (vercel.json):
{
"rewrites": [
{
"source": "/blog/:path*",
"destination": "https://your-blog.superblog.click/:path*"
}
]
}
If your main site runs on other platforms:
Superblog provides setup guides for Nginx, Apache, WordPress (as main site), Webflow, Framer, and other platforms. Check the documentation or contact support.
For subdomain hosting (blog.yoursite.com)
Subdomain setup is simpler. You just need a CNAME record.
- In Superblog settings, go to Domain → Custom Domain
- Enter
blog.yoursite.com - Copy the CNAME value provided (something like
cname.superblog.click) - Log into your domain registrar
- Add a CNAME record:
- Name:
blog - Value:
cname.superblog.click - TTL: 3600 (1 hour)
- Wait 10-30 minutes for DNS propagation
Once DNS updates, Superblog automatically provisions an SSL certificate. Your blog will be live at https://blog.yoursite.com with full HTTPS.
Step 4: Set up redirects (if URL structure changes)
If you're keeping the same URL structure (which Superblog does by default), you may not need redirects. The slug /my-post/ on WordPress becomes /my-post/ on Superblog.
If your URL structure changes (e.g., WordPress used /2024/03/post-title/ and you want /blog/post-title/), set up 301 redirects.
Platform-level redirects
In Superblog:
- Go to Settings → Redirects
- Add old URLs and new URLs
- Save and deploy
Cloudflare redirect rules
If you use Cloudflare:
- Go to your Cloudflare dashboard
- Click Rules → Redirect Rules
- Add dynamic expressions or bulk redirects
- Deploy
Use 301 (permanent) redirects, not 302 (temporary). Google treats 301s as "this page moved forever" and transfers ranking power.
Step 5: Verify SEO settings
After migration, verify that SEO elements transferred correctly.
Check on 3-5 posts
Open a few migrated posts and verify:
Meta titles and descriptions: View page source and search for:
<title>Your Post Title</title>
<meta name="description" content="Your meta description">
JSON-LD structured data:
Search for <script type="application/ld+json">. You should see Article schema with author, publish date, and image.
Superblog generates these automatically. If your WordPress posts had custom meta descriptions, you may want to review and update them.
Use Google's Rich Results Test
Go to Google Rich Results Test and enter your migrated post URL. Google will show you which schemas it detects.
You want:
- Article schema
- Breadcrumb schema
- Organization schema (on homepage)
Step 6: Update Google Search Console
Tell Google your blog moved.
- Log into Google Search Console
- Submit your new sitemap:
https://yoursite.com/blog/sitemap.xml - If you moved to a subdomain, add it as a new property
Google will crawl your site and start indexing new URLs within a few days.
Request reindexing for top pages
For your 5-10 most important posts:
- Open Google Search Console
- Use the URL Inspection tool
- Enter the new URL
- Click "Request Indexing"
This speeds up the transition.
Step 7: Reconfigure integrations
Google Analytics
If you're keeping the same GA property:
- Copy your GA4 measurement ID (looks like
G-XXXXXXXXXX) - In Superblog, go to Settings → Integrations
- Add your GA4 ID
- Verify tracking with GA4 DebugView
Email newsletter signup
Superblog has built-in lead generation forms:
- Go to Settings → Lead Generation
- Configure your signup form
- Connect to Mailchimp, ConvertKit, or use webhooks for other ESPs
Post-migration checklist
Run through this checklist after migration:
Content verification
- [ ] All posts imported with correct titles and content
- [ ] Featured images display correctly
- [ ] Categories and tags transferred
- [ ] Publish dates match WordPress originals
SEO verification
- [ ] URL slugs match WordPress (no changes = no redirects needed)
- [ ] Meta titles and descriptions present
- [ ] JSON-LD schemas appear in source code
- [ ] Sitemap generated at
/sitemap.xml - [ ] Google Search Console shows no errors
Technical verification
- [ ] All images load (no 404s)
- [ ] Internal links work
- [ ] Mobile version displays correctly
- [ ] Page load speed under 2 seconds
Monitor for 2 weeks
Check these metrics at day 3, day 7, and day 14:
- Google Search Console: Click trends (should stay flat or rise)
- Google Analytics: Traffic volume
- PageSpeed Insights: Performance scores (should improve vs. WordPress)
If traffic drops more than 15% after week one, check:
- Are URLs matching correctly?
- Did sitemaps submit to Google?
- Are old URLs returning 404s?
What to do with your old WordPress site
After confirming migration succeeded:
Option 1: Take WordPress offline
Delete the WordPress installation and cancel hosting. Verify your new site works first.
Option 2: Leave WordPress up for 30-90 days
Keep WordPress live but add a redirect plugin to send all traffic to your new blog. This gives Google time to fully process the change.
Option 3: Archive WordPress
Export your WordPress database as a backup. Store it locally or in cloud storage. You won't need it, but it's insurance.
Why Superblog makes migration painless
Traditional migrations require export files, content cleanup, manual image uploads, and hours of debugging.
Superblog's WordPress import:
- Pulls content directly via REST API (no export files)
- Downloads and re-hosts all images automatically
- Preserves URL slugs for SEO continuity
- Takes 10-15 minutes total
After migration, you get:
- 90+ Lighthouse performance score (WordPress averages 40-60)
- Automatic SEO schemas, sitemaps, and IndexNow integration
- Auto image optimization and CDN delivery
- 99.99% uptime with zero maintenance
The platform handles everything WordPress required 15 plugins to do. And because it's fully managed, you'll never migrate again.
Start your migration
Ready to leave WordPress maintenance behind?
- Start your free trial (no credit card required)
- Create a site and go to Data → WordPress
- Enter your WordPress URL and click Import
- Configure your domain
- Go live in 15 minutes
Get automatic SEO, 90+ Lighthouse scores, and a platform built specifically for business blogging.