What are the pros of using https when no sensitive data in at stake?

General
1

Closed. This question is not about programming or software development. It is not currently accepting answers.

This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.

Closed 5 days ago.

Improve this question

I’ve been maintaining some documentation websites for a few years, all using https, and all of them being read-only.

What are the factual pros of using https in that context, i.e. when no sensitive information is ever sent from the client to the server?

My question is fundamentally tied to the fact that every single article or opinion that I read on the subject asserts that https MUST always be used. I’d like to understand why everybody seems to agree on this.

Just to be clear: I’m not asking for opinions. I’m asking for facts, that can be backed up by articles and studies. I’m asking what https bring to websites that don’t transmit sensitive data to the server.

2

Even for read-only, non-sensitive websites, using HTTPS brings the following factual, documented benefits:

1. Integrity – Prevents content tampering

  • HTTPS ensures your site’s content can’t be altered in transit by ISPs, attackers, or proxies (e.g. injecting ads or malware).
  • Example: EFF report — ISPs and hotels have injected ads and tracking scripts into HTTP sites.

2. Privacy – Hides user activity

  • HTTPS encrypts the URL path and query params, so third parties can’t see which pages users are visiting.
  • Without HTTPS, anyone on the same network (Wi-Fi, ISP) can see every page request.
  • Source: Google Transparency Report

3. Trust – Modern browsers label HTTP as “Not Secure”

  • Users are warned if a site uses HTTP. This damages trust, even if the site is harmless.
  • Chrome, Firefox, Safari all show visible indicators or warnings for HTTP.
  • Google Chrome: Marking HTTP sites as “Not Secure”

4. SEO – Google ranks HTTPS sites higher

  • Google confirmed HTTPS is a ranking signal.
  • Even small SEO gains matter in competitive contexts.
  • Source: Google Webmaster Blog

5. HTTP/2 and newer web features require HTTPS

  • HTTP/2 (faster loading) is only supported with HTTPS in most browsers.
  • Features like Service Workers (offline support), Push API, and PWA also require HTTPS.

Summary:

Even if your site doesn’t handle sensitive data, HTTPS protects your users, improves performance and SEO, and avoids browser warnings. These are technical facts, not opinions.