How to block W3 Validator Services
Operated by World Wide Web Consortium (W3C). W3C provides various free validation services that help check the conformance of Web sites against open standards.
robots.txt
What the agent asks to be told. It obeys this or it does not — nothing enforces it.
User-agent: W3 Disallow: /
nginx
In the server block, then reload.
# In the server block. 403 rather than 444: a closed connection tells the
# operator nothing, and an agent that gets a status code can log it.
if ($http_user_agent ~* "(W3C-checklink|W3 Validator Services)") {
return 403;
}
Apache
In .htaccess or the vhost.
BrowserMatchNoCase "W3C-checklink" bad_bot
BrowserMatchNoCase "W3 Validator Services" bad_bot
<RequireAll>
Require all granted
Require not env bad_bot
</RequireAll>
Cloudflare
Security → WAF → Custom rules.
# Security → WAF → Custom rules, action: Block (http.user_agent contains "W3C-checklink") or (http.user_agent contains "W3 Validator Services")
WordPress
A child theme's functions.php, or a small plugin.
// functions.php of a child theme, or a small plugin. Runs before WordPress
// builds the page, so a blocked agent costs one PHP process and no queries.
add_action('init', function () {
$agent = $_SERVER['HTTP_USER_AGENT'] ?? '';
foreach (['W3C-checklink', 'W3 Validator Services'] as $needle) {
if (stripos($agent, $needle) !== false) {
status_header(403);
exit('Blocked: W3 Validator Services');
}
}
});
robots.txt is a request. The rules below it are the wall.
W3 Validator Services publishes a token, so the directive above will work for as long as it keeps honouring it — and nothing except its own good manners makes it. The server rules match on a header the requester sets, which stops the agent that says who it is and not the one that copies somebody else's name. Botscope verifies identity against DNS and published address ranges, records which check decided each request, and shows you the ones that lied.