- Article
- Intermediate
- 1 minute read
- Reviewed August 4, 2026
- WordPress maintenance and troubleshooting
Monitoring detects when WordPress or one of its dependencies stops behaving as expected.
A homepage returning HTTP 200 is useful evidence, but it does not prove that login, checkout, email or scheduled tasks work.
Uptime Checks
Monitor several meaningful URLs from outside the hosting environment.
Check:
- HTTP status.
- response time.
- expected page content.
- TLS certificate.
- redirects.
- DNS.
- geographic availability.
Synthetic Transactions
Critical sites can test workflows such as:
- Login.
- Search.
- Form submission.
- Add to cart.
- Checkout in sandbox mode.
- API response.
- account access.
Avoid creating real orders or user data unintentionally.
Error Monitoring
Collect PHP, web-server, application and browser errors according to risk.
Protect logs from public access and avoid recording passwords, session cookies or unnecessary personal data.
Site Health
WordPress Site Health can report configuration, update, loopback, REST, cron and caching observations.
It is a diagnostic input rather than a complete monitoring system.
Alert Design
Alerts need:
- Severity.
- owner.
- escalation.
- response target.
- runbook.
- suppression for planned maintenance.
- resolution record.
Too many low-value alerts create fatigue.
Frequently Asked Questions
Is one-minute uptime monitoring required?
Choose an interval based on business impact and provider limits.
Does Site Health replace external monitoring?
No. Site Health runs within WordPress and cannot report reliably when the entire site is unavailable.
Continue Learning
Previous: Cleaning Unused WordPress Data