Http vs. https - duplicate content

[BeckyKey]

Hi

I have recently come across a new issue on our site, where https & http titles are showing as duplicate.

I read https://moz.com/community/q/duplicate-content-and-http-and-https however, am wondering as https is now a ranking factor, blocked this can't be a good thing?

We aren't in a position to roll out https everywhere, so what would be the best thing to do next? I thought about implementing canonicals?

Thank you

[luxresorts]

Hi Becky,

I am also faced with the same issue as you and after intensive research, I found that the best solution would be to make the server to an automatic 301 redirection for all HTTP pages to the their respective HTTPS pages.

This would enable you to preserve all SEO value of the pages and at the same time, avoid having duplicates.

However, since you have not yet moved all the pages in HTTPS, then a canonical would work the best, but this needs to be manually defined for each page, unless you have a CRM that can pull the respective absolute URL accordingly.

Hope this helps.

Tej Luchmun

[BeckyKey]

Hi Logan

Thanks this is helpful, I'll check out the article! I need to put a case together for moving to https: so that will be my next step

[LoganRay]

Becky,

The best scenario would be to roll out secure to the whole site and then apply a 301 redirect rule directing all http to https. But since you can't do that, your next best bet is going to be canonical tags. Canonicals are 'soft 301 redirects' and search engines treat them very similarly to an actual 301 redirect. I would go that route in the meantime until you're able to go secure site-wide.

This guide that Cyrus Shepard put together will be helpful when you get to the point of fully integrating HTTPS: https://moz.com/blog/seo-tips-https-ssl