UptimeRobot
Uptime monitoring service that pings URLs its customers asked it to watch.
Mozilla/5.0+(compatible; UptimeRobot/2.0; http://www.uptimerobot.com/)Official documentation: uptimerobot.com
What UptimeRobot does
UptimeRobot sends lightweight HTTP checks to a specific URL at regular intervals - every five minutes on the free tier - to confirm the page is up and how fast it responds. It doesn't crawl or follow links; it hits the one address someone configured and reads the status code.
Why it visits your site
Someone set up a monitor for your URL. Usually that's you, your developer, or your agency - though occasionally a competitor or client is quietly watching your uptime too.
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?
It doesn't consult robots.txt - monitors fetch the exact URL a customer configured, so a robots rule wouldn't change anything anyway. If it's your monitor, blocking it just triggers false downtime alerts. If you didn't set it up and the pings bother you, block the UA or UptimeRobot's published IPs at the firewall.
Block via robots.txt
Add these lines to the robots.txt at your site root to ask UptimeRobot to stay away:
User-agent: UptimeRobot 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 UptimeRobot traffic on your site
You have three windows onto it, each with a catch. Raw hosting access logs contain every UptimeRobot 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 UptimeRobot doesn't run scripts.
Viz's answer is the request log: filter to UptimeRobot 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.