HTTPS is the future of the internet, providing security, getting that cozy "Secure" lock on your browser and enabling a speedy future with HTTP/2. Forcing HTTPS helps secure our content and gives our users confidence to use our products. In 2016 WordPress even added HTTPS support to the minimum requirements for web hosts. But what if your site is already on HTTP? What if it contains hundreds of blog posts full of content and plugins importing content from outside sources? There's a lot to consider including all the absolute URLs to images in your database, outside links to your site, your google analytics account, setting up page redirects and testing to make users aren't seeing mixed content warnings. This session will cover lessons learned from forcing HTTPS on four separate WordPress websites.


Comments are closed.

Lots of info. No dead time. Well presented. Slides have plenty of links in situ to the resources talked about. Explains what the problem is, why you need to switch up to HTTPS, What the terminology is, steps to take, and the downsides (besides the bother of doing it, none.) I feel like I can go home and upgrade my WordPress sites to HTTPS, using her slides as a guide. I feel like it would have been a lot of work to figure all these steps out myself. Good responses to questions. Suggestion for the slide deck: use way fewer words, and larger fonts. (Except the resource links don't need to be bigger.)