For some weird reason the content accessed though our domains is returned via SSL HTTPS on all domains pointing to the server.

https://domain.com leads to our website, with a proper SSL certificate (so, no warning).

https://domain2.com, is also hosted on our server but without a SSL certificate This leads to a warning message and if accepted continues to the content of this domain.

The problem is that any search for our keywords in Google shows "fake websites" on top of ours and with the warning et al.

It seems unsolvable so we are thinking about turning SSL off. I'm just afraid of losing whatever indexing we have. How can I avoid that?

  • If it's without the SSL certificate, should it not be domain2.com? Commented Dec 16, 2012 at 5:33
  • I think this needs to be explained a little more clearly before it's possible to give a useful answer. For example, have you looked at why the 2nd domain is forwarding to the first? By losing "indexing", do you mean content being de-indexed, or losing rank?
    – GDVS
    Commented Dec 16, 2012 at 10:29
  • second domain redirects to the first because the first is the only SSL domain hosted on this server. (that's what the sys admin told me at least). By losing "indexing", i meant losing rank.
    – pixeline
    Commented Dec 18, 2012 at 18:02

2 Answers 2


Here is an video by Matt Cutts discussing a similar subject about people going from HTTP to HTTPS I presume the same would hold true going the other way. But since the host and path name of the pages are not changing I don't expect you should lose rankings if you go down it'll most likely be Google re-indexing your pages.

Can switching to HTTPS harm ranking?



It might have some impact on your rankings if the HTTPS page is indexed within Google.

You should be using rel canonical your pages on the HTTP so Google believes that HTTP is the master protocol.

A quick fix for this is to purchase another SSL Cert for the 2nd domain, they only cost around £10 for a year.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.