Will hosting on EBN get my PBN deindexed?
We've been receiving versions of these questions since the day we launched in 2014. All of this still holds today.
- What if search engine employees infiltrate the system and ban all IPs?
- What if one of the users gets a blog flagged which then flags the whole IP?
- What if EBN gets targeted?
- Will using PBN hosting get my blogs deindexed?
Third-Party Reviews of EBN Deindexation Rate
We host tens of thousands of blogs for thousands of users without issues. There are also public case studies where people compared the EBN deindexation rate to other PBN hosting services and hosting providers.
- Charles Floate: SEO Hosting Reviews (see section “6 Month Deindex Comparison”)
- PBN Fox: 3 Ways to Safely Host a Private Blog Network (see section “The 5000 PBN Sites Study”)
As you can see, EBN has by far the lowest deindexation rate of all PBN hosting services and compares to hosting on premium shared hosts.
Why IPs won’t get banned
First, we have a couple of thousand IPs but for safety reasons, you can purchase only up to 500 unique IPs. This way an average user has access to less than 5% of our whole pool of IPs.
The blogs are hosted by big brand providers and they share data centers with their other customers. We don’t see a search engine banning the whole IP ranges from big hosting providers like Amazon, Rackspace or Softlayer just because of a few PBN blogs.
There are no more IPv4 IPs available. For someone to get an IP, another person has to sell it or stop using it. Our IPs are not proxy IPs, gaming IPs, or something else that you can still get in quantities of thousands, like some of our competitors offer. Our IPs are directly given by the hosts and they are meant for hosting websites. And these IPs are very limited. This is also why we can offer only a limited amount of IPs.
There are users (us included) that use the servers to host money sites and real blogs.
We could also drop banned IPs and get new ones while the banned would get rotated to a new customer. That would cause real issues for the search engine.
Why flagged blogs won’t cause a manual review of the IP
The main reason is the sheer quantity. If for example, a PBN blog is on an IP with 100 other sites, the search engine employees would have to check manually each one. If they have 100 manual checks per day ( but they have 10,000 per day), that’s 10,000 manual reviews just for that day. The very next day there may be 1000 new websites on those IPs and 1000 others would go offline. Sooner or later they’d be manually checking the whole internet, every single day. So this is not a feasible strategy from their point of view.
You also might want to check this Matt Cutts video. While it’s over a decade old, it still shows that they always understood that legitimate websites are often in “unclean” neighborhoods.
What if your platform gets targeted?
We often get questions like this when an algorithm change happens or when a few of our customers get their blogs deindexed and they find themselves in the same Facebook group. We do everything we can to make sure there are no footprints and even have third-party security audits to check our system.
We’re very open about deindexations. We can say that on average fewer than 0.1% of blogs get deindexed monthly on our platform, and it's decreasing year after year. Those numbers are really low. So when a deindexation happens it’s mostly confined to a few blogs and very few people. Most of those blogs also don’t follow our recommendations.
What actually gets your PBN blogs deindexed
Footprints and obvious issues with PBN blogs. Most deindexations can be easily avoided by following the best practices for building PBNs. And if you have absolutely no idea why the blog was deindexed, let us know and we’ll try to help you find the reason.