Skip to main content

How to block MediaMonitoringBot

Operated by MediaMonitoringBot. MediaMonitoringBot crawls and indexes news and media publishers websites for a new materials and try to match it against keywords provided by our customers (subscribers) and send them updates based on that information.

How it identifies itself

MediaMonitoringBot/1.1 (+https://mediamonitoringbot.com/crawler; [email protected])

robots.txt

What the agent asks to be told. It obeys this or it does not — nothing enforces it.

robots.txt
User-agent: MediaMonitoringBot
Disallow: /

nginx

In the server block, then reload.

nginx
# 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 ~* "(MediaMonitoringBot/|MediaMonitoringBot)") {
    return 403;
}

Apache

In .htaccess or the vhost.

Apache
BrowserMatchNoCase "MediaMonitoringBot/" bad_bot
BrowserMatchNoCase "MediaMonitoringBot" bad_bot

<RequireAll>
    Require all granted
    Require not env bad_bot
</RequireAll>

Cloudflare

Security → WAF → Custom rules.

Cloudflare
# Security → WAF → Custom rules, action: Block
(http.user_agent contains "MediaMonitoringBot/") or (http.user_agent contains "MediaMonitoringBot")

WordPress

A child theme's functions.php, or a small plugin.

WordPress
// 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 (['MediaMonitoringBot/', 'MediaMonitoringBot'] as $needle) {
        if (stripos($agent, $needle) !== false) {
            status_header(403);
            exit('Blocked: MediaMonitoringBot');
        }
    }
});

robots.txt is a request. The rules below it are the wall.

MediaMonitoringBot 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.

Others like it

Everything we know about MediaMonitoringBot