Monitoring that explains what happened
Keyword and content monitoring for websites
“200 OK” is not always a healthy page. Confirm that meaningful text remains present and that known error or maintenance messages stay absent.
Require a meaningful marker
For a checkout page, require a stable marker such as Checkout. Choose content returned in the HTTP response; JavaScript-rendered text that appears only after a browser runs is not available to this check.
Reject a known failure message
Set forbidden text such as Maintenance or a specific database error marker. A matching forbidden phrase fails the check and follows the normal incident confirmation flow.
Keep checks useful over time
Avoid volatile copy, dates and personalized strings. Review expected text when you deploy. Full response bodies are not stored in monitoring history; the result identifies the failed assertion.
Common questions
Is matching case-sensitive?
Yes. Use the exact text present in the response and test it after configuration.
Does this take screenshots or run JavaScript?
No. It checks the returned HTTP response body, within the response-size limit. Browser-based synthetic monitoring is outside this phase.