According to my host (who I initially blamed for this), SSL was automatically turned on by cPanel updates. This is a HORRIBLE practice and it should default to off not on. For months I was unaware that SSL had been turned on automatically by cPanel, therefore I couldn't respond in time to the SEO damage it has already caused my site. Not everyone wants/needs SSL, or has sensitive data on their site to protect.
This has done irreversible damage to my site's traffic (and lost ad revenue) now that -- since their algorithm is thinking we are an HTTPS compatible site -- Google has started indexing the wrong page version (https instead of http). So now my site is fragmented into 2 parts -- http and https, getting "trying to load dangerous scripts" errors, etc etc. This has even caused important scripts to stop working on my post popular page. And of course this just HAD to happen during the absolute busiest time of the year for my site, when I was about to take my site to the next level as far as amount of traffic (I was getting 40,000/day, now it's down to 20k and sinking). Again, thanks cpanel!!
Thank you cPanel for the the huge headache I didn't need, when I'm already backed up spending many hours redesigning my site and features, and the financial damage this dumb setting has created. How 'bout next time you let us choose our settings instead of assuming everyone needs https enabled.
This has done irreversible damage to my site's traffic (and lost ad revenue) now that -- since their algorithm is thinking we are an HTTPS compatible site -- Google has started indexing the wrong page version (https instead of http). So now my site is fragmented into 2 parts -- http and https, getting "trying to load dangerous scripts" errors, etc etc. This has even caused important scripts to stop working on my post popular page. And of course this just HAD to happen during the absolute busiest time of the year for my site, when I was about to take my site to the next level as far as amount of traffic (I was getting 40,000/day, now it's down to 20k and sinking). Again, thanks cpanel!!
Thank you cPanel for the the huge headache I didn't need, when I'm already backed up spending many hours redesigning my site and features, and the financial damage this dumb setting has created. How 'bout next time you let us choose our settings instead of assuming everyone needs https enabled.