200 OK doesn't mean it works.
Check the words on the page.
Confirm critical text appears in your pages and API responses, and alert when known failure text shows up even on a successful response. Catch defacement, error messages, and content regressions.
Keyword Assertions
A 200 OK is not a correctness test.
Your server can return a success code while serving a broken page, error modal, or injected content. Keyword monitoring gives you ground truth, the actual text on the page.
Presence & absence assertions
Define exactly what must appear (and what must never appear) in every response. Required text confirms the page rendered correctly; forbidden text catches error messages and failure states that slip through with a 200.
- Assert required text is present
- Alert when forbidden or error text appears
- Case-insensitive and exact match options
Pairs with HTTP checks
Availability and correctness in a single monitor. Layer keyword assertions on top of status-code and latency checks so one configuration covers the full picture: the server is up, it's fast, and the right content is there.
- Combine with status-code and latency checks
- One monitor for uptime and correctness
- Verify content across language variants
Combined Check Results
Catch silent regressions
A deploy ships a broken template. A CMS editor deletes a critical CTA. An injected script replaces checkout content. These failures return 200, only a keyword check will catch them before your customers do.
- Spot template regressions in critical flows
- Detect defacement or injected content
- Alert before customers notice
Catch the broken page that still returns 200.
Add a keyword check in under a minute.
Create Your First Monitor