About 4 years ago, Google started a crusade to get all websites to use HTTPS.

That means that the connection to a site that you view is secure and encrypted.

They’ve even gone so far as to start penalising websites that don’t use HTTPS. Which falls in line with their older announcements that websites delivered over HTTPS would get higher rankings.

This means that if you look at your address bar, there should be a green padlock.

Like This

Like This

I am in no way an SEO expert.

I’m not even an SEO pert

… What? That was funny. Ok, it was Fozzy bear funny. But even so.

 But Google pushing for HTTPS was always a good thing.

Why Are You Telling Us This, Jamie?

Well, it’s a weird way to announce…

If the shoe fits! Am I right?

Ignore him. Anyway, as of right now my blog (what you’re reading right now) and my website are both being served via HTTPS. This is all thanks to the amazing folks at Let’s Encrypt.

They have an amazing post on their site about how HTTPS and Certificate Authorities (CAs) work. At the very least, you should check that out.

Pitfalls

There’s a one caveat to my blog being served over HTTPS, and that’s that some of my articles link to non-HTTPS content (usually old embedded images). That means that your browser might either warn you about it, or just remove that content. I’m going to be taking a look at each post and fixing them where necessary, but this could take some time as there are over 170 published posts (at the time of writing) on here.

I also might have to change my theme, as my search bar doesn’t seem to be using HTTPS, so that’s causing a few issues.

Jamie is a .NET developer specialising in ASP.NET MVC websites and services, with a background in WinForms and Games Development. When not programming using .NET, he is either learning about .NET Core (and usually building something cross platform with it), speaking Japanese to anyone who'll listen, learning about languages, writing for this blog, or writing for a blog about Retro Gaming (which he runs with his brother)