Therefore: does Blackhole for Bad Bots help to keep my stats clean?
]]>[Tue Sep 13 03:05:54.542326 2022] [fcgid:warn] [pid 23668:tid 139805776135936] [host www.marcustibesar.com] [client 77.165.100.4:52772] PHP Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, function “blackhole_register_settings” not found or invalid function name in /var/www/html/ma/marcustibesar.com/wp-includes/class-wp-hook.php:307, referer: https://www.marcustibesar.com/photo-albums/
]]>But, two weeks ago, there were problems with Yandex, he believes that some pages with GET parameters in the URL duplicate the contents of other pages. Because of this, Yandex began to lower the site in the search results, so it considers this as a big problem. When I started to understand, I found only pages with GET parameters – “black hole”. To be honest, I am shocked by this Yandex, I have not seen such stupidity from it yet, although it is whitelisted. Examples of links are shown below:
https://***k.ru/?blackhole=e9aedd3382
https://***k.ru/?blackhole=e09c812159
https://***k.ru/?blackhole=ee9220d773
https://***k.ru/?blackhole=289a028982
https://***k.ru/?blackhole=d6eedf004d
Maybe you, as a plugin developer, will find a solution to protect yourself from stupid Yandex? Thanks.
P.S.: I haven’t seen such a problem in Google yet.
]]>You can see the problem here:
https://www.childcareaware.org/?blackhole=191d1f5616
Whatever it’s worth, here’s the robots.txt file:
https://www.childcareaware.org/robots.txt
And here’s what I see in the page response headers for that URL, using the following curl command:
curl -I https://www.childcareaware.org/?blackhole=191d1f5616
HTTP/2 200
cache-control: no-cache, must-revalidate, max-age=0
content-type: text/html; charset=UTF-8
link: <https://www.childcareaware.org/wp-json/>; rel="https://api.w.org/"
link: <https://www.childcareaware.org/wp-json/wp/v2/pages/6>; rel="alternate"; type="application/json"
link: <https://www.childcareaware.org/>; rel=shortlink
server: nginx
strict-transport-security: max-age=300
x-pantheon-styx-hostname: styx-fe1-b-6565f7757d-v8hwj
x-styx-req-id: f5d07a34-8cb2-11eb-9b04-a2bb4a80cf12
date: Wed, 24 Mar 2021 15:09:43 GMT
x-served-by: cache-mdw17381-MDW, cache-ewr18151-EWR
x-cache: MISS, MISS
x-cache-hits: 0, 0
x-timer: S1616598582.092331,VS0,VE1055
vary: Accept-Encoding, Cookie, Cookie
age: 0
accept-ranges: bytes
via: 1.1 varnish, 1.1 varnish
]]>I am trying to activate the “Black Hole” ban feature but I see nothing is implemented in the robot.txt file.
Any suggestion ?
Regards.
JP FOL
]]>Maybe I have another statistical idea to see WHERE the honeypot was successful.
Put i.e. at custom function.php this action:
// Blackhole at loginpage
add_action('login_head', 'blackhole_trigger');
Cheers!
(@specialk gladly you can include this in a new version)
]]>