Hosting and footprint control for a PBN network
Hosting and footprint control is the technical separation of the sites in a PBN network, so that no common trace connects one site with another. Best Boost Partners places the sites with different hosting providers and in different IP ranges, gives them different DNS, CMS, themes and analytics, and keeps a register of all these parameters. The work is part of the PBN networks service. You receive the register and the access details for every hosting account.
What exactly do we separate and control?
Hosting providers and IP ranges
Each site is placed with its own hosting provider or, at the least, in its own IP range. We do not use hosting sold as made for PBN: its addresses are known, and networks of many owners are gathered on them.
DNS and name servers
Sites of one network do not share name servers. We combine the DNS of registrars, of hosting providers and of outside DNS services, and write the choice into the register.
CMS, themes and templates
The network runs on different systems: WordPress, plain HTML and other CMS. Themes, plugin sets, page structure and the look of standard pages differ from site to site.
Analytics and outside services
A shared Google Analytics or Google Search Console account connects sites with each other at once. Each site gets separate counters and accounts or does without them, and the same applies to advertising codes, fonts and widgets.
Accounts and access
Registrar, hosting and admin accounts are not used for several sites at once, and each account has its own e-mail address. WHOIS privacy hides the registration data where the domain zone allows it.
Register of parameters
All parameters of every site are kept in one table: provider, IP address, name servers, CMS, theme, counters, accounts. Before a new site is launched, its row is compared with the rest of the table.
What do you get from hosting and footprint control?
- The register of footprints: provider, IP address, name servers, CMS, theme and counters for every site.
- Access details for every hosting account, with the e-mail address the account is tied to.
- A list of matches found between sites and what was done about each match.
- A table of hosting costs and renewal dates for every site.
- A written checklist for launching a new site without repeating parameters already present in the network.
When is hosting and footprint control needed?
- You are launching a PBN network, and its sites have to be spread across hosting from the first day.
- Your existing network sits with one provider or in one IP range and has to be moved apart.
- You suspect that the sites of your network are connected by shared counters, themes or accounts.
- You are adding new sites and need a check that they do not repeat parameters already taken in the network.
Frequently asked questions
What is a footprint in a PBN network?
A footprint is any feature that repeats across the sites of a network and shows that one owner stands behind them. Typical footprints are a shared IP address, the same name servers, one analytics account, one theme or identical standard pages. A search engine that finds such a repeat can join the sites into one group.
Is it enough to place every PBN site on a separate IP address?
No. Different IP addresses remove one footprint out of many. Sites on different addresses stay connected if they share name servers, an analytics account, a theme or the same pattern of outgoing links. The check covers every parameter in the register.
Can working PBN sites be moved to new hosting without losing their indexing?
Yes. A site is moved with its content, address structure and redirects preserved, and the DNS is switched after the copy has been tested on the new hosting. Sites are moved one by one, at intervals, so that the network does not change hosting in one visible wave. After each move we check that the pages have stayed in the index.
Tell us about the project
Fill in what you already know. Blank fields are fine: we will clarify the rest in conversation.
Brief sent
Thank you. We will reply within one working day.
Preview mode: the form handler is not connected yet, so nothing was sent.