Keep Your Blogger URLs in WordPress

If your Blogger blog uses a custom domain, you can keep every old link working. Point the domain at WordPress, then either match Blogger's /YYYY/MM/slug.html addresses in your permalink settings, or add one redirect rule that sends every old address to its new one.

If your blog lives on a blogspot.com address, that address stays with Google, and you can't install a redirect plugin there. You still have options, but each one has limits. We checked the Blogger, Google and WordPress details below on 13 November 2026, on their own websites, in WordPress's code and on live Blogger blogs.

How Blogger builds addresses

On the live Blogger blogs we checked, every address followed the same pattern:

• Posts: yourdomain.com/2026/07/your-post-slug.html. The year and month are when the post was first published. A post published in July and edited in August stays under /2026/07/.
• Pages: yourdomain.com/p/about.html.
• Labels: yourdomain.com/search/label/Recipes.
• Mobile: phones get the same address with ?m=1 on the end, so people who share from their phone often share links like .../your-post-slug.html?m=1.

Custom domain or blogspot.com

Which section applies to you depends on your blog's address:

• A custom domain, such as www.yourdomain.com. You can move it to WordPress. Google says that once a custom domain is set up, your blogspot.com address redirects to it. We saw that on live blogs: old blogspot.com post links answered with a 301 redirect to the custom domain.
• Only a blogspot.com address. The address belongs to Google. Skip to the blogspot.com section further down.

Save your list of addresses first

Blogger publishes your post addresses at yourdomain.com/sitemap.xml and your page addresses at /sitemap-pages.xml. On the blogs we checked, the post sitemap listed every published post. Open both and save a copy. They disappear once your domain points to WordPress, and you'll use them to test your links after the move.

On a custom domain: match or redirect

Import your posts first, with their original slugs. Blog Porter does this: it takes each slug from the old address, so /2026/07/your-post-slug.html becomes the slug your-post-slug. Then choose one of these two setups.

Option A: one redirect rule (recommended)

Use clean WordPress addresses such as yourdomain.com/your-post-slug/, and redirect every old Blogger address to them with one rule.

1. In WordPress, go to Settings → Permalinks, choose Post name and click Save Changes.
2. Install the free Redirection plugin. It makes server-side 301 redirects and logs 404 errors.
3. Add a redirect, tick Regex, and enter:
   • Source URL: ^/\d{4}/\d{2}/([^/?]+)\.html
   • Target URL: /$1/
4. Add a second rule for pages, if you recreate them with the same slugs: source ^/p/([^/?]+)\.html, target /$1/.

The $1 is replaced with the part in brackets, the slug. Because the rule doesn't end in $, an old link ending in ?m=1 matches too. Test one to make sure it lands on the clean address.

This option doesn't depend on your post dates, which is why we recommend it. Google's guide to site moves with URL changes says to keep redirects for at least a year, so leave the rule in place.

Option B: match Blogger's addresses exactly

WordPress can reproduce Blogger's pattern. Go to Settings → Permalinks, choose Custom structure and enter:

/%year%/%monthnum%/%postname%.html

WordPress fills in %year% and %monthnum% from the post's date and %postname% from its slug. Old links then work with no redirect at all.

That only works if every post's date is in the same month as its old address. Blog Porter keeps each post's original publish date, so they normally match. Compare a few posts with the sitemap you saved and correct any that differ, or use Option A.

Two more things to check with this option:

• Duplicate slugs. Blogger keeps addresses apart by year and month, so the slug alone doesn't need to be unique there. WordPress gives each post a unique slug, adding -2 to a repeat. Look for slugs ending in -2 and redirect the old address by hand.
• Mobile links. WordPress uses m as its own date filter, so a link ending in ?m=1 asks it for posts from the year 1. Open a few old links with ?m=1 on the end. If they show "not found", add the Redirection rule from Option A.

Labels and other details

• Label pages. Blog Porter imports labels as WordPress tags. Redirect your busiest /search/label/... addresses to the matching tag pages, such as /tag/recipes/. Google says not to send lots of old addresses to an unrelated page, such as your home page.
• Links inside your posts. Blog Porter doesn't rewrite links. Links to your own old posts keep working through the redirects, but you can update them with a search-and-replace plugin.
• The blogspot.com address. While the custom domain stays set up in Blogger, Blogger sends blogspot.com visitors to it. Google doesn't say what happens once the domain points somewhere else, so test an old blogspot.com link after the move.

Your feed

People who follow your blog in a feed reader use Blogger's feed address, /feeds/posts/default (Google). On the blogs we checked, /atom.xml and /rss.xml worked too. Once your domain points to WordPress, those addresses reach WordPress, which doesn't use them.

WordPress's main feed is your site address with /feed/ on the end. In Redirection, add one more rule with Regex ticked:

• Source URL: ^/(feeds/posts/default|atom\.xml|rss\.xml)
• Target URL: /feed/

If your importer adds redirects

Some import plugins set up redirects themselves, as their own pages described it when we checked:

• BtW Importer adds 301 redirects for posts at /YYYY/MM/slug.html, and only if your blog keeps the same domain.
• Blogger Import Wizard has a setting that points old Blogger addresses at the new ones.
• Blogger Importer Extended says it can set up 301 redirects from old Blogger links.
• Feed Importer for Blogger doesn't redirect, but saves each post's old address so you can add redirects with another plugin.

Blog Porter doesn't create redirects, so use Option A or B. Whichever tool you use, test the old addresses the same way after launch.

On a blogspot.com address

Your posts are moving to a new domain, so every old address needs to point to its new one, and you can't run a redirect plugin on Google's server. Here's what's possible.

Blogger's custom redirects

Blogger has a Custom redirects tool under Settings → Errors and redirects. Google's help page describes it for sending the address of a deleted post somewhere else. A Blogger Product Expert's guide in the Blogger Community says it can make 301 redirects to a different website too, but warns that this may breach Blogger's content policies.

Each redirect covers one address, so for a large blog this means a lot of manual entries. If you try it, test a few posts first and keep a list of what you added.

Redirects in your Blogger theme

You can edit your theme's HTML so that each post page sends visitors to the matching address on your new site. These are client-side redirects, which Google's site move guide calls a last resort. Google says it treats an instant meta refresh as a permanent redirect, and to use JavaScript redirects only when neither a server redirect nor a meta refresh is possible, because it might never see them.

Blog Porter keeps each post's slug, so the new address can be built from the old one. Back up your theme first.

A notice and a link

The simplest option is to leave the Blogger blog up with a note on each post that links to its new home. Google calls this a crypto redirect and says not to rely on it to tell search engines your content has moved. It still helps readers who arrive from old links.

Your feed on blogspot.com

In Blogger's Settings, under Site feed, enter your WordPress feed address, such as https://yourdomain.com/feed/, in Post feed redirect URL. Google says Blogger then redirects all post feed traffic to that address, so your subscribers keep getting your new posts.

Whichever you choose, keep the Blogger blog published. If you delete it, every old link breaks, and any image still loading from Google goes with it.

After launch

1. Open a sample of old addresses from your saved sitemaps: a few posts, including your oldest, a page, and a link ending in ?m=1. Each should show the right post. Where one redirects, a redirect checker should show a 301, not a 302.
2. 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.
3. In Google Search Console, submit your new sitemap. If your domain changed and you have 301 redirects from the old home page, Google's Change of Address tool tells it about the move.
4. Watch Search Console for pages Google can't find, and fix the old addresses behind them.

How to migrate Blogger to WordPress puts these steps in order with the rest of the move.

Move the posts with Blog Porter

Blog Porter imports your Blogger posts into WordPress with their original slugs and publish dates, so a single redirect rule can cover every old address. Labels come across as tags, and each post keeps its author. It reads your public blog directly, with no export file, and downloads the images in your posts into your Media Library, in resumable batches.

It costs $0.20 per post, with a minimum of 5 posts, paid once. The free analysis lists the posts it found and the exact price before you pay. Blog Porter doesn't create redirects, and it doesn't move pages, comments or your theme.

Install the Blog Porter plugin to run the free analysis.