How to Migrate Blogger to WordPress

To migrate Blogger to WordPress, set up WordPress on your own hosting, bring your posts and images across with an importer, then keep your old addresses working with matching permalinks or 301 redirects before you point your domain at the new site. Blogger's backup is now a feed.atom file from Google Takeout, and WordPress's own Blogger importer was built for the older .xml file, so choose a tool that reads the new file or your live blog. Keep the Blogger blog published until every post, image and old link checks out on WordPress.

We checked every claim about Blogger, Google, WordPress and the plugins below on 13 November 2026, on their own websites and on live Blogger blogs.

Which route fits you

• A handful of posts: copy and paste them. It's free and you control every detail.
• Free, and you're happy to test: use a free plugin that reads Blogger's feed.atom backup, then check the result carefully.
• You need your comments in WordPress: pick one of the importers that lists comments. Most don't.
• Dozens or hundreds of posts, with no file to export: Blog Porter reads your public blog directly and shows the exact price before you pay.
• You'd rather not do it yourself: ask a WordPress host or agency, and ask exactly what they move.

Whichever you choose, the steps after the import are the same: images, permalinks, redirects, your feed, your domain and Google.

Every way to move Blogger to WordPress, compared

This is what each option's own page said on 13 November 2026. We haven't tested the third-party plugins.

None of these moves your Blogger theme or gadgets. You choose a WordPress theme and rebuild your sidebar instead. How to export your Blogger blog goes deeper into Blogger's backup and the importers that read it.

Before you start

1. Back up your blog and your theme

In Blogger, go to Settings → Back up content → Download. Google sends your blog through Google Takeout, as a feed.atom file with your posts, pages and comments. Save your design separately: Theme → the down arrow next to Customize → Backup (Google's steps).

Why: it's free, it's your copy if anything goes wrong, and it's the file most free importers need.

2. List what you're moving

Count your posts and pages in the Blogger dashboard. Note your labels, comments, gadgets, menus and anything in your sidebar.

Why: most tools move posts, and some move pages or comments. Knowing what's left lets you plan that work now, instead of finding the gaps after launch.

3. Save a list of your addresses

Open yourblog.blogspot.com/sitemap.xml for your posts and /sitemap-pages.xml for your pages, or the same files on your custom domain, and save both.

Why: after launch you'll test these old addresses, and the files disappear once your domain points to WordPress.

4. Get hosting and install WordPress

Use self-hosted WordPress, the free software from WordPress.org, on a hosting plan. On WordPress.com, installing plugins needs a paid plan, and most of the routes above are plugins.

When you compare hosts, check they support what WordPress recommends: PHP 8.3 or later, MySQL 8.0 or MariaDB 10.11 or later, and HTTPS. Blog Porter itself needs WordPress 6.4 or later and PHP 7.4 or later. WordPress says many hosts can install WordPress for you, so ask yours before doing it by hand.

Build the new site before you move your domain. Make sure you're an administrator who can install plugins.

Why: the posts need somewhere to land, and you can check everything on WordPress while your Blogger blog stays live.

5. Choose a theme

Your Blogger theme stays on Blogger. Pick a WordPress theme from the theme directory or your host, and look at how it shows posts, tags and featured images.

Why: if your theme expects a featured image on every post and your importer doesn't set one, your blog's home page will look empty. It's easier to choose with that in mind.

Move your posts and images

6. Check your blog is public and its feed is full

This matters if your route reads the live blog, as Blog Porter and Blogger Import Wizard's address option do. In Blogger's Settings (Google: blog settings):

• set Reader access to Public
• under Site feed, set Allow blog feed to Full. Short sends only about the first 400 characters, and Until Jump Break stops at your jump break.

You can change these back after the import. A feed redirect, such as FeedBurner in Post feed redirect URL, doesn't get in Blog Porter's way. It asks Blogger for its own feed.

Why: Google says site feeds don't work with private blogs, and a short feed means short posts.

7. Import your posts

Do this before you move your domain. Once your domain points to WordPress, the live Blogger blog is no longer there to read.

With Blog Porter:

1. Install the Blog Porter plugin in WordPress.
2. Choose Blogger and enter your blog's address, either yourblog.blogspot.com or your custom domain.
3. Run the free analysis. It lists every post it found and the exact price before you pay: $0.20 per post, minimum 5 posts, paid once, so a 100-post blog costs $20.
4. Start the import. It runs in resumable batches inside WordPress, so an interruption doesn't send you back to the start.

Blog Porter reads your blog's public feed. Blogger serves it 25 posts at a time, with a link to the next page, and Blog Porter follows every page. It imports each post's title and content as WordPress blocks, its original slug and publish date, its labels as tags and its author, and downloads the images in your posts. See what Blog Porter moves from Blogger.

Know its limits before you start:

• It moves published posts only. Drafts, scheduled posts, pages and comments stay on Blogger.
• It reads up to 5,000 posts from one blog.
• If an author's Blogger profile is hidden, Blogger lists them as "Unknown", and their posts are assigned to your WordPress user.
• It sets each post's first image as its featured image. If your theme shows the featured image above each post, that image appears twice; turn it off in the theme, or remove one copy. It doesn't move Blogger's search descriptions.

If you'd rather use a free importer with your feed.atom file, How to export your Blogger blog walks through the options.

Why: compare the post count with your Blogger dashboard before you start. If they match, nothing is missing.

8. Bring your images across

Search your WordPress posts for googleusercontent. Blogger stores post images on Google's servers. On the live blogs we checked, they loaded from blogger.googleusercontent.com or another googleusercontent.com address. Every result is an image still loading from Google.

• Blog Porter downloads each image at the size shown in the post into your Media Library, and lets you retry any that fail. Blogger usually links an image to a larger copy on Google's servers, and that link stays as it is. Remove those links, or point them at the copy in your Media Library.
• Other importers vary. Check the table above.
• Pasted images keep loading from Google. WordPress says to select each one and use Upload to Media Library in the block toolbar, or it may stop displaying once the original is moved or deleted.

Why: images left on Google depend on a blog you'll eventually stop maintaining.

9. Check dates, authors and labels

Compare a few posts with the sitemap you saved. The year and month in each old address, /2021/04/..., is when the post was first published. Blog Porter keeps each post's original publish date, so they should match.

Labels come in differently depending on the tool: as tags with Blog Porter and Feed Importer for Blogger, and as categories with Blogger Import Wizard and WordPress's importer. Decide whether you want categories as well, and add them now.

Why: readers see the date, your permalinks may depend on it, and your tag and category pages become new addresses for Google to find.

10. Spot-check a sample of posts

Open a few old and new posts side by side: title, date, formatting, images, videos, links and lists. With Blog Porter, check colored text in particular. Tables come across as tables, but the text colors, font sizes and alignment set in Blogger's editor are dropped.

Why: problems are easier to fix before visitors and Google arrive.

11. Rebuild what isn't moved

Recreate your pages with the same slugs, add your menus and sidebar, set featured images if your theme needs them, and decide how you'll handle comments. If you rely on SEO titles or descriptions, add them with your SEO plugin.

Why: these are separate jobs, so give them their own time before launch.

Keep your addresses and your traffic

12. Set your permalinks

Blogger posts live at /YYYY/MM/slug.html, and pages at /p/slug.html. In WordPress, go to Settings → Permalinks and choose one of these:

• Match Blogger exactly. Choose Custom structure and enter /%year%/%monthnum%/%postname%.html. WordPress fills in the year and month from the post's date and the name from its slug, so old links work with no redirect.
• Use clean addresses and redirect. Choose Post name, then add one redirect rule that sends every old /YYYY/MM/slug.html address to /slug/.

Keep your Blogger URLs in WordPress has both setups, the exact redirect rules, and the catches: duplicate slugs and the ?m=1 that Blogger adds to links on phones.

Why: if old links land on the right post, you keep your search traffic and your inbound links.

13. Plan your redirects

What you can do depends on your address:

• A custom domain, such as www.yourdomain.com, moves with you. Match the old addresses or redirect them on WordPress, with server-side 301 redirects. Google recommends server-side permanent redirects straight to the new address, kept for at least a year.
• A blogspot.com address stays with Google, and you can't install a redirect plugin there. Blogger's custom redirects and theme edits are possible, but each has limits.

The URL guide covers both. Redirect each old address to its own new address, not to your home page. Google warns that redirecting many old URLs to one irrelevant page confuses users.

Why: without redirects, old links and search results lead to "not found" pages.

14. Redirect your feed

Readers who follow your blog in a feed reader use your Blogger feed. WordPress's main feed is your site address with /feed/ on the end.

• On a custom domain: Blogger's feeds live at /feeds/posts/default (Google), and on the blogs we checked, at /atom.xml and /rss.xml too. After the move, those addresses reach WordPress. In the free Redirection plugin, add a redirect, tick Regex, and enter the source ^/(feeds/posts/default|atom\.xml|rss\.xml) and the target /feed/.
• On blogspot.com: in Blogger's Settings, under Site feed, enter your new WordPress feed address in Post feed redirect URL. Google says Blogger then redirects all post feed traffic to it.

Why: your subscribers keep getting your new posts without having to find you again.

15. Move your custom domain

Blogger's setup points your domain at Google with a CNAME record to ghs.google.com and, for the domain without www, four A records. At the company where your domain is registered, replace them with the records your WordPress host gives you.

• Keep the same address. Blogger custom domains use a subdomain, such as www. If your blog was at www.yourdomain.com, set WordPress's Site Address in Settings → General to the same, so none of your addresses change.
• Lower your TTL first. Google suggests lowering your DNS TTL to a few hours at least a week before the switch.
• Import first. Finish the import before you switch, as in step 7.

Why: until the domain points at WordPress, visitors still see the Blogger blog.

After launch

16. Test your old addresses

Open the addresses you saved in step 3: a few posts, including your oldest, a page, and a few links with ?m=1 on the end. Each should load the right post, or redirect to it in a single step. A redirect checker should show a 301, not a 302.

Why: it's the quickest way to catch a missed redirect or a permalink that doesn't match.

17. Tell Google

1. In WordPress, go to Settings → Reading and make sure Discourage search engines from indexing this site is unticked. While it's ticked, WordPress turns off its sitemap.
2. In Search Console, submit your new sitemap. WordPress's built-in sitemap is at /wp-sitemap.xml, unless an SEO plugin replaces it.
3. If your domain changes and your old home page redirects with a 301, use the Change of Address tool. Google says you must be an owner of both the old and new sites in Search Console.

Why: Google says to keep your sitemaps updated with the new URLs, and the sitemap helps it find them.

18. Watch Search Console for a few weeks

Look for pages Google can't find or index, and fix the old addresses behind them.

Why: Google says to expect temporary fluctuation in rankings during a move, and that a medium-sized site can take a few weeks or more before Google shows the new URLs. A dip isn't always a problem, but a growing list of errors is.

19. Decide what to do with the Blogger blog

Keep it published while any redirect depends on it, or while a googleusercontent search of your WordPress posts still finds images you care about. On a blogspot.com address, add a note to your posts that links to your new site. Blogger lets you restore a deleted blog within 90 days, and after that it's gone.

Why: Blogger is your fallback copy, and it may still be serving some of your images and old links.

Frequently asked questions

Will I lose my Google rankings if I move from Blogger to WordPress?

Expect some movement for a few weeks. Google says rankings fluctuate temporarily during a move. What protects your traffic is that every old address still works: matching permalinks or one 301 redirect per address, a new sitemap in Search Console, and keeping the redirects for at least a year. On a custom domain you can keep every link working. On a blogspot.com address it's harder, because the address stays with Google.

Can I keep my blogspot.com address?

No. A blogspot.com address is part of Blogger, and Blogger has no setting to point it at another site. You'll need your own domain for WordPress. Your old address can still send people on, through Blogger's custom redirects, a theme edit, or a notice with a link. Keep your Blogger URLs in WordPress compares them.

Is it free to move from Blogger to WordPress?

The WordPress software is free and open source, and several importers are free. You still need hosting, and a domain if you don't already have one. Some importers charge for larger blogs or extra features, as the table above shows. Blog Porter costs $0.20 per post, paid once, and the analysis that shows the price is free.

Does WordPress's Blogger importer still work?

Not with a new Blogger backup. WordPress's documentation tells you to upload Blogger's XML export. Blogger now gives you a feed.atom file through Google Takeout, and WordPress ticket #64207 reports that the importer fails with it. The plugin's page says it hasn't been tested with the latest 3 major WordPress releases. If you still have an old .xml backup, it's worth a try.

My Blogger backup is too big to upload. What can I do?

File importers take your backup through an upload form, so your host's upload limit applies. Feed Importer for Blogger, for example, lists a 64MB upload limit in its requirements, and WordPress warns that very large import files can exhaust your server's memory. Ask your host to raise the limit, or use a route that doesn't need the file. Blog Porter and Blogger Import Wizard's address option read your public blog instead.

Will my images move to WordPress?

Only if your importer downloads them, or you upload them yourself. Otherwise they keep loading from Google's servers. After any import, search your posts for googleusercontent to find what's left. Step 8 covers this.

Can I move my Blogger comments?

Yes, with some routes. Blogger's backup includes your comments. Of the plugins above, Blogger Importer Extended lists comments, Blogger Import Wizard imports them in its Pro version, and WordPress's own importer does with an old .xml backup. Blog Porter doesn't move Blogger comments.

How long does the move take?

The import itself depends on your route and the size of your blog. Allow time for the steps around it: checking posts, rebuilding pages and setting up redirects. After launch, Google says it can take a few weeks or more before it shows your new addresses.

Should I delete my Blogger blog afterwards?

Not straight away. Keep it published until your posts, images and redirects all check out. On a blogspot.com address, any redirect you set up runs on Blogger, so deleting the blog ends it. If you do delete it, Blogger lets you restore it within 90 days.

Every Blogger guide, in order

1. How to migrate Blogger to WordPress: this page, every route and every step in order.
2. How to export your Blogger blog: Blogger's backup, the importers that read it, and what each route misses.
3. Keep your Blogger URLs in WordPress: match your old addresses or redirect them, on a custom domain or blogspot.com.
4. Install the Blog Porter plugin: set up the plugin and run the free analysis.