Quote from: ergophobe on August 11, 2016, 08:03:16 PMVery true gents. It was pure HTTP until a limited number of non existent HTTPS pages listed in the index. Checked all the 301's (all dating back to 2015) nothing obvious that would affect approx 4% of pages from a 3000 page site. Started about 3-4 weeks ago (when I noticed the issue). May have been when WC2.6 was released or a kin. Thinking about it a google analytics plugin went on the fritz around about then also. No idea where google is getting the https from, screamingfrog finds none. Hence why I'm thinking to buy a certificate and turn the entire site https; least the currently index https pages will resolve properly rather than pick up penalties. The EV cert was just trying to stand out a little. My logic is probably skewed on the matter.Quote from: Drastic on August 11, 2016, 05:34:18 PMAgreed. And check your redirect hops. Our devs originally set it up so that each redirect action, including http -> https was a hop. So if we had a URL that was used in print in the form
I think you should have your entire site either SSL or not, and not doing so is causing you problems. If you want ssl, all your http should redirect to https.
