First and foremost the most important aspect of your Private Blog Network is randomness. Consider what pattern or foot print your PBN might have and avoid that commonality.
Good PBNs Are Random, Start With Different Name Registrars
First off you need private domain registration, if not private then you’ll need people and addresses from all over. If you always use Godaddy you’re going to have to try out others to avoid a pattern. Incidentally if you always use Godaddy you’re getting ripped off as they will charge you for privacy and many others don’t. Some popular Name Registrars are 1and1.com namesilo.com namecheap.com cosmotown.com each of these can save you a considerable amount over Godaddy considering they offer free private registration and using more than one breaks a pattern.
Each time you add a new site to your PBN you need to approach it from the beginning as if you’re playing a character in a story who has never made a website before, when I say that I mean if you know you have a site on Host A and you like that host you’re making decisions based on previous sites and are more likely to create a pattern. Forget Host A how would you find a host for the first time? Google popular web hosts and pick a cheap new partner.
One thing that’s really beneficial about building PBNs that is more helpful to you in the long run is the forced exploration. After you’ve built ten sites on ten hosts using ten registrars and ten WordPress themes you’ll be able to write three top ten lists and rank the best of the 720 combinations that were available to you. It’s a lot of practice and as you’re avoiding patterns and repetition you’ll find yourself stepping out of your norm.
Vary Your Web Hosts
Speed of a web host is important normally but not necessarily when your building a PBN. While you want your primary or money site to load in under 3 seconds its perfectly fine if your PBN site loads in 7 seconds and that opens the door to all manner of generic no name web hosts. Your primary goal with multiple web hosts is to utilize a different IP address.
The only two big issues with this model …
Organization OF PBN Resources
What site is down? Oh….well which domain registrar did I use? Am I using their nameservers, someone else’s? Where did I point that to be hosted? Sure these aren’t that annoying to answer with a 10 site network, but try answering it when you’ve built and scaled up to 200 sites using 7 registrars, 20 name servers, 150 different IPs … it becomes unmanageable as you find yourself searching for your site more than you are building new sites, and why are you having to search? Maintaining a site is essential, as updates roll out to WordPress, plugins get updated and hackers exploit new vulnerabilities. If you log into every site you own and spend 5 minutes on each site your 200 domain name network will take 16 hours … or two days a week and consider that you only spend 5 minutes on a site, you likely didn’t fix any issues and took no breaks! It’s time to consider an apprentice or spreadsheets that fully document every aspect of your network, or both.
Somewhere around 100 domains I figured out I needed to approach this like an enterprise would and have actual uptime monitoring allowing me to see the state of the network easily. UptimeRobot allows you to set up 50 monitors on a free account.
In the real world 94% Uptime is horrible. Consider that in the last 30 days I had a recorded 104765 minutes sites were down in this sample of sites. I had issues with a server getting attacked by someone using 1700 servers causing a DOS attack. Why? Anyone’s guess … usually its a game to them and they aren’t paying for those 1700 servers but they’re other people’s hacked resources being used to grow their network.
You may be interested in MainWP or InfiniteWP … Godaddy provides Godaddy Pro. You need to be mindful that these only work when they work and will they give away a signature pattern? Likely they can create an easier management solution but easier is dangerous.
Costs Ballon And Randomness Prevents Savings
As you scale up from 10 to 20 to 50 sites your going to wake up one day and realize youre spending hundreds of dollars a month on infrastructure and all of your time will now be consumed with maintaining your network. Adding someone to help you is going to increase costs and take your time to train them in being effective at maintaining the network. Be careful who you bring in to help you, friends are obvious choices but when they get upset about something unrelated to the network they could leave you high and dry. Worse yet, they are the most likely to teach you a lesson by bailing on you for a couple weeks. Trust the people who are in it for the money … pay them more than they can get at a retail job to build loyalty to your mission. They need not be technical people but they need to understand that if a site is down, Google can’t index it and that backlink is missing now. They need to be able to follow a logical progression and understand the parts that are in play to help you maintain the site.
The obvious answer to addressing costs is to bundle services and make sure you’re utilizing resources in the most effective manner but that is accomplished by making patterns. You can’t find cost savings by giving away your sites.
Cloudflare Allows Consolidation And The Pattern Is Indistinguishable
Cloudflare offers the ability to hide among the masses. Who is Cloudflare? They stand in front of your server and take the brunt of the internets crap. Upwork.com, Medium.com, Themeforest.net, Chaturbate.com are among the names using Cloudflare.com services. Some estimates suggest that Cloudflare is about 8% of the entire internet. Thats huge! At one point they found themselves protecting the Israeli government’s network as well as the PLOs.
Using Cloudflare is hiding in plain sight and free. I recommend it but in a mixture capacity still have some sites out side of their network just to avoid any one bottleneck, it would seem odd if 100& of the sites linking to a domain are using Cloudflare….remember they are 8% and while the largest chunk of the internet they aren’t the internet.
This article has focused mainly on external and infrastructure concerns of building a PBN. This is really a third of topic and in the coming weeks I’ll include two more posts that address on site content issues of building a PBN and site design considerations for a network of sites.