WebCheck can detect when a configured response changes or when expected text disappears. Content monitoring is useful for deployment regressions, maintenance pages and important user-facing messages, but dynamic pages need careful assertions.
Baseline monitoring
A hash-mode content check records a baseline hash after a successful initial result. Later responses are compared with that baseline. A different hash produces a content-changed result for review.
Required and forbidden text
A required-text assertion fails when the configured text is missing. A forbidden-text assertion fails when the configured text is present. Use stable, distinctive text rather than a value that changes on every request.
Good candidates
Useful assertions include a checkout page containing its checkout heading, a status page containing an operational message, or a public page not containing a known error message. These are examples, not claims about any particular customer incident.
Dynamic content limitation
Timestamps, rotating offers, personalised content, localisation, cookie banners and A/B tests can create legitimate differences. If a page changes normally, monitor a stable phrase or a dedicated health endpoint instead of its complete response hash.