Keyword & Content Monitoring
Verify your content is always what you expect.
A page that returns 200 OK can still serve the wrong content — a blank page, an error message beneath a header, a cached version of a deleted page, or defaced content. Keyword monitoring fetches your pages on a schedule and verifies that specific words, phrases, or identifiers are present (or absent) in the response, catching content regressions that HTTP status codes would never surface.
HTTP 200 doesn't mean the page is correct
Many of the most damaging content failures are completely invisible to uptime monitoring. A CDN caching an error page returns 200. A CMS that crashes mid-render serves a blank body with 200. A page after a botched deployment loads the header and footer but renders empty content between them — all returning 200 with no indication of a problem unless you're looking at the content itself.
Keyword monitoring provides a layer of content validation that uptime monitoring cannot. By checking that a specific term — a product name, a critical sentence, a page element — is present on every check, you catch these invisible failures immediately rather than when a customer reports seeing the wrong content.
Key features
Keyword presence checks
Alert when an expected keyword or phrase is absent from the page response body.
Keyword absence checks
Alert when a term appears that shouldn't — such as "error," "exception," or a known failure message.
Content change detection
Alert when the content of a page changes significantly from the baseline — useful for detecting defacement or unauthorized edits.
Scheduled checks
Fetch and validate page content on any interval — from every minute to daily — based on how frequently the content changes.
Free content diagnostic tools
Validate your content automatically
NetTests fetches your pages on a schedule and verifies that the right content is present — catching blank pages, caching errors, and content regressions that status codes miss.
Start monitoring free →