Back when I wrote the article “Why Everyone Should Upgrade to HTTP/2” it was meant to raise awareness of an awesome protocol update that I thought was an easy win for making a website faster.
Since then, I’ve talked to hundreds of business owners and SEOs about upgrading, done dozens of upgrades, and solved dozens more. I realized there was still one big hurdle for business owners and SEOs: HTTPS. The problem with HTTP/2 is that most browsers only support this new protocol over a secure connection, which means you need to migrate your website to HTTPS.
Yet with all of this push for a more secure web, the fact remains
It seems like everyone is trying to Germany Phone Number make switching as easy as possible by removing barriers to entry, like cost. Let’s Encrypt offers free certificates (Sidenote: I’m very amused that Google Chrome has the only nofollow on its paid referral link after being called.) Many web hosts and CDNs also offer free security certificates to encourage people to make the change, but a lot of people are still not moving.
Google identifies several reasons to switch to HTTPS in its website migration guide:
There are other benefits though, including the previously mentioned Google ranking boost.
The switch also prevents a lot of bad stuff, like when AT&T injected ads into their hotspots. They could not have injected these advertisements on a website with HTTPS.
Switch from HTTP to HTTPS
- Start with a test server . This is important because it allows you to do everything right and test without messing it up in real time. Even if you make the change without a test server, there is almost nothing you can do that you can’t recover from, but it’s always better to have a plan and test everything beforehand.
- Explore the current website for the current status of the website and for comparison purposes.
- Read any documentation for your server or CDN for HTTPS . I run into a lot of funny CDN issues, but it can also be simple.
- Obtain a security certificate and install it on the server