| 1:52 am on Dec 6, 2012 (gmt 0)|
Curious why you can't just have a redirect to always go to www. ?
| 4:15 pm on Dec 6, 2012 (gmt 0)|
Yes, that's a fair question. Let's change it from "domain.com" and "www.domain.com" to "domain.com" and "sub.domain.com" then so that the original question doesn't get changed.
| 8:21 pm on Dec 6, 2012 (gmt 0)|
Actually.. your situation is incredibly common and most cheap certificates cover the www and root domain. I just looked at godaddy's site and it reads..
"> 1 certificate protects www.securemywebsites.net AND securemywebsites.net"
In your case a real wildcard would be unnecessary.
| 8:28 pm on Dec 6, 2012 (gmt 0)|
I wish I could change the top post so that I referenced two subdomains instead of what I wrote (www.domain.com and sub.domain.com). I'm just trying to understand if there's going to be a search penalty/trust lost if we switch to a wildcard certificate.
| 8:48 pm on Dec 6, 2012 (gmt 0)|
You essentially lose nothing with a wildcard in the way of security. domain.com and *.domain.com are secured. So if for some reason you have https:// indexed urls, then that won't hurt or change anything.
| 1:24 pm on Dec 7, 2012 (gmt 0)|
Thank you for your reply. I'm not concerned about "security" - I'm worried about getting a search penalty or being put in a sandbox b/c we opted for a wildcard cert instead of a non-wildcard cert.
| 3:25 pm on Dec 7, 2012 (gmt 0)|
no, you won't
| 1:57 pm on Jan 22, 2013 (gmt 0)|
I don't think it will be problem in Google's eye if you add SSL to your domain !
| 2:54 pm on Jan 23, 2013 (gmt 0)|
I haven't read or seen anything that would lead me to believe there is a risk.