Content alerts can be noisy when a phrase changes during normal operation. WebCheck checks for one configured phrase in the HTTP response; it does not compare the full response with a saved content baseline.
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, distinctive phrase for a required-text check, or a known failure message for a forbidden-text check. Keep the phrase exact and case-sensitive, and avoid values that change on each request.
Investigate an alert
Open the check run and review its status, evidence and response hash. Compare the result with nearby runs and check recent deployments, templates and edge responses. If the phrase is expected to vary, replace it with a more stable one or monitor a dedicated health endpoint.
Limitation
WebCheck makes a bounded HTTP request; it does not render an arbitrary browser session or reproduce every client-side variation.