In the last year or so, you may have noticed a lot of websites moving from HTTP over to HTTPS. Now, there are a couple of good things in terms of moving over from HTTP to HTTPS and good implications from an SEO standpoint, but also from a user experience standpoint as well. What are the implications of doing this, and why should your website migrate across to HTTPS, and what implications does that have on SEO? You’re going to learn all about that coming up.
Hey there, guys, Darren Taylor of thebigmarketer.co.uk here, and my job is to teach you all about search engine marketing. If that’s up your street, you should consider subscribing to my channel. In this video, we are looking at the HTTP versus HTTPS discussion and what the implications of SEO are on those factors. First of all, what does HTTP even mean? HTTP stands for Hypertext Transfer Protocol. It’s, essentially, a way of transmitting information across the web. When you go to a website and that website information is transmitted to you, it’s via HTTP, the Hypertext Transfer Protocol. What is HTTPS? The S is just secure, so it just means it’s a more secure version of that protocol.
Therefore, your data within that transfer process is encrypted and your site is verified. By encrypting and verifying your data, Google likes this. Generally speaking, Google likes anything that helps protect the user. By moving your website from HTTP to HTTPS, you may experience a small boost in rankings, not necessarily a big one, especially if all your competitors are already on HTTPS, but if they’re not and you do this, you might experience a good ranking boost. That extra security and credibility in terms of that SSL certificate, which is the certificate you need to verify and encrypt your data with HTTPS, gives Google a good hope that you’re doing things in the right way and protecting the users’ information.
In fact, Google have gone ahead and made changes to their Chrome browser that if you access a website with no HTTPS protocol and only go for an HTTP protocol, it warns you with that warning triangle that you see next to the URL saying your data is not protected. That’s always been the case across the internet, but for Google to take that step and say explicitly within the browser, “This information is not protected,” that can put the user off, and you don’t want to put off your users because, again, it will give them a bad user-experience. SEO and bad user-experience are so closely linked now.
You maybe asking yourself are there any negative implications of moving over from HTTP to HTTPS? The answer is no. There are no negative implications of doing this if it’s done properly. If you manage your migration from HTTP to HTTPS properly, meaning that when someone goes to your website on any given page and they put in the HTTP version of your website, they should be successfully redirected to the HTTPS version of your website. If you manage these redirections and make sure everybody gets to the right place perfectly, then there’ll be no negative implications. In fact, there’ll only be positive implications.
However, if you manage this incorrectly and there are two versions of your site live or there’s one version that’s got a bad response code because it’s not valid, then there’s massive issues for your website, so you’ve got to make sure you manage the migration properly. If you need help, speak to an expert on how they can help you manage your migration as opposed to trying to model for it yourself. Guys, get on and do this. There’s only benefits doing this from a Google perspective and from a user perspective. That’s all you need to know. Get going and make sure you do the migration.
Thanks for watching this video. If you liked it, please leave a like below. Let me know in the comments whether you are thinking of migrating from HTTP to HTTPS. More important than that, don’t forget to subscribe. Check out the other content on my channel and I’ll see you guys on my next video.