A content alert is only useful when the changed or missing text represents a problem you want to know about. Dynamic pages can change legitimately, so the assertion or baseline must be chosen around stable content.
Common causes
- Timestamps, counters or rotating availability values.
- Personalised content based on cookies or account state.
- A/B tests, localisation or device-specific templates.
- Cookie banners and consent messages.
- Rotating promotions, prices or stock information.
- JavaScript-generated content that is not present in the server response.
How to reduce noise
Choose a stable heading or service phrase for required text. Choose a known error phrase for forbidden text. For hash mode, monitor a stable endpoint or accept that a full response change requires review rather than automatically meaning an outage.
Investigate an alert
Open the run evidence, compare the response hash or assertion result with the last good run and check recent deployments, templates and edge responses. If the change is expected, update the monitoring configuration deliberately.
Limitation
WebCheck compares the response available to its bounded request. It does not render an arbitrary browser session to reproduce every client-side variation.