How to Make WordPress PBNs Faster

If you know basic coding then you know that php / htaccess code is executed server side and G can't see it. For example people who think blocking bots in htaccess is a footprint. To anyone that understands coding this is a ludicrous statement. G has shadowbots but they aren't sending shadow MJ12 bots, and they can't even see the code as htaccess is executed server side before G loads the page.

The same goes with PHP. If your plugins folder has an index.php file, and G visits the page, it's shown a blank page. They cannot tell what plugins you're running except by looking at the source code. That's why you:

A) Only use plugins that don't leave footprints in the source code of your blog.

B) Remove the source code from any that do if you want to use them. For example I have a modified Yoast plugin I made that removes all traces of anything to do with "Yoast," there is no indication in the source of my sites that I have this plugin installed. There is a 0% chance G would / could know.

I recommend every SEO learn at minimum the basics of PHP / etc. Teaching myself helped my SEO career immensely.

Alright, so what you said is, that plugins leave footprints and in order to avoid them, you need to either use plugins that don't leave crap in your source code or remove that crap from the source code.

And how exactly this doesn't fit with my original statement, that plugins can be a footprint then? :)
 
Where the hell are you getting $20 from and wtf is this $20 for? You're not making any sense.

OP said he didn't want to spend $20 on an automation plugin. I guess you were so busy attacking others, you missed that part.
 
everything leaves a footprint lets be honest....everyone has their own method to building out PBN's....you can be 99.9% sure you did everything right and you still get de indexed...there is no rhythm or reason to why google does this or what they are looking for if there was and we figured it out we wouldnt be hearing talking about it

Hiding your PBN from crawlers some people think this has to be done.....I on the other hand hide half and let the other have get discovered......so let my competition see whats going on if they wanna reverse engineer and find out my backlinks and my domain then they can hit up the contact us page and send me an email asking for a back link and I will not approve it its simple....people are way to worried
 
OP said he didn't want to spend $20 on an automation plugin. I guess you were so busy attacking others, you missed that part.
Actually, I spend $$$ on single domains sometimes, So $20 is not an issue which people are making fun of, But i though the plugin is not that good and there can be something else better.
 
Alright, so what you said is, that plugins leave footprints and in order to avoid them, you need to either use plugins that don't leave crap in your source code or remove that crap from the source code.

And how exactly this doesn't fit with my original statement, that plugins can be a footprint then? :)

No, they don't. I'm not convinced that even if you used the same 10 plugins on 300 sites it would count any less or be easier for G to find. And guess what, you can't prove it. I have many, many blogs with the exact same plugins and my sites still rank properly and G doesn't magically catch them all.
 
No, they don't. I'm not convinced that even if you used the same 10 plugins on 300 sites it would count any less or be easier for G to find. And guess what, you can't prove it. I have many, many blogs with the exact same plugins and my sites still rank properly and G doesn't magically catch them all.

Well few posts above you said that you are having some deindexations, so it's hard to discuss anything when you are changing statements all the time. :)
 
Well few posts above you said that you are having some deindexations, so it's hard to discuss anything when you are changing statements all the time. :)

When you have a network of thousands of domains and compete in blackhat niches there's always going to be deindexing mate... it's how the game is played.
 
Definitely safe over fast.

Using same plugin to build everything will definitely leave some huge footprints as well, so that's not advised. Still, it costs just $20, that's really nothing if you really want to use that. Another option is to outsource the process. I would rather focus on quality than quantity. My 2 cents.

It should leave no footprints as all it does is database, server side related, If I understand correctly it does not build, it destroys. However I know nothing about the plugin but it in theore no footprint should be added for the tasks it supposedly does.

On a side note, if he wants to automate he either pays for it or builds the tool himself.
 
everything leaves a footprint lets be honest....everyone has their own method to building out PBN's....you can be 99.9% sure you did everything right and you still get de indexed...there is no rhythm or reason to why google does this or what they are looking for if there was and we figured it out we wouldnt be hearing talking about it

Hiding your PBN from crawlers some people think this has to be done.....I on the other hand hide half and let the other have get discovered......so let my competition see whats going on if they wanna reverse engineer and find out my backlinks and my domain then they can hit up the contact us page and send me an email asking for a back link and I will not approve it its simple....people are way to worried

No. Not at all. Plugins or anything that works on the internals do not leave footprints to the public website. Websites are divided in internal (the server) and external (public, the browser ). Google and users only get to see the external section.
 
I'm seriously building PBNs these days. However, I am looking for ways to make the process as Fast and As Easy as possible.
.

ipnetwork x has presets you can use that does 90% of what you want.
you can aso use all in one wordpress migration and just change the theme and you would be done..
 
You're way overthInking "footprints". Footprints are more along the line of having the same / too similar post titles, having the date in the same format on every blog and adding multiple posts with the same keyword in the title on the same day. .

please take mathew woodworms PBN course and make your own PBN license for beginners.. and stop spreading that bs.
 
please take mathew woodworms PBN course and make your own PBN license for beginners.. and stop spreading that bs.

Ahahaha Matthew Woodward's PBN course that's hilarious, I was likely building PBN's before that guy even what SEO meant. Even more funny is that you're probably not joking LMAO.
 
If you are really into building a big PBN, just hire some V/A to do it for you.
I hired some guy from Upwork for building around 30 blogs, this way you get all the customizations you want without problem.

And if you are worried about giving him access to tons of valuable domains, just look for someone that doesn't know shit about SEO and tell him you are building sites for clients or whatever.
 
Doing it manually would be the best option but if you are dealing with PBNs, I am sure you can set some budget for premium plugins instead of looking for free ones.
 
If you know basic coding then you know that php / htaccess code is executed server side and G can't see it. For example people who think blocking bots in htaccess is a footprint. To anyone that understands coding this is a ludicrous statement. G has shadowbots but they aren't sending shadow MJ12 bots, and they can't even see the code as htaccess is executed server side before G loads the page.

Faking a user-agent is trivial, whether that's using a browser, or curl, or an HTTP library. It's just a piece of text.

The bulk of the htaccess configurations mentioned in SEO circles use the User-Agent HTTP header as the string to match against to determine what the bot is. And then not check the IP address is in the range matching that user-agent server.

Granted, Google can't see your htaccess file. But if the same request from the same server, one with a user-agent string that looks like a browser, and one with a user-agent string that matches majestic's user-agent string, when there's a different response, then it's a clue that user-agent filtering is going on.

This is simple black-box probing. They can't see what's inside the black box of your htaccess file, but they can control the input (the HTTP request), and see the output (HTTP response). If there's a site they think might be a PBN, then a quick test of sending two HTTP requests (directly, or indirectly via proxy), with specific user-agent strings will either help confirm the site in question is a PBN, or not.
 
Faking a user-agent is trivial, whether that's using a browser, or curl, or an HTTP library. It's just a piece of text.

The bulk of the htaccess configurations mentioned in SEO circles use the User-Agent HTTP header as the string to match against to determine what the bot is. And then not check the IP address is in the range matching that user-agent server.

Granted, Google can't see your htaccess file. But if the same request from the same server, one with a user-agent string that looks like a browser, and one with a user-agent string that matches majestic's user-agent string, when there's a different response, then it's a clue that user-agent filtering is going on.

This is simple black-box probing. They can't see what's inside the black box of your htaccess file, but they can control the input (the HTTP request), and see the output (HTTP response). If there's a site they think might be a PBN, then a quick test of sending two HTTP requests (directly, or indirectly via proxy), with specific user-agent strings will either help confirm the site in question is a PBN, or not.

yes, thats also why all good cloakers use rDNS checks ;)
however it doesn't mean just because UA filtering is going on, that its a PBN, because there is lots of other legitimate software employing this method. google can't instantly conclude just because a site filters UA's, that its a PBN. for example there are many security plugins that filter bots or unwanted traffic. then there are plugins that probe for mobile traffic via UA. also not all forms of cloaking are against the google ToS, so it would require a manual review to do a real assessment, its not reliable to do this automated. there are better ways to detect bad PBN setups for example those with reverse proxies..
 
Faking a user-agent is trivial, whether that's using a browser, or curl, or an HTTP library. It's just a piece of text.

The bulk of the htaccess configurations mentioned in SEO circles use the User-Agent HTTP header as the string to match against to determine what the bot is. And then not check the IP address is in the range matching that user-agent server.

Granted, Google can't see your htaccess file. But if the same request from the same server, one with a user-agent string that looks like a browser, and one with a user-agent string that matches majestic's user-agent string, when there's a different response, then it's a clue that user-agent filtering is going on.

This is simple black-box probing. They can't see what's inside the black box of your htaccess file, but they can control the input (the HTTP request), and see the output (HTTP response). If there's a site they think might be a PBN, then a quick test of sending two HTTP requests (directly, or indirectly via proxy), with specific user-agent strings will either help confirm the site in question is a PBN, or not.

The idea that Google is sending shadow bots as MJ12 or spoofing MJ12 to find people who block Majestic is nothing but fear-mongering nonsense.

Google has many different types of shadow bots, looking for many fingerprints, of which many people have been monitoring and recording for a decade. Google is not sending fake MJ12 bots to find your PBN's.

If you're talking about cloaking, of course UA is utter shit. Of course Google will catch that. But applying that same logic and saying they're going to detect you blocking bots is dumb.
 
Last edited:
yes, thats also why all good cloakers use rDNS checks ;)
however it doesn't mean just because UA filtering is going on, that its a PBN, because there is lots of other legitimate software employing this method. google can't instantly conclude just because a site filters UA's, that its a PBN. for example there are many security plugins that filter bots or unwanted traffic. then there are plugins that probe for mobile traffic via UA. also not all forms of cloaking are against the google ToS, so it would require a manual review to do a real assessment, its not reliable to do this automated. there are better ways to detect bad PBN setups for example those with reverse proxies..

rDNS checks are so slow. There are ways to do a proper cloak without that or UA, it's obvious how, but I don't discuss cloaking in public anyways.
 
Back
Top