Thu Mar 30, 2017 4:19 pm
The techs are planning it all out in case it's a go - that planning alone is a huge job. For anyone wondering what all the issues are, read this...
https://www.link-assistant.com/news/htt ... study.html
Your sites aren't as complicated as this case study, but it gets pretty complicated when so many folks are doing so many different things, not to mention C2, Infin It!, etc.
We'll automate 80-90% of your work (ex., moving images into secure folders, internal linking, etc.), but there's some (if you're using outside resources) that you'll have to follow detailed help for.
All in all, it's a minor issue for a typical content site. The only really significant reason to do this is if the majority of other sites move that way. If a "lemming effect" takes place, we'd have to follow right along. If, as has happened many times in the past, it's just too much work for too many sites, it won't be a factor.
Google can't really disadvantage a majority of sites that don't use it, especially if they don't really need to be using it. There are no security risks in reading straight content. So even if they ever made this a minor factor, they'd almost surely scale the factor to the type of site.
There are other issues such as Stripe (see Harvey's post above), but there are other ways to work around those (not to mention lots of others ways to do transactions). Another - Browser notifications would become annoying if the majority don't go secure - no one wants to annoy users/diminish their product for something that is not of major importance for a majority of sites.
Bottom line: The dev plan is being put in place so we'll be ready to go if and when we need to do this. My gut feel is that we'll end up doing this, being a follower and not a leader on this. It's not a dev that I want to do (since ther are always other projects on the plate) unless it's truly needed.
If/when we do it, it'd be done well before it would become a Google factor.
All the best,