HTTPS (stands for Hyper Text Transfer Protocol Secure) is the secure version of HTTP. It is a protocol over which data is sent between your browser and the website that you are connected to. And the communication between your browser and the website remain encrypted – leading to secure browsing.

Recently Google advised all the webmasters to move their sites to HTTPS browsing for offering a secure experience to the visitors.

In his latest article on HTTPS, MOZ columnist JR Ridley has talked about the pros and cons of HTTPS services.

Addressing Google’s concern over implementation of HTTPS, Ridley says, “Google’s singular focus in this area is to provide a better user experience to web visitors by improving Internet security. On its surface, there’s nothing wrong with this movement. However, Google’s blatant disregard for the complexities this creates for webmasters leaves a less-than-pleasant taste in my mouth, despite their good intentions.

Luckily, there’s a bit of a silver lining to these HTTPS concerns. Over the last few years, we’ve worked with a number of different clients to implement HTTPS on their sites using a variety of different methods. Each experience was unique and presented its own set of challenges and obstacles. In a previous post, I wrote about the steps to take before, during, and after a migrationbased on our experience. In this post, my focus is instead on highlighting the pros and cons of various HTTPS services, including non-traditional implementations”.

Pros and Cons of HTTPS Services: Traditional vs Let’s Encrypt vs Cloudflare


Sharing is caring