Skip to main content
Webmasters

Return to Question

use example.com in title
Link
Stephen Ostermiller ♦
Stephen Ostermiller ♦
  • 99.4k
  • 18
  • 141
  • 364

Will not having https redirect from domainexample.com to www.domainexample.com affect SEO

Tweeted twitter.com/StackWebmasters/status/840033334478700544
URL/domain formatting.
Source Link
MrWhite
MrWhite
  • 43.1k
  • 4
  • 50
  • 90

I've recently set up SSL for a bunch of my domains using a Positive SSL Multi-domain certificate from NameCheap, my domain provider.

In the past when I was using single domain certificates, they would cover both the www domain and the non-www domain, like this:

I set up IIS so that all these URLs would redirect to https//www.example.comhttps://www.example.com:

Everything was good.

Now, with the new multi-domain cert in place, I discovered that it does not cover the www domainwww subdomain and the non-www domain by default. My thought was to control this with redirect rules, just as I did above. HoweverHowever, I ran into an issue:

I spent a lot of time modifying redirect rules to try to address this, but eventually came to believe that browser checks the certificate and shows the cert error page before the server is able to perform the redirect.

I could add more domains to my multi-domain cert to make sure it covers both the 'example.com'example.com and 'www.example.com'www.example.com for each respective domain. II have avoided this due to cost.

My question is: Do search engines care that https://example.comhttps://example.com doesn't work? Will that affect search rankings for the overall domain?

I've recently set up SSL for a bunch of my domains using a Positive SSL Multi-domain certificate from NameCheap, my domain provider.

In the past when I was using single domain certificates, they would cover both the www domain and the non-www domain, like this:

I set up IIS so that all these URLs would redirect to https//www.example.com:

Everything was good.

Now, with the new multi-domain cert in place, I discovered that it does not cover the www domain and the non-www domain by default. My thought was to control this with redirect rules, just as I did above. However, I ran into an issue:

I spent a lot of time modifying redirect rules to try to address this, but eventually came to believe that browser checks the certificate and shows the cert error page before the server is able to perform the redirect.

I could add more domains to my multi-domain cert to make sure it covers both the 'example.com' and 'www.example.com' for each respective domain. I have avoided this due to cost.

My question is: Do search engines care that https://example.com doesn't work? Will that affect search rankings for the overall domain?

I've recently set up SSL for a bunch of my domains using a Positive SSL Multi-domain certificate from NameCheap, my domain provider.

In the past when I was using single domain certificates, they would cover both the www domain and the non-www domain, like this:

  • www.example.com
  • example.com

I set up IIS so that all these URLs would redirect to https://www.example.com:

  • www.example.com
  • example.com
  • http://www.example.com
  • http://example.com
  • https://www.example.com
  • https://example.com

Everything was good.

Now, with the new multi-domain cert in place, I discovered that it does not cover the www subdomain and the non-www domain by default. My thought was to control this with redirect rules, just as I did above. However, I ran into an issue:

  • www.example.com works
  • example.com works
  • http://www.example.com works
  • http://example.com works
  • https://www.example.com works
  • https://example.com Shows Cert Error

I spent a lot of time modifying redirect rules to try to address this, but eventually came to believe that browser checks the certificate and shows the cert error page before the server is able to perform the redirect.

I could add more domains to my multi-domain cert to make sure it covers both the example.com and www.example.com for each respective domain. I have avoided this due to cost.

My question is: Do search engines care that https://example.com doesn't work? Will that affect search rankings for the overall domain?

Source Link
JeffryHouser
JeffryHouser
  • 151
  • 2

Will not having https redirect from domain.com to www.domain.com affect SEO

I've recently set up SSL for a bunch of my domains using a Positive SSL Multi-domain certificate from NameCheap, my domain provider.

In the past when I was using single domain certificates, they would cover both the www domain and the non-www domain, like this:

I set up IIS so that all these URLs would redirect to https//www.example.com:

Everything was good.

Now, with the new multi-domain cert in place, I discovered that it does not cover the www domain and the non-www domain by default. My thought was to control this with redirect rules, just as I did above. However, I ran into an issue:

I spent a lot of time modifying redirect rules to try to address this, but eventually came to believe that browser checks the certificate and shows the cert error page before the server is able to perform the redirect.

I could add more domains to my multi-domain cert to make sure it covers both the 'example.com' and 'www.example.com' for each respective domain. I have avoided this due to cost.

My question is: Do search engines care that https://example.com doesn't work? Will that affect search rankings for the overall domain?