Welcome to WebmasterWorld Guest from 126.96.36.199
Forum Moderators: phranque
More and more hosts are making it easier to freely install & use certs for their hosting customers.
That is not a fact based statement, more along the line of a conspiracy delusion. There is no evidence supporting anything like that scenario.
HTTPS is not a requirement .... yet. That's all the OP asked. :)I didn't ask that, but IMO I see no indication that HTTPS will be "required" and by who? However, eventually browsers may drop support for nonsecure sites. I guess we'll find out.
I think it will take a long time to switchA large portion of the world's web sites probably won't switch. Many sites are not maintained and have become archaic. This might end up being an affective method of getting rid of the dead wood from indexes.
Careful, HTTPS encrypts the content of pages, not the URL itself (or at least not the IP or Host).
The underlying problem is the mechanism used by certificates. Something more like ssh where everyone always issues there own keys - or the option of doing either - would be far preferable.
[edited by: robzilla at 10:47 am (utc) on Feb 23, 2017]
Specifically, we’ll start crawling HTTPS equivalents of HTTP pages, even when the former are not linked to from any page. When two URLs from the same domain appear to have the same content but are served over different protocol schemes, we’ll typically choose to index the HTTPS URL if:
- It doesn’t contain insecure dependencies.
- It isn’t blocked from crawling by robots.txt.
- It doesn’t redirect users to or through an insecure HTTP page.
- It doesn’t have a rel="canonical" link to the HTTP page.
- It doesn’t contain a noindex robots meta tag.
- It doesn’t have on-host outlinks to HTTP URLs.
- The sitemaps lists the HTTPS URL, or doesn’t list the HTTP version of the URL.
- The server has a valid TLS certificate.
I understood it this way that if the page does not exists in BOTH sitemaps Google will prefer the secured one.
The general consensus seems to be that nowadays, if the implementation is correct, moving to HTTPS should not result in a loss of rankings, traffic or revenue.
I don't understand what that means.
Whether the links lose any value from the redirect of HTTP to HTTPS is a matter of debate, but I doubt it