: How to make HTTPS not a ranking signal on an information-based site According to google, they say that HTTPS based sites deserve a higher ranking signal than those with only HTTP. Many sites
According to google, they say that HTTPS based sites deserve a higher ranking signal than those with only HTTP.
Many sites still use HTTP and HTTP is faster than HTTPS because HTTPS requires an additional handshake which increases the time-to-first-byte of a page.
Google goes on to explain in their own way how HTTPS works here: support.google.com/webmasters/answer/6073543?utm_source=wmx_blog&utm_medium=referral&utm_campaign=tls_en_post
They claim no one can listen to one's conversation over HTTPS, however I think anyone can hack any system (even HTTPS). Heck, even texts on cellphones can be hacked.
They also claim data over HTTPS cannot be corrupted without being detected, but I don't understand how HTTP is any different in this regard.
And they think that with HTTPS, it can be proven that users communicate with the intended website, but I believe some kind of man-in-the-middle attack (or data corruption) can happen at any point during the HTTPS session (even in the DNS lookup stage).
I apologize if I am bashing HTTPS hard. Whoever invented HTTPS may be trying to make the internet more secure, but there are hackers who can get into anything and everything.
So my question then is, how do I make it where google doesn't use HTTPS as a ranking signal for websites whose sole purpose is to provide general non-secretive information to the whole wide world?
More info on HTTPS
One website claims that HTTPS does NOT make a website more secure, and:
Ever since Google made their announcement that they were exploring the idea of using HTTPS as a Ranking Signal for your SEO, the web has gone nuts for HTTPS. For a number of security professionals it’s generated groans and a heightened level of annoyance and consternation at what has become an over abundance of irrational thought, perspective and improper guidance and insight.
see: perezbox.com/2015/07/https-does-not-secure-your-website/
More posts by @Angela700
1 Comments
Sorted by latest first Latest Oldest Best
Generally IF you pay for something you care for that something. Google ranking position trust for https sites is not so much about "secure" (in my view) as it is about your paying for SHA2 certs. It is not enough to say "I have ssl" and so I am secure. As goes security with https - the most important thing is to host with a known firm that has a first rate team which checks whether their servers are exposed to the attack on a hourly basis. Google does NOT tell us to host our sites with "secure" hosting. Hence my argument that ssl is a fiscal means for trust.
Also, I must disagree:
Https and http operate AT THE SAME speed. In fact https could be said to be faster as the content (to make the page work) has to come from a dedicated IP.
See: www.httpvshttps.com/
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.