HTTPS redirecting to subdomain; do I need to 301 to HTTP first?

[alimo]

Hello there, quick question on HTTPS downgrade to HTTP.

Originally, full site was HTTPS. Redesign eliminated need for secure layer. Site currently has https 301'd to sub.domain.com.

Ideally, site would live at domain.com, but with the old site having been indexed https, the security warning triggers when you visit, hence the 301 to a subdomain.

Thinking possible solutions here are to a) add back in secure layer or b) 301 all old https pages to new http pages. Have I overlooked something?

With (a), I will see no SEO impact, correct? With (b), can I expect impact similar to a relaunch? Have seen a lot of chatter that there is some impact in switching http to https, but not much the other way.

Any help much appreciated!

[alimo]

Okay, we'll give it a whirl. Thanks so much for your help!

[FedeEinhorn]

If you MUST http all pages then a simple rewrite rule will do (if using apache).

RewriteEngine On

RewriteCond %{HTTP} !=on
RewriteRule ^/?(.*) http://%{SERVER_NAME}/$1 [R=301,L]

Users won't get warnings as that only happens when you are POSTING data from an HTTPS page to an HTTP. Just make sure any sensitive info is transmitted over HTTPS to prevent any eavesdropping.

[alimo]

Well, I just don't need it anymore because the store is secure through shopify.

Seems like the best option is to keep the https in place if I can, but if I can't... do I have to 301 all https pages to http pages? And will I still see the security warning when someone enters from an https link?

[FedeEinhorn]

Why would you remove the HTTPS if it was working good?

Pages under HTTPS may be slower if you are using a low end certificate, but it you are using a good provider, HTTPS gives a little more confidence to users.

I will consider having all the pages under HTTPS if the speed isn't affected. Run some tests and check for loading speeds.