Why Selenium and headless browsing will never work for CTR

Status
Not open for further replies.

theautomationdomination

Regular Member
Joined
Feb 7, 2018
Messages
392
Reaction score
214
Selenium bots like CTR Booster/CTR Boss are detected by Google and other search engines. Headless browsing like Agency Assassin is not even loading the page. If these people had any understanding of JS and how all this worked they would never use these. You need something outside of that and you can get good results. A lot of people have given up on it based on the bot creators not knowing anything about how it works. But it definitely works.
 
You need to run "real" traffic to what you are trying to rank. Meaning it has to be custom actions that actually go to google.com search it cookie the profiles etc... Most of the actions that count are JS which means they don't even load or trigger until you click on them.
 
Selenium bots like CTR Booster/CTR Boss are detected by Google and other search engines. Headless browsing like Agency Assassin is not even loading the page. If these people had any understanding of JS and how all this worked they would never use these. You need something outside of that and you can get good results. A lot of people have given up on it based on the bot creators not knowing anything about how it works. But it definitely works.
You must really be a Newbie.
 
Hello, owner of CTR Boss here.

Selenium out of the box without using extensions and additional methods of bypass will be detected, agreed. It comes down to a lot of things:

How premium and private are your proxies?

Random user agents. Random footprint Generation. Disabling of webRTC. Realitic actions (visiting google first, typing in 1 letter at a time, scrolling as a real user, all things captured by Google).

For Google maps specifically, visiting the location from random areas within the same city (not just a Country level).

Edits to the JS. As an example, Google detects selenium by testing for predefined javascript variables, and documents with variables like $cdc_ and $wdc_

Modifications to things like your chromedriver are the key to antidetection.

We don't care to relay all of the ways we've managed to beat detection, and we don't want to tip off Google to many of our implementations, but please don't bucket CTR Boss into our list of competitors with zero knowledge about what we've implemented.
 
Hello, owner of CTR Boss here.

Selenium out of the box without using extensions and additional methods of bypass will be detected, agreed. It comes down to a lot of things:

How premium and private are your proxies?

Random user agents. Random footprint Generation. Disabling of webRTC. Realitic actions (visiting google first, typing in 1 letter at a time, scrolling as a real user, all things captured by Google).

For Google maps specifically, visiting the location from random areas within the same city (not just a Country level).

Edits to the JS. As an example, Google detects selenium by testing for predefined javascript variables, and documents with variables like $cdc_ and $wdc_

Modifications to things like your chromedriver are the key to antidetection.

We don't care to relay all of the ways we've managed to beat detection, and we don't want to tip off Google to many of our implementations, but please don't bucket CTR Boss into our list of competitors with zero knowledge about what we've implemented.
It seems like CTR boss is just CTR booster with an interface. Do you have any videos of the software working?
 
Hello, owner of CTR Boss here.

Selenium out of the box without using extensions and additional methods of bypass will be detected, agreed. It comes down to a lot of things:

How premium and private are your proxies?

Random user agents. Random footprint Generation. Disabling of webRTC. Realitic actions (visiting google first, typing in 1 letter at a time, scrolling as a real user, all things captured by Google).

For Google maps specifically, visiting the location from random areas within the same city (not just a Country level).

Edits to the JS. As an example, Google detects selenium by testing for predefined javascript variables, and documents with variables like $cdc_ and $wdc_

Modifications to things like your chromedriver are the key to antidetection.

We don't care to relay all of the ways we've managed to beat detection, and we don't want to tip off Google to many of our implementations, but please don't bucket CTR Boss into our list of competitors with zero knowledge about what we've implemented.
Who told you that disabling WebRTC was a smart idea? They detect that you know.
 
It seems like CTR boss is just CTR booster with an interface. Do you have any videos of the software working?

I have zero clue what CTR Booster is. Everything is custom coded on our end, we have our own 8 scripts broken down as:

Desktop search - Organic
Desktop search - Google maps
Desktop search - Knowledge panel
Desktop search - directions
Mobile search - Organic
Mobile search - Google maps
Mobile Search - Directions
Mobile search - Knowledge panel

Who told you that disabling WebRTC was a smart idea? They detect that you know.

No, they detect you're on a proxy without webrtc.
 
I have zero clue what CTR Booster is. Everything is custom coded on our end, we have our own 8 scripts broken down as:

Desktop search - Organic
Desktop search - Google maps
Desktop search - Knowledge panel
Desktop search - directions
Mobile search - Organic
Mobile search - Google maps
Mobile Search - Directions
Mobile search - Knowledge panel



No, they detect you're on a proxy without webrtc.
Same exact actions as CTR Booster too. That is very interesting. Where is the video of the actual software running?
 
I'm trying to educate the monkeys on this forum.
Excellent. From your educational posts I can see that you've never used Selenium at all. Go on educating, please. This will be funny. (And keep on posting so you can upgrade to Jnr. VIP and sell your stuff.)
 
Same exact actions as CTR Booster too. That is very interesting. Where is the video of the actual software running?
Again, I have had zero knowledge of CTR Booster before reading your post. Our backend in django is scheduling another server to launch the browsers and perform the actions.
 
Again, I have had zero knowledge of CTR Booster before reading your post. Our backend in django is scheduling another server to launch the browsers and perform the actions.
You must be really new to SEO if you never heard of CTR booster. And the fact you copied that bot to a T makes me think you are fibbing.
 
Again, I have had zero knowledge of CTR Booster before reading your post. Our backend in django is scheduling another server to launch the browsers and perform the actions.
Where are the videos of the ctr boss bot running?
 
You need to run "real" traffic to what you are trying to rank. Meaning it has to be custom actions that actually go to google.com search it cookie the profiles etc... Most of the actions that count are JS which means they don't even load or trigger until you click on them.
You must be really new to SEO if you never heard of CTR booster. And the fact you copied that bot to a T makes me think you are fibbing.
I'm trying to educate the monkeys on this forum.
Same exact actions as CTR Booster too. That is very interesting. Where is the video of the actual software running?
Who told you that disabling WebRTC was a smart idea? They detect that you know.
Where are the videos of the ctr boss bot running?
Please use the multi-quote function if possible, as it makes the threads flow much easier. How to multi-quote can be found here Newbie Guide
 
Status
Not open for further replies.
Back
Top