HTTPS as a ranking signal
googleonlinesecurity.blogspot.com
HTTPS as a ranking signal
1–10 of 212 posts
Re: HTTPS as a ranking signal
#2Hopefully this will take into account the supported TLS versions and ciphersuites as well. It's sad to see sites that only supports TLS 1.0 and prefers a CBC ciphersuite.
Re: HTTPS as a ranking signal
#3If only webmasters had an option to change http:// to https://, the entire move would have been slightly easier as "fetch as googlebot" returns "redirect" since we direct http:// to https://.
Apart from that, we've had no ranking loss for their keywords.
Re: HTTPS as a ranking signal
#4Re: HTTPS as a ranking signal
#5I don't get it. I have a website that is purely content and available to everyone. It has no user accounts, no sign-ups, no nothing but static pages. Why should I use HTTPS for that? To prevent man-in-the-middle attacks?
Re: HTTPS as a ranking signal
#6Re: HTTPS as a ranking signal
#7I don't get it. I have a website that is purely content and available to everyone. It has no user accounts, no sign-ups, no nothing but static pages. Why should I use HTTPS for that? To prevent man-in-the-middle attacks?
Re: HTTPS as a ranking signal
#8Quick question though. There was no mention of the type of certs used. Will plain certs be worth less than EV certs?
Hopefully Matt or any other Google search representative here can comment.
Re: HTTPS as a ranking signal
#9I don't get it. I have a website that is purely content and available to everyone. It has no user accounts, no sign-ups, no nothing but static pages. Why should I use HTTPS for that? To prevent man-in-the-middle attacks?
Re: HTTPS as a ranking signal
#10Bonus points if they allow a single bad site to tarnish the reputation of all sites under a milti domain cert.
We could have had this from the start if domain names weren't essentially free via domain tasting. But hey, better late than never.