After a long time, Blogger has come up with a new option for technical settings of the blogs, and this time, it is something that most bloggers didn't generally expect: The option to serve their blogs over HTTPS.

This indeed came as a surprise, especially on a platform like Blogger. Most people use it for blogs; generally, blogs don't require much protection against data theft. Do note that serving your blog over has nothing to do with the security of your Blogger account but to ensure that the data from your blog's domain being transferred to a visitor is more secure than the standard HTTP.

Other than the esdata's security, HTTPS have some exciting advantages; for instance, many advanced APIs in HTML5 allow sites to use features that require advanced device or application access. But that is generally insignificant for any regular or even advanced Blogger.

1. What is HTTPS, and What Does it Do

HTTPS has no significant effect on your search rankings or such or the content displayed or presented to the visitor; only how it is done is affected or improv, ed and secured.

It stands for "HyperText Transfer Protocol Secure," which clarifies its true meaning, it is secure, and yup, it makes it difficult for a hacker to steal data between the user and your blog. But these are implemented mainly on sites that require protection from potential data thefts, like a Banking Site or many sites like Google, Facebook, Twitter, etc., which have to protect a user'ss data being transferred over the air from thefts. These are some examples, but you will see the use of HTTPS not only on these popular websites but also on more business and service websites. 

Why is encrypted data so important? It is essential when transferring content that can be a subject of data theft. A website that asks for your credit card details so you can pay money, mostly HTTPS and advanced encryption to ensure that a hacker doesn't steal the data and decrypt it that might reveal the details to them. Credit card details are one example; other reasons are to protect the transfer of cookies, which might give away a way for the hackers to pretend to be you and log into a site using those cookies, and HTTPS just gives the data more protection. 

3. Should I use it?

Most people who visit a site with HTTPS sub-consciously get assurance that the site is genuine and safe to use, probably even better than competitors with only HTTP. It does help a visitor to decide physiologically whether to trust the site or not. That is different fromom a blog; most people don't expect HTTPS to be implemented on a blog they just want to read, though it doesn't harm the experience either. 

HTTPS can be helpful but, at the same time, can obstruct small things you might be doing. For example, when your blog is on HTTPS, and you are supposed to have linked an image from another site with only HTTP in its URL, the browser may give out a "mixed content" warning, which might confuse a visitor who doesn't know what's going on and might lead them away. Though those are not malicious, they might give out a feeling of it, so when you use HTTPS, you have to ensure the resources like assets, files, and images are also on HTTPS. 

On the other hand, you might also note that you should not embed content that is not on HTTPS, but this isn't a big issue if you mainly embed content from sites that already serve the secure protocol, i.e. HTTPS, like Google Docs, YouTube, and many other well-known sites. 

4. Benefits

  1. Visitors are ensured that the site they've opened is genuine and not a malicious site they've been redirected to without their knowledge. 
  2. Any person trying to manipulate the content being transferred from your blog to the visitor will find it more difficult, thus providing security to the data.
  3. If you are tech-savvy, then there are some more advantages of it that you can enjoy through the latest web technologies, e.g. the notification API, or the use of media devices through the site

5. Things to look out for

  1. If you have third-party gadgets that use resources on the general HTTP protocol, errors might arise as HTTPS suggests only resources on the same protocol be served.
  2. Only for "". It is not available by bloggers for custom domains, though HTTPS services might be available from your domain registrar. 
  3. 'http://' doesn't redirect to the secure version if someone types it in. However, when you have turned off "HTTPS Availability," your blog's URL will redirect to the HTTP even if a user types in "https://" 
If you are unsure about it, I recommend you research HTTPS and its technical aspects to make a decision; otherwise; wise, there is no harm in staying with HTTP.

It is, though, only for some. A blog, generally needed HTTneed, but this has undoubtedly come as a breeze of hope for many folks who might have wanted to have this on Blogger. So if you know what you are doing,, you are good to go.  

On a further note, I would suggest you visit this official forum thread to learn what the users have to say about this feature:!topic/blogger/AYiZ_QjkbxE