WordPress uptime monitoring: a practical setup

Monitor the part of WordPress that matters

A server can return a successful response while WordPress shows an empty template, a database error, or a maintenance page. Start with a webpage checker for the public page that matters most to visitors, not only the domain root.

For a brochure site, that may be the homepage. For a store, monitor a product or shop page. For a membership site, use the public login page. Simple Ping does not submit credentials, so choose a page that can be checked without signing in.

Recommended WordPress setup

1. Create a webpage checker and enter the complete HTTPS URL.
2. Add a short, stable search string that appears in the page’s HTML.
3. Give the checker a clear display name, such as Client name - Store.
4. Use a group such as WordPress, Production, or the client name.
5. Run Check state now before saving so the URL and text can be verified immediately.

Reduce alert noise without hiding a real outage

Choose text that belongs to the page template and changes rarely. Avoid prices, inventory counts, rotating banners, dates, visitor names, translated phrases that vary by browser, and content injected only after JavaScript runs.

For most public WordPress sites, consider the checker down after two consecutive downs. One is faster; two gives another scheduled observation before an email is sent. Repeated alerts are useful for a service that must be fixed immediately, but one notification per state change is quieter for routine client monitoring.

Understand what failed

Open the checker’s history after a DOWN. New incidents record the HTTP response code and a normalized failure reason. When the server returned a page but the expected text was absent, View page shows the captured source as plain text so it cannot execute in the dashboard.

• HTTP 500: WordPress, PHP, or an upstream application failed.
• HTTP 403: a firewall or security plugin may have blocked the monitoring request.
• HTTP 200 with missing text: the server answered, but the expected page did not.
• Connection or TLS failure: investigate DNS, the web server, certificates, or the hosting network.

Add a short incident description after resolving the problem. Over time, the history becomes a useful maintenance record for the site.