Put a part of PBN in SSL

W

websitedesign

Junior Member

Mar 6, 2016

133

15

• Oct 14, 2016

• #1

May it have a positive impact to install SSL cetificates on a part of PBN network sites?

 

Lauriat

Power Member

Oct 23, 2011

796

259

• Oct 15, 2016

• #2

interesting, i don't know if google considers links from ssl sites stronger than non-ssl, try it and let us know.

 

Aty

Elite Member

Jan 27, 2011

7,631

5,300

• Oct 15, 2016

• #3

I'm pretty sure that would be useless.

 

P

prisonbreak

Newbie

Oct 14, 2016

4

1

• Oct 15, 2016

• #4

google likes ssl sites more. test it. i would recommend to put 25% of your sites on ssl, use for the other 25% incapusla and/or cloudflare. just mix it up

 

Nargil

Elite Member

Executive VIP

Jr. VIP

May 10, 2012

9,306

7,419

• Oct 15, 2016

• #5

This is absolutely pointless and only reduces your ROI. Really, absolutely no point in that, rather keep your money and get more PBN domains.

 

Dwain Stewart

Regular Member

Jan 20, 2011

369

135

• Oct 15, 2016

• #6

Give for Charity instead of wasting money on getting SSL for your PBNs. Not worth it brother.

 

I

IceHD

Power Member

May 8, 2013

534

222

• Oct 15, 2016

• #7

Last time I check SSL is free, provided via https://letsencrypt.org/ I've seen many new hosting adding a cPanel plugin so that you can have it generated inside CPanel for each and every project of yours. You can even install that on a VPS and generate the keys there and add them to cPanel.

Or an easier alternative, CloudFlare provides shared SSL certs, so by having a domain using their NSs you get it.

Even this being free I don't think it's a good idea to use it, not sure how google makes the switch in juice, that's why we use the version with the best links (www or non-www)

 

starki

Senior Member

Jul 17, 2012

911

344

• Oct 16, 2016

• #8

Wasted time and money. If the expired domain ran on http instead of https before, the additional redirect (which is necessary, changing from http://www.example.com to https://www.example.com is technically identical to changing from http://www.example.com to http://www.newdomain.com) from http to https just wastes a bit of linkjuice (dampening factor for the 301). Not much, but without advantages, it's pointless anyway.