1. Confirm the product and provider expose the site-health tool and that the customer service is active.
2. Open the correct service or website and inspect the configured domain and available health checks.
3. Run an initial check and read the individual results rather than relying only on an overall colour or status.
4. Verify the normal WHMCS cron is collecting any scheduled monitoring work.
5. Review the resulting history after later checks and confirm timestamps correspond to your operating schedule.
6. Enable and preview the relevant Website Health Alert email if you intend to notify customers.

Start with the affected hostname and the specific condition reported. Check DNS resolution, certificate validity, HTTP response and whether the page is expected to be public. A staging site protected by authentication can produce a different result from a public homepage without being broken.

Compare the monitor's observation with an independent request and the server's logs. Maintenance, rate limiting, firewall rules or a redirect problem may explain the failure. Correct the actual cause and rerun the relevant check.

Historical performance is based on collected samples. A new website or recently enabled monitor may have little history. Missing samples should be investigated as missing monitoring data, rather than reported as a successful period of perfect uptime.

PageSpeed scoring is a separate optional integration that requires its configured provider key. Server traffic data and live activity also come from their own sources. Do not combine these metrics into an unsupported claim about every visitor's experience.

Decide who reviews repeated alerts, how support verifies them and when an upstream server team should be involved. Include the domain, timestamp, exact check and recent changes in the incident record. Avoid sending credentials or full customer data when a simple response code and log excerpt are sufficient.

Check the saved product tool profile, provider capability, service status and user permission. Optional server integrations can affect which detail is available. Restore the intended configuration rather than adding a cosmetic link that cannot perform the check.

After changes to DNS, CDN, PHP or the website, verify the relevant health checks again. A passing homepage check should be followed by application-specific tests when checkout, login or other business functions were affected.

• Enable optional website insights, malware and performance tools
• Configure and verify the WHMCS cron for Hosting Suite
• Connect Cloudflare and roll out Global CDN safely
• Manage website migration requests and source credentials