Does a domain need an SSL to transfer equity in a 301 redirect?

[kontentdruid]

I have https://www.oldsite.com and built some links to it
Now i have https://www.newsite.com
and I want to 301 redirect https://www.oldsite.com to https://www.newsite.com

But it turns out that https://www.oldsite.com does not have an active SSL cetificate intact, and when you go to it, chrome gives that scary warning of BEWARE!

Anyways, i 301'd redirected http://www.oldsite.com to https://www.newsite.com

And i noticed that if i click on https://www.newsite.com it does not redirect to the new site. (except in chrome it does, but other browsers it does not). I realize this is b/c i didnt 301 the https and i can't bc it doesnt have one. So does this really mean that i have to install an SSL on the old domain in order to properly 301 it and gain the link equity toward the new domain?

 

[dandan594594]

Redirect Pizza allows you to set a free SSL through a redirect.

Set DNS to Redirect Pizza, 301 to new site.

 

[tiiberius]

If the redirect is not in place then equity is not passed.

Alternative would be to simply link out to webpage.

 

[magdalenokiri]

Is there a specific video tutorial? I'm also learning how to do it

 

[sparior]

Yes, having an SSL certificate on the old domain is essential for a seamless 301 redirect, especially for maintaining link equity. When a website lacks an SSL certificate, modern browsers, like Chrome, often display warning messages to users, which can deter traffic and negatively impact user experience.

Both domains must have SSL certificates installed. This not only helps in preserving the SEO value of the redirected links but also enhances overall website security and trustworthiness.

 

[ralphnsk]

I have https://www.oldsite.com and built some links to it

Strange, you're saying that you already had https on your old site, so I guess at some point you had an SSL cert installed, right?

Anyway, what you could do is point name servers of an old site to cloudflare, and there you can set up a redirect rule. Go to Rules -> Redirect rules and add something like this:

 

[BlackShield]

To make sure your website redirects properly and keeps its link value, Install an SSL certificate to the old domain.

 

[NeedMyLink]

You should definitely install an SSL certificate on your old domain to properly redirect from https to https. Without SSL on the old domain, users and search engines encountering the https version will get a security warning.

 

[l0cke]

I have https://www.oldsite.com and built some links to it
Now i have https://www.newsite.com
and I want to 301 redirect https://www.oldsite.com to https://www.newsite.com

But it turns out that https://www.oldsite.com does not have an active SSL cetificate intact, and when you go to it, chrome gives that scary warning of BEWARE!

Anyways, i 301'd redirected http://www.oldsite.com to https://www.newsite.com

And i noticed that if i click on https://www.newsite.com it does not redirect to the new site. (except in chrome it does, but other browsers it does not). I realize this is b/c i didnt 301 the https and i can't bc it doesnt have one. So does this really mean that i have to install an SSL on the old domain in order to properly 301 it and gain the link equity toward the new domain?

Of course, you'll need to add an SSL certificate to the old site to ensure links redirect properly to the new site without any scary warnings.

 

[kontentdruid]

im struggling to understand this - why should i have to maintain an ssl certificate on an old website for the rest of eternity if i just want to keep the old website domain 301 redirecting to a new website?