In this episode we touch base on the big changes that were planned with SSL. Has Chrome updated yet to flag non https sites as insecure? What can you expect to happen if you delay the update?

https://youtu.be/Ny9D7o_5in8Resources for this Episode

Add these two lines to your htaccess file unchanged and they will help with the http -> https redirectRewriteEngine On RewriteCond %{HTTPS} offRewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Darryl: Hi and welcome to The My Bloody Website podcast, where we talk about all things online, especially for small and medium business owners or marketers. I'm Darryl King, and I've been running a web agency for over 25 years. I’m here with my co-host Ed Pelgen. He has been running his online marketing agency for just as long. Our goal is to cover things in a way anyone can understand, and can improve how you’ll use online for your business. This is Episode 37 - July 26, 2018 and it’s titled “What happen with SSL?” Hey Ed how you going?

Edmund: Good mate. Yourself?

Darryl: Yeah really good, really good, I enjoyed our last few episodes. Now we went on a bit of a tangent; sort of challenging people to you know think about stuff. There was some really good traction on a couple of those that; I don't know and for whatever reason; they’ve got a lot of little lessons a lot of sharing and stuff so that was great. Today we're gonna get back into the nuts and bolts. What’s been going on in online kick-start world?

Edmund: Mate, I've been doing a lot of audits lately looking at campaigns for people, making sure things are working. It's been really quite interesting some lots of insights actually maybe; maybe; we'll share them in one of these episodes in the next few weeks

Darryl: excellent; excellent, well this; This episode I want to talk about this week, is timely. Like we're at the end of July, the 1st of July there were some changes, and we hopped on it and I look back and we first hopped on episode 2. Which is a little while ago; where we talked about SSL and just [1:33 coughing] and we've talked about it on the way through, when we talk about things that people need to do, when we're talking about you know making sure your website's going well. But July 1, 2018 was when chrome update came out, and started marking sites, that didn't have SSL implementation done properly, as insecure.

Edmund: well, actually it's chrome 68 which is the actual version that's updating, and its pending update now. I've been trying to check and check, but you're right. The difference between 67 and 68 - sorry for those who are looking for technicalities - 67 shows a little— gosh I'm getting slow. A little icon. A little circular icon.

Darryl: Yep

Edmund: which indicates that it's not secure. Sixty-eight, oh, sorry 67. 68 will actually show “not secure”, so that’s gonna be a [kick up? (2:19)]

Darryl: Yeah; yeah, that's the big one that's, you know, gonna make a big difference. And so I think, what we really want to do - is make people understand, just in simple terms, what the impact is. And I've seen a lot of people sort of being more cognizant of it, like we've talked about it for a while, but now that people are starting to see it. Now that there was a date put out, like everyone heard July 1; which is why I use that day, and it's of course its dependant on whether you update chrome; you know, if you don't have updating Chrome

Edmund: Absolutely

Darryl: you won't see it straight away, but there are other impacts as well, and there's going to be impacts as far as what's showing up in search results.

Edmund: hmm-what one thing I want, what I think you should talk about is - why people still keep screwing up the migration. Because, I've...almost every campaign that I've looked at, in the last two or three months, where they've either done a migration to SSL, or they still...they said they've implemented SSL, and it's not working on a site. They’re constantly screwed up, you know.