How to move from HTTP to HTTPS: A checklist

How to move from HTTP to HTTPS: A checklist

What does it mean to move from HTTP to HTTPS? Wait, what is HTTPS? How does it impact you as a person? Let me give you a scenario which may explain this.

Are you a blogger or a small business owner? Perhaps you have a shop online where you sell products and need people to enter their credit card information. Or maybe you are a blogger who gets traffic to your website on a regular basis with people leaving comments, connecting with you and maybe you’re even working with brands or advertisers.

I finally made the move from HTTP to HTTPS! But it wasn't without the help of a fabulous tech support team. Find out what HTTPS is, whether you need it and how to switch today! #Bloggers #Blogging #Tips

Now imagine a person landing on your page and getting a message that says , ‘Warning: This site is not secure. Information entered here can be hacked.’ What would you do if you were the customer? Turn around and leave, of course! Whether you are a blogger or a business, you don’t want people to leave. That, my friends, is the number one reason you must make the move from HTTP to HTTPS.

What is HTTPS and why do I need it?

Before we get started, I must make a resounding disclaimer. I am not a tech-savvy person, not in the way you’d imagine. I learn a lot through blogging and of course, Google, but I cannot code or manually overwrite commands in a complex algorithm. So whatever you read here today is based on my personal experience as a blogger who made the move to HTTPS.

So, why read this then? For two reasons.

One, I can explain to the best of my ability, what is HTTPS and why you need it.

Two, I will be talking about the team that helped do all the heavy lifting on the back end and provided round-the-clock support right through the shifting process. So stick around.

HTTPS: What is it and why you need it for your #blog Click to Tweet

What is HTTPS?

To put it in very simple terms, HTTPS stands for Hyper Text Transfer Protocol Secure. For instance, this means that the data that is sent from my website (shailajav.com) to the browser (Google Chrome), is now secure. Hackers and other middle men will find it more difficult to break into your site. This gives users a sense of relief.


Do I need HTTPS for my blog/website?

Short answer: Yes. Security is just one benefit of HTTPS. The others include:

  • Google indexes your site higher in search results, so you have a competitive edge
  • Your site is made AMP-ready (Accelerated Mobile Pages)
  • Mobile views of your site will be indexed better
  • You have a better experience to offer your users (think of how safe you feel when you visit a banking site)

*For more details, check out this site: 5 Reasons why HTTPS should be enabled on your website


How do I know if my site is HTTPS-enabled?

Enter any website’s name in the browser, using your desktop or mobile. We typically don’t type in ‘http’ when we do this, but that gets resolved automatically by the browser. Now, notice if there is a green padlock icon at the beginning of the URL. It should look like the one in the image below. If yes, that means the site is secure.

If not, there will be an ‘i’ inside a circle. When that is clicked you will get a message that says ‘Your connection to this site is not secure’.


WordPress and Blogger: Do they have the HTTPS option?

Blogger’s platform has two options, as you may know. There is the free option and there is the custom domain option.

  1. Free domain: This means you have a blog that has the URL: www.xyz.blogspot.com Now, if that’s the case, you are in luck. You have the option to make the switch to HTTPS very easily. Check this tutorial and follow the steps exactly as mentioned: Switch to HTTPS
  2. Custom domain: This means you are still on blogger but you’ve paid to get the  ‘blogspot.com’ removed from the URL. So it may be www.xyzl.com. If this is the case, then, unfortunately, there is no option to make the switch to HTTPS. You’d have to move to self-hosted and then make the switch.

On WordPress, you have the choice between WordPress.com and WordPress.org. Most bloggers start off on the free WordPress platform. For instance I started off as shailajav.wordpress.com.

  1. WordPress Free: If your blog is abc.wordpress.com, then this site is already secure. Nothing needs to be done.
  2. WordPress Custom domain: If you have paid  for masking or removing the wordpress.com from your URL but have not moved to self-hosted, that means you have a custom domain. So it would be www.shailajav.com, for example. Good news! This, too, is secure! No effort required on your part.

WordPress.org or the self-hosted option is when you have your website on WordPress but have chosen an external hosting provider such as Bluehost or Siteground or Amazon or GoDaddy. This is what I have for both my blogs: www.shailajav.com and www.shailajav.in

I bought the hosting from BlueHost last August for this blog and at the time, I did not buy the SSL certificate. So it fell to me, thanks to the October 1st deadline announced by Google, to make the shift to HTTPS as soon as I could.

How I made the shift to HTTPS

Well, first I panicked, because I had no clue how I would go about it! Then, after I calmed down, I checked Bluehost and was thrilled to discover that they were offering free SSL certificates for everyone who was hosted with them! Considering I have two blogs and needed it for both, this was a huge relief!

(Rajlakshmi, a fellow blogger, has written a very succinct description of the way she moved from HTTP to HTTPS here using Bluehost. You can check it out).

If you are slightly more tech-savvy than I am, I recommend this tutorial as well: Moving to HTTPS Guide

Move from HTTP to HTTPS: A handy checklist Click to Tweet

Here’s a handy checklist of things you can check if you are going to do it either on your own or with a tech support team. For this process, I went with HostMyBlog, as I had been very impressed with some support they had provided for me back in June. I am thrilled to say they came through yet again!

HTTP To HTTPS Checklist:

  1. Buy and install the SSL certificate from your hosting provider or a third-party provider.  (I got it for free from Bluehost)

  2. Back up your website before making any changes. Use a backup plugin like BackWpUp or UpdraftPlus.

  3. Check and install the certificate.

  4. Set up HTTP to HTTPS redirect.

  5. Update Google Analytics and webmaster search console.

  6. *Optional: Get a paid social media plugin to restore social media share counts. I loved this feature! When you move from HTTP to HTTPS, you lose all share counts because Google doesn’t track the old URL. I bought Easy Social Share at a one-time fee and was thrilled to see the share counts restored for all my social media accounts on each post, including Twitter!

If the above steps are freaking you out, relax. That’s where HostMyBlog comes in. So here’s what I did.

 How HostMyBlog handled the move from HTTP to HTTPS

  1. I had to give them access to my Bluehost control panel as well as my WordPress dashboard. You can do so by changing your password temporarily for this process.

  2. I told them what I needed in the free consutation e-mail that they provided.

  3. They started the process after getting the green signal from me.

  4. Using Team Viewer, they could remotely access my screen and check which plugins I wanted to retain, which ones to discard and if there were any issues I faced. This is something I really appreciated since I had to login with my username and password.

  5. They remotely updated my Google Analytics dashboard as well as my search console. (These effectively tell you about the traffic you get to your website).

  6. The move from HTTP to HTTPS was done!

From start to end, there was zero downtime and absolutely no glitches on my site. I was thrilled at how seamless it had been. If you’re even slightly worried about things going wrong, I recommend going with HostMyBlog. (This is not a paid promotion, by the way. I volunteered to write this post as a sign of gratitude).

*Featured image courtesy: Shutterstock

***

About HostMyBlog and services provided

  1. Domain + Web Hosting – They provide domain names & web hosting that come with free SSL Certificate.
  2. Theme Customization – This includes web development, logo design and a premium theme of your choice.
  3. Annual WordPress Maintenance – This is a premium support service availed by many top bloggers. It includes daily backups, security, troubleshooting, tweaks, updates and lots of maintenance work.
  4. #RepairMyBlog – This can include blog migration, http to https, URL fix and any WP related issues.

As a special and exclusive offer for readers of my website, HostMyBlog is giving a discount coupon valid on the above services till the 31st of December, 2017. The code is applicable as follows:

  1. Domain + Web Hosting: 15% off
  2. Theme Customization: 25% off
  3. Annual WordPress Maintenance: 10% off
  4. #RepairMyBlog: 10% off

**How to avail of the coupon**

  • Subscribe to my blog by entering your e-mail address in the subscription box below this post.
  • Use the coupon code ‘SHAILAJAV‘ when you reach out to them.

*Disclosure: This post contains affiliate links to the Bluehost programme. If you decide to buy the hosting through this link, I will get a fee as commission, at no extra charge to you. If you do buy it, I thank you for the same.



Top post on IndiBlogger, the biggest community of Indian Bloggers

1,084 total views, 15 views today

Comments

comments

14 thoughts on “How to move from HTTP to HTTPS: A checklist

  1. Loved your excellent explanation of all the technical details. I now realize what was missing from my post thank you so much for the mention. It’s so sad that there’s no option for custom blogger blogs. I will have to self host my travel blog now.
    Bluehost made the transition so simple. I was surprised how easy the move was.
    Rajlakshmi recently posted My Sister’s love for 50 kg of Poultry FeedMy Profile

    1. Yay! Coming from you that means a lot, Raj. I was hoping it didn’t sound wrong and I meant to include the point that people should reach out and correct me if I have made any technical errors. Yeah, that’s bad about the custom domain. I don’t know why Google does this it to its own native blogging platform!

      Super happy with Bluehost and the support they provide 🙂

  2. Thanks Shailaja. Now at least I understand why I need to get this done. The other bits remain a mystery. To me all it means is that I should get in touch with Host My Blog. I hate it when I get caught in the technicality of it all.

  3. Nice exhaustive post, Shailaja. Luckily, I had the husband who did the move for all the 3 blogs for me. I handled the GA and SC changes. Thank you for all your inputs that helped me when I was doing them. I still have so much to read on this and have not been able to find the time to do so.
    Rachna Parmar recently posted That Subdued and Lonesome DiwaliMy Profile

    1. Thank you so much, Rachna! Easy social is fairly simple to set up and their support team is also very active. You can ask Sid about Social warfare if you want to get feedback. Remember to deactivate existing share plugins when you install a new one, so there’s no conflict. And whee, so glad the https is done for us both! Good thing your husband helped out

    1. Oh dear, I didn’t mean for it to come across as complicated! It was quite simple actually. But I needed help with the social media share buttons and updating the URL to re-direct so that way, HostMyBlog stepped in. 🙂 Glad to hear yours was straightforward and stress-free 🙂

  4. Thank you for the nudge and then this post. I was able to transition so smoothly. Though I lost my social media count, it’s okay 🙂
    Really appreciate the message today <3 Hugs!

Leave a Reply

Your email address will not be published. Required fields are marked *

CommentLuv badge

error: Content is protected !!
%d bloggers like this:

Parenting and Blogging Tips by email? Sign up here.

Once a week, you'll get a new post and once a month, a newsletter with features and updates.

Thank you for subscribing.

Something went wrong.