Keyword Monitoring
A 200 response doesn't mean the page is right. Keyword monitoring checks the content too.
Servers can return a healthy status code while showing an error page, a maintenance screen, or someone else's content entirely. Keyword monitoring adds a content check on top of a regular website check: Kawze looks for (or checks the absence of) specific text in the response body, so a technically-200 page that says "Service Unavailable" still gets flagged as down.
How it works
- Add a keyword check to any HTTP monitor alongside its status code rule.
- Set Kawze to require the keyword be present (e.g. confirm a checkout page still says "Add to Basket") or absent (e.g. flag if "Error" or "Maintenance" appears).
- Every check scans the response body for a match as part of the same request - no extra monitor or check interval needed.
- A missing (or unexpectedly present) keyword counts toward the failure threshold just like a bad status code.
Why it matters
- Catches soft failures: error pages served with a 200, empty pages, wrong-language content after a CDN or region issue.
- Verifies specific functionality stays intact, like a price, a login form, or a "Add to basket" button.
- No separate monitor to manage - it is a rule on your existing website monitor.
Frequently asked questions
Does keyword monitoring need a separate monitor?
No. Keyword matching is a rule on a regular HTTP monitor, checked on the same request - you're not paying for or configuring a second monitor.
Can I check that a word is NOT on the page?
Yes. You can require a keyword be present, or flag the check as failed if a keyword like "Error" or "Maintenance" appears.
Does keyword monitoring slow down my checks?
No. The keyword scan runs against the same response your website monitor already fetched, so there is no extra request and no added latency to your check interval.
What are common uses for keyword monitoring?
Confirming a checkout page still shows "Add to Basket" after a deploy, catching maintenance pages left up by mistake, verifying a login form renders instead of an error page, and detecting when a CDN serves stale or wrong-region content.
This capability lives on Kawze's http monitor - see that page for the full feature list and pricing for that uptime monitor type.