# Any consequences to "Requiring HTTPS" (Both are active currently)

**URL:** <https://community.hubspot.com/t/any-consequences-to-requiring-https-both-are-active-currently/10326>\
**Category:** Tips, Tricks & Best Practices\
**Created:** [September 20, 2018, 4:33pm UTC](https://community.hubspot.com/t/any-consequences-to-requiring-https-both-are-active-currently/10326 "2018-09-20T16:33:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![PSM](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/psm/32/17277_2.png) [@PSM](https://community.hubspot.com/u/PSM)\
**Post date:** [September 20, 2018, 4:33pm UTC](https://community.hubspot.com/t/any-consequences-to-requiring-https-both-are-active-currently/10326/1 "2018-09-20T16:33:51Z")

</div>

I haven’t clicked the “Require HTTPS” because I’m unsure of any unkown consequences. I’ve changed a bunch of links from HTTP to HTTPS, and I’m not concerned if a couple pages show up “Not Found” since I can get that corrected quickly.

Are there any issues I should be aware of other than the URL fixes?

My fear is, I require HTTPS and suddenly I see my rank plunging for some strange reason.

Hopefully its an unfounded fear.

I appreciate any advice or heads up you could provide.

Thank you,

Shannon

---

<div class="post-metadata">

**Author:** ![Phil\_Vallender](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/phil_vallender/32/48924_2.png) [@Phil\_Vallender](https://community.hubspot.com/u/Phil_Vallender)\
**Post date:** [September 21, 2018, 8:16am UTC](https://community.hubspot.com/t/any-consequences-to-requiring-https-both-are-active-currently/10326/2 "2018-09-21T08:16:49Z")

</div>

Hi @PSM

Require https creates a wild card redirect from http urls to https urls. So any pages that resolve at http currently, should continue resolving at https.

One thing to be aware of is mixed content issues. If your site uses asets that are pulled in from non-secure sources, these can cause rendering issues and security warnings for users.

I’m not 100% how much this impacts SEO, but it definitnly degrades the user experience.

Check out this article for more info: [Resolve mixed content warnings on an SSL site](https://knowledge.hubspot.com/articles/kcs_article/cos-general/how-do-i-resolve-mixed-content-warnings-on-an-ssl-site?_ga=2.88950610.898997105.1536908800-1119211941.1536433913)

Hope this helps.