If you isolate ALL pages on your site that need HTTPS to a single folder (or subdomain like secure.example.com) on your site and keep all HTTP pages outside of that folder it's very easy to use .htaccess to insure that all requests for pages in that folder or subdomain are HTTPS and all others are HTTP.
Unfortunately most don't think that far ahead.
PS: You have other URL canonicalization issues in addition to http vs. https. You have a similar problem w/ www vs. non-www... and also showing index.html vs. hiding index.html. These URL canonicalization issues lead to duplicate content and split page rank/link juice.
I can still reference your home page (and other pages on your site) several ways like:
http://ttaxi.pt/
http://ttaxi.pt/index.html
http://www.ttaxi.pt/
http://www.ttaxi.pt/index.html
Search engines rank URLs. They typically see each unique URL as a different page. So if 10 sites link to each of the above URLs, they see 4 pages each w/ 10 inbound links... NOT a single home page w/ 40 inbound links.
Each page on your site should have a single URL used to reference it. This URL is the canonical (preferred) URL. All other non-canonical URLs that can be used to render the same page should be 301 redirected to the canonical URL.
This means you need to make several decisions like:
www vs. non-www
show default documents or hide default documents (index.html)
show trailing '/' when referencing folders w/ default documents or hide the trailing '/'
http vs. https (which I think you've already fixed)
Last edited by Canonical; 01-04-2010 at 11:47 AM..
|