Welcome to WebmasterWorld Guest from 188.8.131.52
Forum Moderators: open
For the past several years, we’ve moved toward a more secure web by strongly advocating that sites adopt HTTPS encryption. And within the last year, we’ve also helped users understand that HTTP sites are not secure by gradually marking a larger subset of HTTP pages as “not secure”. Beginning in July 2018 with the release of Chrome 68, Chrome will mark all HTTP sites as “not secure”.Source: A secure web is here to stay [security.googleblog.com]
Last I heard, there are no plans to mark sites as insecure in the SERPs, so people would have to notice the missing "https://" in the URL.
I suspect that at some point in the future, any unsecure site will either be significantly demoted, or removed from SERP altogether.
joined:Nov 18, 2017
Well my http sites are still doing extremely well...That's great... however this announcement appears that your HTTP site may not continue to do "extremely well" after July when Chrome warns your visitors. Don't forget, Chrome is the most used browser in the world, especially on mobile.
I may want to sell some of my sites eventually, and that might be easier if they are https.I don't see how A leads to B. Do you mean that https sites have already been through the algorithmic hiccup that comes with a protocol change, so you can safely sell them “as is”?
On the other hand, there have been reports that some sites suffered traffic losses immediately after switching to https.
I say "leave it to CloudFlare, and allow at least half a minute to make the change."And at least a half a minute to load every file. Most sites are much better off optimizing their sites & configs than sticking a CDN in front of an existing problem.
And at least a half a minute to load every file.
Most sites are much better off optimizing their sites & configs than sticking a CDN in front of an existing problem.
Sorry, but that makes no sense at all.
joined:Apr 13, 2002
...simply because it is a browser fad is beyond me...
You just need to be more informed as to why HTTPS is to your benefit
It's an exaggeration, of course, but since dynamically generated pages are not cached
Point is, a CDN is not a *fix* for not updating a site to be secure