On this page
Plan how to monitor a website with UptimeRobot #
The sample monitors a small studio's home page and, as a variation, checks for its contact-page heading. Follow the official first-monitor walkthrough. This guide uses documented controls and doesn't require taking a live website offline.
Use the final URL after any normal redirects, including HTTPS and the intended hostname. A test subdomain or an old domain can produce a perfectly accurate alert about the wrong destination.
1. Create an HTTP monitor #
Sign in to the dashboard and select + Add New Monitor. Choose HTTP(s) as the monitor type for a normal website.
HTTP monitoring checks the web endpoint. It is a better starting point for this example than ping, which checks whether a server responds to a different kind of network request. The monitor form should show its URL and configuration fields.
2. Enter the URL and a recognizable name #
Fill in URL with the public home-page address. UptimeRobot fills Friendly Name from the URL; change it to a label such as Studio home page.
The name appears in alerts, so include enough detail to identify the service. A message saying Home page can be confusing if the account watches several client sites. Keep credentials and secret query values out of both the label and the URL.
The expected result is one monitor whose destination and friendly name clearly refer to the studio's production page.
3. Assign the alert contacts #
Review alert contacts and select who should receive this monitor's notifications. For a first setup, choose an email address you can reliably receive at and check the address for spelling errors.
The official walkthrough also covers notification delay and repetition. Use a delay only when you have a reason to tolerate a short interruption before contacting someone. Repeated alerts can help with an ongoing incident, but they need to fit the person's response routine.
Don't assume that creating an account automatically routes every monitor to every possible channel. Contacts belong in the monitor setup and need review when the responsible person changes.
4. Choose the interval and region #
Review monitoring interval and region in the form. Free uses five-minute checks. Choose the available region that makes sense for the site's audience and the account's plan.
A regional check sees the route from that location. If your customers are spread across countries, a single check location can't prove the website works equally well for all of them. Begin with the public endpoint, then add coverage when the business has a reason for it.
5. Save and inspect the first checks #
Select Create monitor. After the scheduled check, inspect its Up, Down, or Paused status and the documented Response Time, Logs, and Incidents views.
For a working sample page, expect an Up result when the service can reach it successfully. If it shows Down, investigate the check before changing the website. The browser you use and a monitoring service can receive different responses from a firewall or CDN.
Review the alert contacts once more from the saved configuration. The important outcome is a monitor and a receiving person, not simply a green dashboard row.
6. Record what an alert means #
Write a short response note for the site owner: the monitored URL, the responsible contact, and where to check the website and hosting status. A home-page HTTP failure calls for a different investigation from a certificate warning or a missed scheduled-job heartbeat.
For the studio example, the first action is to open the public page and check whether the hosting or CDN reports a problem. If the page loads normally, inspect monitoring logs and access controls before declaring the incident resolved.
Keep this note with the site's maintenance records. Update it when the person responsible or the public URL changes.
Known problems and fixes #
The monitor says Down but the page opens
UptimeRobot's debugging guide explains firewall, CDN, CAPTCHA, and geographic blocks. Review those logs for the monitoring request. If legitimate checks are blocked, allow the current monitoring IPs through the site's applicable rule without turning off protection for everyone.
A Telegram group doesn't receive alerts
The Telegram groups feedback request is completed, and the current Telegram instructions explain the setup. Invite the bot to the group and send the activation message supplied by the dashboard. Each chat or group needs its own integration. Telegram requires Solo or higher under the current integration overview.
A protected webhook refuses notifications
An older HTTP-auth feedback request asked how to protect callback endpoints. Current webhook documentation supports custom headers such as Authorization. Webhooks require Team or Scale. Stay within ten headers and 4 KB combined, then verify the receiver gets the expected header; exceeding the documented limit drops the custom headers.
Alerts stop after a connection changes
The missing-notification guide advises checking revoked or rotated integrations. Reconnect the affected destination and review the monitor's selected contacts. A working monitor doesn't repair a deleted channel or an expired connection.
Troubleshooting #
| Problem | Likely cause | Fix |
|---|---|---|
| Browser works, monitor is Down | WAF/CDN blocks automated requests | Inspect logs and allow legitimate monitoring traffic |
| Ping and website disagree | Ping doesn't check the web application | Use HTTP(s) for the page |
| Alert never reaches the owner | Wrong contact or mailbox filtering | Review monitor contacts and receiving mailbox |
| Chat alerts stopped | Revoked connection or changed chat | Reconnect and review the target |
| Webhook rejects the request | Missing auth header or receiver failure | Review documented headers and endpoint response |
| Short outages don't appear | They fall between scheduled checks | Consider the interval and business need for faster checks |
Variations #
Check a page's expected content
Choose a Keyword monitor, enter its URL and expected text, and select whether to alert when the keyword is found or missing. For the sample contact page, use a stable visible heading. A frequently edited sentence creates avoidable alerts.
Add several related URLs
The documented Monitor Wizard can prepare several checks; review them before selecting Create monitors. Name each service clearly so the resulting alert identifies the affected page.
Add a public status page
Free includes one basic status page on a UptimeRobot URL. Use it when visitors need a place to check service status, and decide who will add human incident updates. A status page is most helpful when it explains the service affected and the next update time.
Completion checklist #
- The monitor uses the final public URL and HTTP(s) type.
- Its name identifies the service in an alert.
- The saved contacts reach the responsible person.
- The first scheduled checks appear in logs.
- Any access-control exception is limited to legitimate checks.
- The owner has a short incident response note.
Next steps #
Compare UptimeRobot vs Uptime Kuma and the free website uptime shortlist. See UptimeRobot, its alternatives, and HetrixTools for other monitoring arrangements.
