Web browsers have changed the way they handle non-HTTPS websites, and more changes are on the way. If you already have our Whole-Site SSL add-on, you’re covered. Otherwise, read on to see how these changes affect your website, and what to do about it.
Web browsers Chrome and Firefox, which account for more than 70% of web traffic, have started warning users to varying degrees when they visit non-HTTPS websites, and those warnings will become more prominent over time.
Below are examples of how these browsers display websites that have HTTPS and those that do not.
First, this is how your customers will see your site if you add Whole-Site SSL:
Next, this is how your customers will see your site today if you don’t have Whole-Site SSL:
That looks harmless, but if a visitor clicks the “i” for more info, they’ll see something like this:
And it’s already been announced that in the future, Chrome, the most popular web browser, will display non-HTTPS websites like this:
In fact, Chrome already displays non-HTTPS pages this way (though not in red) if those pages ask for a password or credit card number.
Don’t let web browsers scare away your customers and shoppers.
To stop browsers from displaying these warnings on your website, add Whole-Site SSL today for just $9/mo. Simply click here or email your account manager.
And don’t just take our word for it. Adding HTTPS on your whole website is recommended by Safeco, Google, and countless others. Safeco’s SearchSore checks for HTTPS, and Google even gives a slight ranking boost to HTTPS websites, helping you with SEO.
Why wait?
If you want Whole-Site SSL but your agency doesn’t have a website from Banyan Theory yet, head over to our pricing page and sign up.
It’s important to note that if your insurance agency website is hosted by Banyan Theory and you don’t have Whole-Site SSL, your website’s forms are still protected with SSL, but the rest of the pages on your website are not. We made Whole-Site SSL available in response to the browser changes described above. More details on how we handle SSL are here.