Problem with https://www.my-web-site-1.com

Identified as duplicate? Probably yes.

[zafile]

My Web hosting company provides shared SSL in some of its accounts.

Hence, one of my Web sites is accessed via http://www.example-1.com and https://www.example-1.com.

Today, I discovered that Google has indexed both http://www.example-1.com and https://www.example-1.com.

I have another site (different content) hosted with the same company but in an account that doesn't provide shared SSL. Therefore, the site http://www.example-2.com doesn't have a "duplicate" at https://www.example-2.com.

http://www.example-2.com works well in Google.

http://www.example-1.com gets constantly bumped in the SERPS.

My hosting company doesn't allow to put a blank page at https://www.example-1.com.

Can I exclude https://www.example-1.com via robots and let http://www.example-1.com be fully crawlable?

Thanks for your input.

[zafile]

[google.com...]
explains the procedure on how to include different robots.txt files in ports http and https.

However, my Web hosting company (a major player in the US and Japan) doesn't permit by default different robots.txt files in ports http, https under the same domain name.

Basically, the content at https: //ww w.example-1.com is a complete mirror of http: //ww w.example-1.com .

Some of my strongest competitors rank high in searches whereas http: //ww w.example-1.com performs poorly. Their Web sites don't provide access via https.

http: //ww w.example-1.com and http: //ww w.example-2.com are built based on [webmasterworld.com...] . As far as I can notice, https access is the only difference.

[moehits]

could https:// cause duplicate page problems?

I have a site that is only indexed under either www or https, no listings are showing for http://

I'm going to add the robots tags, but I was wondering if this could cause problems?