All are tedious, complicated and unappetizing, but they are nothing compared to migrating a blog from Blogger to WordPress.org without having nightmares and losing hair.
So, because this is not a trivial task, I have set out to create the definitive guide that will help you migrate Blogger to WordPress with hosting in a much more bearable way and without causing you headaches.
This guide is born from a compilation of all the bumps that I have found while migrating my blog and that did not appear in any guide on the Internet.
Although this is my particular case, this guide should be 100% complete. However, if you see details that I have not covered or things to improve, do not hesitate to leave a comment
The migration process is going to be divided into 9 steps:
At this point I assume that you have a blog hosted on Blogger and that you want to migrate it to WordPress.org. We are going to differentiate two different cases:
- Your blog has a contracted .com domain and your URL is of the type: http://www.tubtubname.com
- Your blog does not have its own domain and your URL is of the type: http://tubname.blogspot.com
If you have contracted a .com domain with Google, there will be parts of the process that will be a bit more tedious. These parts will be indicated in the appendix at the end of the post.
The entire process of installing, configuring, and customizing the WordPress.org blog has already been covered extensively in other articles on this blog, so we won’t go into it further. In any case, links will be provided for those who need a more exhaustive vision of these points.
The migration of a blog between two platforms requires the interaction of 4 independent services:
It is possible that specific problems appear with one or several services, in which case the best option will be to speak to the technical service of the same.
In general, completely migrating a blog from Blogger to WordPress can take some time, especially if complications arise. Therefore, it is better to assume from the beginning that, depending on your case, it may take some work. Of course, I guarantee it is worth it.
If you have any questions, leave a comment and we will do our best to help.
So that, let’s migrate!
1. Web domain
First of all is mastery; the address that you put in the explorer, come on.
If your blog doesn’t have a contracted own domain yet, this step is trivial; it can be done automatically when hiring the web hosting. Anyway, it may happen that you want to contract it with a separate company, such as GoDaddy or Namecheap; especially if you have several domains and you prefer to have them all contracted with the same service.
The next thing will be to hire a hosting to host your website.
As good but affordable hosting options, I recommend Ionos, BlueHost, SiteGround or Hostgator. In the links you have more information about plans and prices, and you will see we are talking about very affordable amounts in the basic plans.
Basic plans are usually more than enough for something like 98% or 99% of cases. So for sure you don’t need more.
Within this, although they are all good options, my recommendation is Ionos.
We chose Ionos, above all, for:
- Its speed and reliability
- Your good technical support
- It is a specialized WordPress hosting(and also in Joomla and Prestashop).
- They take special care of security with things like 4 -hour backups and WordPress – specific anti-hacking settings
- The possibility of hosting the blog in a temporary domain during the migration
In this video you can see how to hire Ionos hosting:
If you already have a .com domain…
The issue of time domain is key, I highly recommend it. Thus, you will be able to configure and start the new blog easily while regular readers visit the old one.
Also, I recommend that you hide content from the general public during this period with a plugin such as Ultimate Coming Soon Page.
If your blog already has its own .com address and you don’t want your visitors to come across a page under construction while migrating, this option is perfect. If, on the contrary, your blog keeps the original address of Blogger, it gives you a little the same.
If you decide to choose not to take a temporary domain, you had better choose a very low moment of traffic to do the migration. Since for a long time your blog will be a real disaster, I would choose something like 2 in the morning at night from Saturday to Sunday to minimize the number of unexpected visits.
3. Installation of WordPress.org
Once you have the hosting contracted and ready, the next thing is to install WordPress.org in it. In Ionos there is an automatic installation pack, but you can also do it in the “standard” way, common for any hosting
However, in the other options that I recommended, ionos, SiteGround and Hostgator works exactly the same since they all use the popular cPanel hosting management tool.
4. Personalization and configuration of the blog
Then comes the magic of installing the template and configuring the blog as best suits you, in short, completing the WordPress installation. For this, you can consult the details of this post to which I have already referred you before
Anyway, there are two configuration details that we are going to point out, given their importance:
- Visibility for search engines
- Permanent links configuration
Visibility for search engines
An important point to avoid problems with Google. To prevent the new website from being indexed at the same time as the old one and finding duplicate content, it is important to deactivate the option of being tracked by search engines in the blog settings, or use the plugin to hide the previously recommended content. .
You can find it in the menu Settings -> Reading
Permanent links configuration
By default, WordPress configures the permalinks of the blog in the format:
From the point of view of SEO and blog aesthetics, having links in this way is not the best option; therefore, we recommend changing the structure to one of the type:
Stylish and easy to remember. In addition, part of the adjustments that we will make later require that the links be arranged in this way.
To do so, all you have to do is go to Settings -> Permanent links and select the “Entry name” option.
The rest of the blog I leave it to your good judgment, which you will surely leave very cute
5. Import content
At this point in the migration we have:
- org installed
- Personalized and configured blog
Now let’s go to what really matters: migrate our blog content from Blogger to your new home, WordPress.org.
Courage, there is less left!
Due to some changes that Blogger has made on its platform, the “classic” WordPress import plugin described below has stopped working.
Luckily, there is no problem because the Blogger Importer Extended plugin works in a very similar way and is an excellent alternative as long as the problem is not solved with the original plugin.
Importing Blogger content into WordPress is really easy. From the WordPress desktop, go to Tools à Import, and once there, click on Blogger:
This will take you to the plugin download page:
Once installed, we go back to Tools -> Import -> Blogger and a screen like this will appear:
Here we must authorize the Google account with which we are registered as authors in Blogger:
We allow access and we will already have at our disposal the importer’s control panel:
We click on the button and wait for the process to complete. This can take a while, depending on how big your blog was. When you finish you will see something like this:
And that’s it! Now you have your old blog copied to your new home.
6. Content review
Now that we have our imported blog, it’s time to check that the import has been done properly. Automatic import has four basic problems:
- Line breaks are lost
- The authorship of the posts is assigned to a single user
- Images lose quality and captions fall out of photo
- Tags go into categories and it all gets a little messy
If you weren’t using line breaks, if you were just an author, or if your blog images weren’t too important, you might want to overlook these details.
Changing authorship, labels and categories can be done easily with the “Bulk Edit” tool. For this:
- Go to Tickets -> All tickets
- Select the entries you want to edit together
- Click where it says “Batch Actions”, select “Edit” and then “Apply”
- Modify at your whim
Correcting photos and line breaks is a bit tedious, because you have to go through the entries one by one to put the line breaks in place and replace the images with their higher quality version. Fortunately, WordPress imports the original images, so there’s no need to re-upload them, just re-index them.
In the case of my blog we are two authors, we have line breaks and the photos have a fundamental weight, so we are still working. What is costing us the most is replacing all the low-quality photos with the original version. It’s a careful beating, so if anyone has better advice, they’ll be well heard.
Apart from these 4 points, it is convenient to give a general review of the entries to verify that there have been no other errors in the import of content. Each blog is a world and each one will have its little problems.
7. Web domain redirection
Now that we have the blog ready to go, it’s time to bring it to light. For this, we are going to point the domain to the hosting where we have hosted the blog.
If your blog had the original address of Blogger (http://blogname.blogspot.com) and you have hired in domain along with hosting, you can skip this step because your new website will already be operating under the domain you chose.
If you have a .com domain…
The next step will be to redirect your web domain to your brand new blog. To do this, we access the administration console of our domain with the manager with whom we have contracted it and change the fields indicated by our hosting provider.
For example, in the particular case that our domain manager is GoDaddy and our hosting provider, Ionos, it will be necessary to change the name servers in the DNS control panel, so that you point to those of Ionos:
Highlight that this is for the particular case Ionos – GoDaddy. For each combination of Hosting – Domain Manager you will have to proceed in a similar way, although the user interfaces of the providers will be somewhat different.
In any case, remember that with a good hosting provider like Ionos, in all these details your technical support assists you, so in this case you should never have any problem. So don’t be afraid of these things.
Also, if during the installation, configuration and migration phases you were working under a temporary domain, you will have to carry out an internal link replacement process.
During the entire import process of the posts, the internal links that previously redirected to your old Blogger pages were changed to the new domain. There is only one small problem … that the new domain is not the good one either, it was a temporary one.
To solve this, Ionos offers a plugin that automatically changes the internal links that pointed to the old domain to the new domain. The specific instructions are provided by email when you hire their services and they are really clear and easy to use.
8. Redirection of links
Blogger and WordPress.org have different link structures. Let’s put a real example to understand it well.
In we have a recipe called “How to make sauce”. Blogger’s old address looked like this:
However, in the new version of the blog, the address looks like this:
With these types of redirects, you’re basically saying something like “Hey! This page you are looking for is no longer here. From now on, always look for it in this other link. ”
In this way your readers will be able to reach your blog through old links without any problem. Needless to say, this is ideal for SEO because you will retain all the inbound links you already had.
With the redirection of links we want to solve 2 problems:
- Guarantee that the old links to your website continue to work
- Fix small errors in the links that may have occurred during the migration
To fix this we will use the Redirections plugin, which in addition to allowing us to make 301 redirects, will also allow us to monitor 404 errors of page not found. The latter is very useful to detect possible anomalies in the incoming links that we will have to solve.
To add a new rule, simply open the control panel of the plugin in Tools à Redirection and copy the fields of the cases that I will indicate below.
Blogger links differ from WordPress.org in 3 points:
- They are dated structures
- They have .html ending
- Mobile pages end in /? M = 1
We are going to establish 2 redirection rules, one for the general structure and one for the pages optimized for mobile devices:
This redirect removes the part of the link that corresponds to the year and month of publication, as well as the ending “.html”.
- Source URL: / ( d *) / ( d *) / ([A-Za-z0-9 -] *). Html
- Destination URL: / $ 3
- HTTP Code: 301 – Moved Permanently
- Regular expression: CHECK
Mobile pages m = 1
This redirect removes the /? M = 1 termination from your mobile-optimized links to your blog.
http://www.blogname.com/yyyy/mm/name-of-your-post.html/ ? M = 1
- Source URL: /(.*)/?m=(d*)
- Destination URL: / $ 1
- HTTP Code: 301 – Moved Permanently
- Regular expression: CHECK
Adding the 2 rules, we will have a link structure nailed to that of WordPress.org:
http://www.blogname> / yyyy / mm / name-of-your-post. html /? m= 1
It looks like magic, right?
In addition to the old links, we will also have to redirect the RSS Feed.
The RSS feed is an xml file that is hosted on the blog. This file contains all the information of the posts that are published and is updated only every time new content is published. In this way, it allows obtaining information in real time from a website without having to access it. Basic uses of a feed are:
- Feedly RSS readers
- Mail campaigns that automatically send new entries
- Social aggregators
- Share new posts on social networks as soon as they are published
And if the blog RSS feed address is lost, all those visits are lost.
In our particular case, we find that the level of visits dropped dramatically. The bulk of visits to “yourblog” comes, on the one hand, from Google and, on the other hand, from recipe aggregators. On the part of Google we remain more or less the same, but we were missing the sector of aggregators (which work with RSS) and those first visits by RSS subscribers.
The blogger has the feed hosted at http://www.blogname.com/feeds/posts/default. WordPress.org, at http://www.blogname.com/feed. For redirection we will use the Redirections tool again (often a great match).
This redirect affects comment feeds.
http://www.blogname.com/ comments / feeds / dd / comments / defualt
- Source URL: / feeds / ( d *) / comments / default
- Destination URL: / comments / feed
- HTTP Code: 301 – Moved Permanently
- Regular expression: CHECK
This redirect affects standard feeds.
http://www.blogname.com/ feeds / posts / default
- Source URL: / feeds / posts / default
- Destination URL: / feed
- HTTP Code: 301 – Moved Permanently
- Regular expression: CHECK
Redirection from blogname.blogspot.com
This redirection will allow to redirect to your blog all the visits that go to your old website http://blogname.blogspot.com. For this, we will use the Blogger to WordPress Redirection plugin.
After installing it, we go to Tools Blogger to WordPress Redirection and we will find the following page
We click on the button and a list will appear with the blogs that we can redirect. This step only works if you have imported a blog from Blogger with the WordPress import tool. If you have been following all the steps in this guide, everything should go smoothly.
If we click on “Get Code”, a code box will appear.
We have to paste this code in the template of our old Blogger blog, for which we will go to the control panel of this and enter Template -> Edit HTML:
There, we will replace the code that there is with the one that we have previously generated in the plugin and save the changes. Don’t forget to make a backup copy of the original code just in case.
And with this we will have the redirection ready. As a verification, you can try entering the old address of your blog in the browser and you will see how it sends you to the WordPress version. Or if you have not migrated yet, see how http://blogname.blogspot.com/biscuit redirects you to http://www.blogname.com/biscuit/.
If you understand English and want a more detailed tutorial, you can check the one offered by the creators of the plugin. Very complete.
9. Last fringes
Migrating a blog from one platform to another is a complicated process. Above all, if your blog was already a certain age and you do not want to lose position or readers, it is a job that requires hours and a lot of care.
To polish the last fringes and try to solve problems that have been overlooked, here I recommend some extra craft actions so that everything goes as well as possible.
- Let your readers know via social media, email and even with an entry in the new and old blog when you are moving and when you have already moved. That way you won’t catch anyone by surprise.
- Occasionally check for 404 errors on the hunt for links that don’t arrive to take appropriate action
- During the first weeks you will notice a drop in visits from Google. This is normal and will recover over time as long as you keep posting and doing your homework as a good blogger.
- Remember to check all the posts you can for poor quality photos, non-existent page breaks and other problems. Everything is because your old content is as cool as the new
And nothing, thank you for reading and wish you the best of luck for this adventure that is migrating a blog. Any questions, do not hesitate to comment and we will do our best to give you a cable.
Annex I: What to do if this is beyond you or you don’t have time to do it yourself
As you may have seen in the post, migrating Blogger is not entirely trivial.
If technical things are not too good for you or you just don’t want to waste time with them, your thing is to let a professional do it for you.
Annex II: What to do if you have contracted a .com domain with Google
In the event that you already have .com domain as you have contracted with Google for your blog in Blogger you may encounter a complication that I unravel below:
For some time now, Google has been hiring web domains through GoDaddy. This means that there is already a GoDaddy account open in your name where your web domain is managed.
Only the access data is missing.
These data (supposedly) are provided by Google when you contract the domain. However, if you are as messy as I am, you will not have this data, nor will you know how to get it.
To recover them, you must first access the password recovery console of the administrator of your Google Apps account. This wonder can be found at: https://admin.google.com/blogname.com/ForgotAdminAccountInfo
From there you will have to follow a series of steps to recover your password…
Solve a Captcha:
Check the email with which you contracted the domain:
Choose new password:
He will confirm it with this message:
We can now access the administrator console at https://admin.google.com/blogname/
They will tell you to accept the legal terms…
… And that you change the password again:
And at the end you will come to a screen like this:
Now you will finally be in the administrator console. Remember that we are here because we want to get the access data of our GoDaddy account in order to have control over our DNS.
To find them, we click on the square at the top left, just below the Google logo, and select “Domains”.
Once here, we click on “Advanced DNS Configuration”:
And finally we will have reached our destination:
Google has very easy and intuitive things, but, as you can see, there are others that are to give you a couple of capons