How to handle UptimeRobot in robots.txt
UptimeRobot is an uptime monitoring service that pings configured URLs on an interval. This page explains why robots.txt is not the right way to stop its checks, how UptimeRobot identifies itself, and how to exclude it from analytics cleanly.
Why a Disallow will not stop it
UptimeRobot fetches the exact URL you told it to monitor to verify the endpoint responds. Like other uptime monitors, that check is about availability, not indexing, so a robots.txt Disallow is not the intended control and will not reliably stop it.
To change what is monitored, edit or pause the monitor inside UptimeRobot. That is the authoritative control; robots.txt is for crawler etiquette, not monitoring.
- UptimeRobot pings a fixed configured URL
- robots.txt does not reliably stop the ping
- Edit or pause the monitor in UptimeRobot itself
Identify and exclude
UptimeRobot's checks use a self-identifying user agent. Use that token to filter the checks out of analytics rather than attempting to block them. WebmasterID does this by classification; in raw logs, match the UptimeRobot token.
If the checks add load you care about, lengthen the monitoring interval in the dashboard instead of relying on a robots.txt rule that a monitor may not honour.
How it appears in analytics and logs
Periodic, regular hits from an UptimeRobot user agent are scheduled availability pings, not visits or search crawling. They tell you the monitor is active, not that traffic grew.
Diagnostic use case
Decide how to treat UptimeRobot checks: keep them for availability monitoring while keeping them out of human analytics and crawl-budget thinking.
What WebmasterID can help detect
WebmasterID classifies UptimeRobot as a monitoring bot, so its checks are separated from human analytics rather than counted as page views.
Common mistakes
- Expecting a Disallow to stop UptimeRobot availability pings.
- Treating interval pings as human page views.
- Using crawl-delay instead of adjusting the monitor interval.
Privacy and accuracy notes
UptimeRobot checks are machine pings of your own monitors. Identification uses the user agent only; no person and no visitor data are involved.
Related pages
- UptimeRobot bot — uptime monitoring checks
UptimeRobot is an uptime monitoring service that requests your URLs at intervals to confirm they respond. Its requests are automated availability checks, not search indexing or human visits. UptimeRobot identifies its monitor in the user agent so operators can recognise its checks.
- How to handle Pingdom's bot in robots.txt
Pingdom is an uptime and performance monitoring service whose checks fetch your pages on a schedule. This page explains why robots.txt is not the right tool to stop monitoring requests, how Pingdom identifies itself, and how to exclude it cleanly from analytics.
- Monitoring robots.txt for changes and errors
robots.txt is a single file that can accidentally block an entire site. This page explains why monitoring it matters, which failure modes to watch (Disallow: /, 404, 5xx, unexpected diffs), and how crawl-behavior signals confirm a problem.
- Bot vs human
See UptimeRobot pings separated from real visitors.
Sources and verification notes
- Google — How Google interprets robots.txtrobots.txt requests crawler compliance; monitors fetch fixed endpoints.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.