HTTP vs HTTPS duplication where HTTPS is non-existing

[gamajunova]

Hey Guys,

**My site is **http://www.citymetrocarpetcleaning.com.au/

Goal: I am checking if there is an HTTPS version of my site (duplication issue)

What I did:

1. I went to Screaming Frog and run https://www.citymetrocarpetcleaning.com.au/. The result is that it is 200 OK (the HTTPS version exists - possible duplication)

2. Next, I opened a browser and manually replace HTTP with HTTPS, the result is "Image 1" which doesn't indicate a duplication. But if we go deeper in Advanced > Proceed to www.citymetrocarpetcleaning.com.au (unsafe) "Image 2", it displays the content (Image 3).

Question:

1. Is there an HTTP vs HTTPs duplication here?

2. Do I need to implement 301 redirection/canonical tags on HTTPS pointing to HTTP to solve duplication?

Please help! Cheers!

uIgJv DsNrA El7aI

[Joe_Stoffel]

Hi There!

The best practice here would be to implement those 301 redirects to prevent the possibility of duplicate content. It does not appear that any https://www. pages are in Google's index now (screenshot) but the potential is there with both http://www. and https://www. URLs being able to resolve and the fact that they both contain self-referencing canonical tags.

I would recommend making the switch to https:// given Google's recent announcement regarding the 'Not Secure' warning in Chrome 62 starting October (All http:// pages with forms will be marked as 'not secure' - more on that here).  This warning will be triggered on every page due to the 'request a quote' form in the right-hand sidebar. If you are interested in looking into this further, I recommend checking out this 'Secure your site with HTTPS' Search Console Help article.

Hope this helps!