Keyword Monitoring

Confirm critical text appears in application responses and rendered pages, and alert when known failure text shows up even on a 200 response. Keyword monitoring catches a whole class of failures that status-code checks miss: a page that loads successfully but displays the wrong content, an error message, or a broken template.

What it checks

A keyword monitor fetches a URL on a schedule and inspects the response body for the text you specify:

• Expected content present - whether a required term or phrase appears in the response, confirming the page or endpoint rendered correctly.
• Failure text absent - whether known error or failure text is missing, so an error message showing on an otherwise healthy 200 response raises an alert.
• Template and copy regressions - detection of unexpected content changes in critical flows, such as a broken template or missing section.
• Content integrity - verification that user-facing text is intact, including across language or regional variants.

Configuration

Keyword monitors build on a standard URL check with content matching:

• URL - the page or endpoint whose response should be inspected.
• Keyword - the term or phrase to look for in the response body.
• Match mode - whether the keyword should be present (the check fails if it is missing) or absent (the check fails if it appears), letting you guard against both missing content and unexpected error text.
• Check interval - how often the monitor runs.