Uptime monitoring checks whether a website responds from outside the hosting platform. It is useful, but it does not replace backups, application logs, or real checkout and form testing.
What a Basic Monitor Checks
A simple HTTP monitor loads a URL every few minutes and records whether it receives an acceptable response. For many small business sites, checking the home page over HTTPS is a sensible starting point.
For important sites, monitor more than the home page. A home page can work while checkout, login, or a contact form is broken.
Useful Checks
- HTTPS home page response.
- Important landing pages.
- Login page or customer portal.
- Checkout or booking flow, where safe to test.
- SSL certificate expiry.
- Keyword checks for expected page content.
What Uptime Monitoring Does Not Prove
A green uptime check does not prove that emails are sending, payment callbacks work, stock levels update, or every plugin is healthy. It only proves that the monitored URL returned the expected response at the time of the check.
Responding to an Alert
When an alert arrives, check from more than one network before assuming the whole site is down. Then review:
- DNS resolution for the domain.
- SSL certificate status.
- Website error logs.
- Recent updates, deployments, or content changes.
- Resource usage and disk usage.
Avoid Alert Fatigue
Very short check intervals can create noisy alerts for momentary network issues. Choose checks that match the value of the website, and send alerts to someone who can actually investigate them.
Self-Hosted Monitoring
Tools such as Uptime Kuma need a persistent process, so they belong on a VPS rather than shared PHP hosting. If monitoring your main website, host the monitoring system somewhere separate from the site being checked.
For troubleshooting after an alert, read How to Check Website Error Logs in Enhance and How to Check SSL Certificate Status in Enhance.
