Forum Moderators: Robert Charlton & goodroi
I have no idea how Google has indexed the SSL url as I do not have SSL turned on and I have never had SSL turned on.
I am also seeing the [example.com...] showing up when I do a site:example.com search the last couple of days. For the last 18 months it was showing http://www.example.com at the top.
Has anyone seen this before, any idea how to correct it, am I being penalized in some way for it?
[edited by: tedster at 5:47 pm (utc) on June 23, 2009]
[edit reason] switch to example.com - it cannot be owned [/edit]
If the latter then your site is responding to https, which looks like the case since google's link shows it with https and port 443.
Do you not use SSL at all? If not it looks as if something is set up incorrectly and someone, somewhere has posted an https url for the site that actually works - google would not, I think, infer it otherwise.
If SSL is turned on (and you don't use it) then ensure it's turned off. If your site is on virtual hosting or you can't get access to the domain setup then you would need to talk to your hosting company.
We have a thread that discusses fixing this challenge in the Hot Topics area [webmasterworld.com], which is always pinned to the top of this forum's index page.
I do not have SSL turned on and I have never had SSL turned on
Somehow googlebot did get a response from those urls - so your understanding of how the server is set is not matching up with googlebot's experience. Have you tested them in a browser?
I'd also fix up all of the index filename canonicalisation ahead of any rules for the rest of the site. The whole lot needs to be very carefully planned such that every URL sees only one redirect from bad to good.
That is, you must take steps to avoid a Redirection Chain for any type of URL request.
If any site on a virtual server shares an IP with a site that has SSL (ie a certificate installed and (usually) port 443 enabled) then ALL sites on that IP potentially have SSL enabled. It happened to me many years ago.
In theory all sites except the official SSL one SHOULD have port 443 disabled but that's not guaranteed; it's up to the server manager how well it's set up.