You can move a Blogger (Blogspot) blog to WordPress without losing your posts, images or search rankings. The current route is a Google Takeout export, a Blogger importer plugin that reads that file, and 301 redirects from your old addresses to the new ones. The work is a few hours for a small blog. The part that decides whether your traffic survives is the hosting setup you do first and the checks you run last. We run WordPress hosting with free migration, daily backups and free SSL, so this guide is written around the setup we would want under a blog before moving it.
TL;DR
- Back up your blog from Blogger (Settings > Manage blog > Back up content > Download). You get a Google Takeout file called feed.atom.
- Set up WordPress on hosting first, with SSL on and the Post name permalink structure, then import the file with a plugin built for the Takeout format.
- Pages, widgets and your theme design do not come across in the export. Rebuild them by hand.
- Keep the old blog live until you have checked posts, images, redirects and Search Console. Expect a temporary traffic dip even when everything is right.
Table of Contents
- Why the old method no longer works
- Before you start: decide three things
- Step-by-step: Blogger to WordPress
- What does not move automatically
- Check the result after migration
- When something goes wrong
- Our perspective
- A hosting plan built for this move
- FAQ
- Sources
Why the old method no longer works
Most guides ranking for this topic describe a one-click importer under Tools > Import. That importer was built for Blogger's old XML backup. Blogger now sends backups through Google Takeout, and several current write-ups, including a 2026 WordPress migration guide from WPBeginner, report that the default importer no longer handles the new file reliably. Readers on forums report that the Blogger option has disappeared from some WordPress installs altogether.
The practical result: you need a plugin that reads the Takeout file directly. BtW Importer is one that does. It takes the .atom file from Google Takeout and brings in posts and images. The same WPBeginner guide also lists a second plugin, Blogger Importer Extended, which can import comments but limits the free version to 20 posts.
Before you start: decide three things
Where the blog will live
There are two kinds of WordPress. WordPress.com is a hosted service with plan limits on plugins. WordPress installed on your own hosting (self-hosted WordPress) lets you install any importer, any SEO plugin and any theme. Because the import relies on a third-party plugin, self-hosted WordPress is the straightforward choice for this migration. It is also what business blogs, affiliate sites and anything you plan to grow usually end up on.
Our WordPress hosting plans are built for this case: WordPress installs easily, and the stack uses LiteSpeed with LSCache, MariaDB, HTTP/2 and PHP 8, with a free CDN, free SSL and staging tools. If you only run a simple blog, our shared hosting plans cover the same basics.
Whether you keep your address
If your blog uses a custom domain (yourname.com) connected to Blogger, you can keep it. You point the domain to the new host once the import is checked, and the old URLs keep working. If you are on a yourname.blogspot.com address, you do not control that domain, so the move means a new domain and a new set of addresses. Register one first through domain registration, or bring an existing one with domain transfer. Then read our guide on redirecting one domain to another without losing SEO, because forwarding the old address is where blogspot.com moves lose the most traffic.
What you will have to rebuild
The Blogger export carries your content, not your design. According to the WPBeginner guide, Blogger pages (About, Contact), widgets, the template and comment avatars need to be recreated manually unless your importer handles them. Make a list now: the pages, the sidebar items, any ad code, the email signup form, the analytics tag. It is much less stressful to tick items off a list than to discover gaps after you switch DNS.
Step-by-step: Blogger to WordPress
Step 1: Back up your Blogger blog
In Blogger, open Settings, then Manage blog, then Back up content, and choose Download. Per Blogger's own help page, the backup is delivered through Google Takeout, and inside it you find a path like Takeout > Blogger > Blogs > [your blog name] > feed.atom. Blogger states that this file can be used to import posts, pages and comments, and that older XML backups can also be imported.
Where it goes wrong: people download the export and then delete or edit the blog. Do not. Keep the blog live and untouched until the end, and store the zip file somewhere safe. If you have several blogs on one account, make sure you picked the right one in the Takeout selection.
Where hosting helps: a new WordPress site is only as safe as its backups. Our plans include daily backups, so once the import is done you have a restore point from day one rather than relying on a manual export.

Step 2: Set up WordPress on your host
Install WordPress, turn on SSL (an HTTPS certificate, which we include free), and set a theme you can live with for now. You can change the design later. Do not import into a half-configured site you plan to rebuild.
Then go to Settings > Permalinks and select Post name. The WPBeginner guide recommends this default when using BtW Importer, because the plugin stores the old address of every post and sends visitors from the old address to the new post.
If you want to do all of this without touching the live site, use staging. Staging is a private copy of your site where you can run the import, check the results and fix problems before anything is public. It is included with our WordPress hosting. Our blog setup workflow covers the rest of a fresh WordPress launch, including the settings people forget.
New to moving WordPress sites between environments? We keep a guide to migrating WordPress to a new host, and you may need it later if you go from staging to the live address.
Step 3: Import with a Takeout-compatible plugin
The steps for BtW Importer, as described in its project page on GitHub and the WPBeginner guide:
- Install and activate the plugin from the Plugins screen.
- Open the BtW Importer menu in WordPress.
- Upload your feed.atom file.
- Click Extract Data. The plugin reads the file and counts your posts and pages.
- Click Start to begin the import.
According to those sources, the plugin downloads images hosted on Google's servers into your WordPress media library and rewrites the image links to the new copies. It also sets the first image of each post as the featured image. Blogger labels become WordPress categories, and drafts stay drafts.
Where it goes wrong:
- Large archives time out. The plugin's page notes that it does not overwrite existing posts, so if an import stops partway and you run it again, delete the partial import first (posts, pages and images) to avoid duplicates. Make sure your hosting has enough PHP execution time and memory for a big archive.
- Server speed matters. The project page notes that Nginx-based servers import more slowly than Apache or LiteSpeed. Our hosting runs LiteSpeed, which fits this job.
- Comments. WPBeginner reports BtW Importer does not bring in comments. If your comments matter, check whether you need the Extended importer, and test it on staging first.
Step 4: Rebuild pages, menus and widgets
Create your About, Contact and any other static pages by copying them from Blogger. Rebuild your navigation under Appearance > Menus. Add the sidebar items you actually want, not every widget Blogger had. This is the moment to drop the clutter.
Then check the old tags in your Blogger template: analytics, ad code, verification meta tags. These live in the template, so they are not in the export. Add them again with a lightweight plugin or your theme settings.
Step 5: Check redirects
Redirects are the step that protects your rankings. A 301 redirect is a permanent "this page has moved" signal that tells Google to pass the old address's standing to the new one. WPBeginner's guide calls this the most important part of the whole migration.
Blogger post addresses follow the pattern /YYYY/MM/post-title.html. BtW Importer automatically adds a 301 from that pattern to the new WordPress address and provides a redirect log page where you can review and manage them, according to its project page. Open a few old Blogger URLs on your new site and confirm each lands on the right post. If you want to keep the old .html endings instead, one 2026 checklist suggests setting the permalink structure to /%year%/%monthnum%/%postname%.html, per Income Affairs. Pick one structure and keep it.

If you switch to a domain that is not the old one, you will also need server-level redirects. Our guides on moving WordPress to a new domain and HTTP to HTTPS redirects give the rules to use.
Step 6: Go live
When staging checks out, point your domain's DNS to the new host. Keep the Blogger blog in place and do not delete it while DNS settles and you run your checks. Our website migration checklist walks through the cutover order so nothing is served from two places at once.
What does not move automatically
| Item | Comes over in the import? | What you do |
|---|---|---|
| Posts | Yes | Spot-check formatting |
| Images | Yes, copied to your media library | Review the Media Library |
| Labels | Become categories | Merge or rename as needed |
| Drafts | Stay drafts | Review before publishing |
| Comments | Depends on the plugin | Test on staging |
| Pages | Not in the default importer, per WPBeginner | Recreate or check importer support |
| Widgets and sidebar | No | Rebuild |
| Theme and design | No | Choose a WordPress theme |
| Analytics and ad code | No | Add to the new site |
Check the result after migration
Work through this list on the new site before and after the DNS switch.
- Flush permalinks. Go to Settings > Permalinks and click Save Changes without changing anything. A post-migration checklist from ServMask says this refreshes the rewrite rules and fixes many URL issues.
- Test 5 to 10 URLs. The same checklist suggests sampling posts, pages, categories, tags and author archives.
- Review imported content. Look at a handful of long posts, posts with galleries and your oldest posts, since formatting problems cluster there.
- Check the Media Library. Images should be in WordPress, not still pointing at Google's servers.
- Confirm redirects return 301. Use your browser's network tab or a header checker.
- Update internal links. Links between your own posts may still point to old addresses.
- Add an SEO plugin and a sitemap. Rank Math and Yoast are the two the Income Affairs checklist names.
Tell Google about the move
Add the new site to Google Search Console and submit its XML sitemap, which usually sits at yourdomain.com/sitemap.xml. Watch the Pages report over the next weeks for 404 errors and add redirects for any broken URLs, per the WPBeginner guide. If your domain changed, use the Change of Address tool in Search Console settings, as the ServMask checklist describes.
Expect a dip, then recovery
Some sites see a traffic dip after a platform move. One 2026 guide puts it at roughly 2 to 8 weeks while Google re-indexes, with recovery when redirects are correct, according to Aurora WP Theme. Treat that as a rough range rather than a promise. To judge your recovery, compare the same pages week over week, and our walk-through of blog analytics for growth shows which numbers are worth tracking. Our SEO best practices for bloggers covers what to work on once the move is stable.
A secure certificate matters here as well. If your old blog served HTTPS and your new one does not, you lose trust and rankings at once. Our piece on SSL and SEO explains why, and free SSL is included with our plans.
When something goes wrong
Most problems after a Blogger import fall into four groups.
- Missing images. Some posts still load pictures from Google's servers. Re-run the import on staging after clearing the failed attempt, or fix the posts individually.
- Broken formatting. Blogger's editor adds inline styles and line breaks. Your theme may render them differently. Fix the worst posts by hand and leave the rest.
- 404 errors. These show up in the Search Console Pages report. Add a redirect for each one that has traffic or links.
- Something broke on the live site. Restore from backup. We have a guide on how to restore WordPress from a backup via your host, a plugin or FTP.
Our perspective
Most Blogger migrations fail on the boring parts, not the import. People spend an evening on the plugin, then switch the domain with no staging copy, no backup and no redirect check.
We design our hosting around that. Every plan comes with free migration, daily backups and free SSL, and your site is looked after by SRE and DevOps engineers in the EU and US. WordPress hosting adds staging tools, so you can run the whole import where visitors cannot see it, fix what breaks, and only then go live.
A blog is a long-term asset. The platform you move it to should give you speed (LiteSpeed and LSCache), security that runs automatically, and renewal prices that match what you saw at signup. That is the standard we hold ourselves to.
Ihor
A hosting plan built for this move
If you are ready to leave Blogger, start with a WordPress home that has staging, daily backups and free SSL. Our WordPress hosting plans come with free migration and a 30-day money-back guarantee, and the WordPress install is simple enough for a first-time site owner.

If you also need a domain for the new site, you can register or transfer one from the same dashboard through our domain services.
FAQ
Can I move Blogger to WordPress for free?
WordPress itself is free software, and the importer plugins described here have free versions. Your costs are hosting and, if you need one, a domain. Some plugins limit the free version, for example one importer caps the free tier at 20 posts, per the WPBeginner guide. Check the limit before you start a large import.
Will I lose my Google rankings?
You can protect them. Keep the same address if you use a custom domain, import with a plugin that creates 301 redirects, and submit your sitemap to Search Console. A temporary dip is common while Google re-indexes, and it is smaller when redirects are correct.
Do my comments and pages come across?
Blogger says its Takeout file can be used to import posts, pages and comments. What actually lands in WordPress depends on the importer plugin you use. Test on staging, then rebuild whatever is missing by hand.
Should I delete my Blogger blog after the move?
Not until you have checked everything. Keep it live while DNS settles and you confirm posts, images, redirects and Search Console are in order. Only then decide what to do with the old blog.
Can I keep my blogspot.com address?
No. That address belongs to Blogger. If you were using a custom domain, you keep it and point it at your new host. If you were on blogspot.com, you need a new domain for WordPress.
Sources
- Back up or import your blog - Blogger Help
- mnasikin/btw-importer on GitHub
- How to Move From Blogger to WordPress Without Losing Google Rankings, WPBeginner
- Post-Migration Verification Checklist, ServMask
- How to Move Blogger Blog to WordPress Without Losing SEO, Income Affairs
- How to Migrate From Blogger or Wix to WordPress, Aurora WP Theme
