@nprofile1q... I read
http://scripting.com/2026/10/05.html#a165533 - regarding "blocking Google" - what are you trying to do, block the Googlebot? Or block Chrome?
To block the Googlebot, that's relatively trivial -
https://developers.google.com/crawling/docs/crawlers-fetchers/verify-google-requestsTo block Chrome, then you're probably wanting to block anything with a useragent containing "Chrome/" from your website. Since you're hosted on Amazon S3, you can't without putting Cloudfront in front of the request (which would be cheaper for you anyway). Cloudfront's WAF would be able to block Chrome useragents.
I willingly went to https after seeing my local coffee shop literally replace the ad banners on a site I had produced with replacement ad banners that it earned money from, rather than me. That sort of thing - messing with your website's content - is impossible with https. Adding https also means that your ISP can't snoop on what page you're looking at (the only thing visible is the domain name). So it does have benefits. I totally understand your annoyance tho.