Question - PBN backlinks pointing to http://www... should i move to https?

Emme

Registered Member
Joined
Oct 27, 2018
Messages
70
Reaction score
27
So, yes.
Thank you guys for taking your time and opening the thread to read.

The question is simple, so as you guys might know most TIER 1 expired domain sites that has let say 400 domains pointing to a http://www (non ssl version).
Would you guys use the http://www version or you'd just do a 301 from the http://www to the https://www. have you guys tested if some "juice" is lost or something?

I've around 60-70 of this tier 1 sites - expired domains, and, well... it has been working for me keeping it as http://www .... so I kept doing it...but I'm wondering if there's more juice if I do what google suggest about moving to https://www...

--
I know that 301 because it's a permanent redirect it usually don't lose power... but i'm not sure if i should move all my 60-70domains to a https:// version of the domain.

What are your thoughts?
Thanks.
 
I'd stick with the non-ssl version as I don't wanna mess up the link juices. Unless your site is an e-commerce there's no need to use SSL.
 
I think the same way you do.
But also part of a PBN is maintain and also if you work it good enough you’ll gain positions in rankings easily...and nowadays google takes https as a ranking factor.... so I really don’t know what’d make more sense... ssl or no ssl.
 
I'd stick with the non-ssl version as I don't wanna mess up the link juices. Unless your site is an e-commerce there's no need to use SSL.
I have an aged domain... The backlinks point to www. Version....
But i rebuild the domain with non www.

Will it decrease the link juice too?
 
Redirecting might lose link juice but it will be recovered after a while, you have to wait. Else don't do any changes.
 
Regarding SSL:

Changing to SSL isn't a problem with PBNs. No link juice is lost in the long term.
You are probably using wordpress, right? Just use Let's Encrypt for the SSL certificate + Really Simple SSL (the PRO version is great) plugin to make sure it works properly on your PBNs and you're good to go.
Having said that, if you have good results, why change it? We still have hundreds of PBNs with no SSL, mostly because those are very old (5+ years) and SSLs were pricey back then. But all of our latest PBN builds are with SSL, even if the links point to http:// iterations.


Regarding www / non-www:
Using the correct www/non-www version is more important, imo. I'd recommend to use the one that has more links pointed to it and 301 the other via htaccess:

htaccess changes to redirect www to non-www:
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC] RewriteRule ^(.*)$ http://%1/$1 [R=301,L]


.htaccess changes to redirect non-www to www:
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]
 
I did that and lost the 80% link juice at first. But after a while coming back to normal.
 
Regarding SSL:

Changing to SSL isn't a problem with PBNs. No link juice is lost in the long term.
You are probably using wordpress, right? Just use Let's Encrypt for the SSL certificate + Really Simple SSL (the PRO version is great) plugin to make sure it works properly on your PBNs and you're good to go.
Having said that, if you have good results, why change it? We still have hundreds of PBNs with no SSL, mostly because those are very old (5+ years) and SSLs were pricey back then. But all of our latest PBN builds are with SSL, even if the links point to http:// iterations.


Regarding www / non-www:
Using the correct www/non-www version is more important, imo. I'd recommend to use the one that has more links pointed to it and 301 the other via htaccess:

htaccess changes to redirect www to non-www:
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC] RewriteRule ^(.*)$ http://%1/$1 [R=301,L]


.htaccess changes to redirect non-www to www:
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]

hey great answer I agree with you.
so far nobody answer that if In the long term it’s beneficial the SSL version.

So conclusion.
Https more beneficial long term than http. But initially worst than the http version because there are none links pointing to the https version. (So little slow until google crawls, index, etc etc the juice to the ssl version)

Http it’s good, very good short term. But not better long term than the htttps version.

Thank you guys!
 
gang - interested to know what the general consensus in 2023 is? should you build back PBN as the original http version, or take the short term hit, and build it as https:??

@Rachmaninoff - what is your latest thinking on this?

@Emme - thoughts in 2023?

@Nargil - would appreciate your input here as well
 
gang - interested to know what the general consensus in 2023 is? should you build back PBN as the original http version, or take the short term hit, and build it as https:??
Take the hit, if indeed there is one. Not having SSL enabled on your domains will never be a positive signal.
 
gang - interested to know what the general consensus in 2023 is? should you build back PBN as the original http version, or take the short term hit, and build it as https:??
I do stick with the http version for the PBNs and they work without any problems,
Redirecting any expired domains used for the money sites to the https version thought,

The thing is, it's not as much as important, both versions will pass the link juice,
301 to https will simply take you some more time to things take effect on the PBN website and will dilute some of the link juice for some time as well,

So, you'll be sacrificing 4-6 weeks to wait for the domain/website after restoring it with the http version,
and additional 3-6 weeks for the redirect to take effect for that PBN, then you can place your link(s)
 
Back
Top