Jetpack

What Jetpack does

When a site runs the Jetpack plugin, Automattic's servers call back to it - mostly via xmlrpc.php - to sync content, serve related posts, run downtime monitoring, and power other WordPress.com-hosted features. The jetmon variant is specifically Jetpack's uptime monitor. Automattic publishes the IP ranges these requests come from so hosts don't block them by accident.

Why it visits your site

You (or a previous owner or developer) installed Jetpack and connected the site to WordPress.com. If you don't run Jetpack, requests with this UA are someone spoofing it.

The bigger picture: utility & developer tools

This category is the honest miscellany of a server log: monitoring services, platform callbacks, and the default user agents of HTTP libraries. The unifying rule is that the string identifies software, not intent. A curl request might be your host's health check or a vulnerability probe; a python-requests hit might be a researcher or a scraper; a WordPress UA is one site talking to another. Reading these names as a threat list misses what they actually are - a census of the scripted web touching your site, most of it mundane, some of it yours.

robots.txt barely applies here, and not out of rudeness: monitors fetch the exact URL a customer configured, feed fetchers act on a user's subscription, and bare libraries simply ship with no robots logic at all. Blocking a default library UA filters the honest and the lazy while the malicious change one line and continue, so the effective levers are different - rate limiting by IP, watching which paths get requested, and reserving blocks for named services you can verify and have decided you don't want.

Should you block it?

Not if you use Jetpack - blocking it silently breaks stats, backups, and monitoring, and it's a common culprit behind mysterious Jetpack connection errors. If you've uninstalled Jetpack, it's fine to block; verify against Automattic's published IP list rather than trusting the UA string alone.

Block via robots.txt

Add these lines to the robots.txt at your site root to ask Jetpack to stay away:

User-agent: Jetpack
Disallow: /

Remember that robots.txt is a request, not a lock - compliance is voluntary, and enforcement happens at the server. Viz's AI Control pairs robots.txt rules with server-level 403 responses and then probes your site to verify the block is actually holding.

How to see Jetpack traffic on your site

You have three windows onto it, each with a catch. Raw hosting access logs contain every Jetpack request, but many managed WordPress hosts don't expose them, and when they do you are grepping text files by hand. A CDN dashboard sees the traffic at the edge, but it lives outside WordPress and speaks in totals, not in your site's terms. And JavaScript analytics - GA4 and friends - will never show it at all, because Jetpack doesn't run scripts.

Viz's answer is the request log: filter to Jetpack and read exactly which URLs it fetched and when, right inside wp-admin - then watch the same filter after any blocking decision to see whether the visits stopped, slowed, or kept coming.