Tiffany Kuchta: Moving to HTTPS

Continue the discussion

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Published

June 19, 2017

In 2014, Google rather quietly announced that they were planning to start using HTTPS as a ranking signal. In the months since, you may have noticed an increase in the number of encrypted sites you use daily. You may have also noticed changes in the way Chrome alerts users about the presence of encryption. Google’s changes are leading the charge on security, helping push website owners and developers to HTTPS as standard. Of course we all want more security (right?), and while a variety of tools can be used to help you transition your site, there isn’t a one-size-fits-all solution to this problem for existing WordPress builds not designed to use HTTPS. You’re going to need a solid plan, and a few more than 5 minutes to transition legacy WordPress content to effectively use HTTPS. We’ll discuss why encryption even matters if you’re not processing credit cards or social security numbers. I’ll share our typical process, identifying common missteps and tricks as well as how to future-proof for new content.

Takeaways:

What is HTTPS? And why you should care if your site is using it.
How to smoothly transition a WordPress site that is not currently HTTPS to HTTPS.
How to prepare your WordPress site for a future of exclusively HTTPS assets.

Presentation Slides »

Rate this:

Event

WordCamp Asheville 2017 31

Speakers

Tiffany Kuchta 2

Tags

HTTPS 12

Language

English 5396

Download
MP4: Low, Med, High
OGG: Low
Subtitles
Subtitle this video →
%d bloggers like this: