What is the best way to deal with https?

[adarsh88]

Currently, the site I am working on is using HTTPS throughout the website. The non-HTTPS pages are redirected through a 301 redirect to the HTTPS- this happens for all pages.

Is this the best strategy going forward? if not, what changes would you suggest?

[CommT]

Hi,

It sounds as though you have done everything right.

BUT - (this is a bug-bear of mine) Google doesn't display breadcrumb rich snippet info on https pages.

Also, some directories won't link to https pages (not ever seen this as a major issue because it's usually the spammy directories that do this)

Amelia

[FedeEinhorn]

Thomas, he already said that the HTTP site is being 301 redirected to its HTTPS version. So why adding all that about how to do 301s on Apache on nginx?

[BlueprintMarketing]

I normally would have agreed with Federico I did some checking and I personally would go with the 301 redirect the other thing I would do when you're doing this is move your server to Nginx it's much faster and uses much less RAM.

My reasons being that you want the site to be consistent. The 301 redirect will do that there is a chance of inconsistency with Canonical tags as the server does not have to obey it.

https://sites.google.com/site/onlyvalidation/page/301-redirect-https-to-http-on-apache-server

http://www.elevatedsearch.com/how-to-301-redirect-https-http-htaccess/

http://searchenginewatch.com/article/2288690/How-and-When-to-Use-301-Redirects-vs.-Canonical

If you do decide to make the change this is a handy tool

http://www.anilcetin.com/ This converts Apache redirects to Nginx redirects.

sincerely,

Thomas

[FedeEinhorn]

Then you are all set!

[adarsh88]

Canonical tags, when in place, point to HTTPS currently.

[FedeEinhorn]

What you are doing is completely alright.

Make sure your canonical tags are set properly to point to the HTTPS versions of the pages.

Hope that helps!