Keyword monitoring
Keyword monitoring verifies that a page or API response actually contains the content you expect, not just that it responds. A monitor can return a 200 status code while serving an error page, an empty template, or a broken deploy. Checking for a keyword catches these silent failures.
How it works
On every check, Hyperping fetches the response body of your HTTP monitor and verifies that it includes the text you configured. If the text is missing, the monitor is considered down: we double-check from your other selected regions to rule out a false positive, then open an outage and alert your channels, exactly like a failed status code.
Set up a keyword check
- Create a new HTTP monitor or edit an existing one. See Create a monitor.
- Open the advanced HTTP settings.
- In Text body assertion, enter the text that the response body must include.
- Save the monitor.
The check runs at your monitor's regular interval, from all the regions you selected.
Choosing a good keyword
- Pick stable text. A footer mention, a product name in the hero, or a fixed JSON field name are good candidates.
- Avoid dynamic content. Timestamps, usernames, cart counts, or A/B tested copy will cause false alarms.
- Keep it exact. The response body must include the text exactly as you typed it.
- For APIs, assert on structure. A key like
"status":"ok"validates that your endpoint returns real data, not an error payload.
Common use cases
- Soft errors: catch error pages served with a 200 status code.
- Deploy regressions: detect a page that renders empty after a bad release.
- CMS issues: verify critical content is still published.
- API contracts: confirm an endpoint returns the expected payload, not just a response.
Plan availability
Keyword monitoring is included on every plan, including the Free plan.
Troubleshooting
If a keyword check fails unexpectedly, open the monitor's logs to inspect the actual response we received. Frequent causes are localized content, cookie or consent walls, and pages that only render the keyword client-side with JavaScript. For content that requires a real browser to render, use a browser check instead.
