What Is Keyword Monitoring? Response Body Checks

Keyword monitoring (sometimes called content monitoring) is an HTTP check that inspects the response body for a specific string. You tell the monitor to alert if a keyword is present (e.g., "database error" appearing on your page) or if an expected keyword is absent (e.g., "Welcome back" missing from your homepage).

This catches a class of failure that plain HTTP monitoring misses: the server returns 200, the page loads, but the content is wrong. A CMS glitch renders a blank template, a database connection fails mid-page and dumps an error where your product listing should be, or a deploy ships a broken build that still serves HTML. Status-code-only monitoring sees green; keyword monitoring sees the problem.

Use an absence check (alert when keyword is missing) for content that must always be there: your logo alt text, a known product name, the logged-out homepage headline. If it disappears, something has broken the render path. Pick a string that's stable across deploys — not a price or a date that changes weekly.

Use a presence check (alert when keyword appears) for error signatures: "Fatal error", "Exception", "maintenance mode", "Database connection failed", a specific error code your app emits. This turns a silently broken page into a paged incident. SurePing supports both modes and checks the full response body, not just the first few kilobytes.

Reach for keyword monitoring whenever a 200 response doesn't guarantee a working page: e-commerce product pages, dynamic dashboards, API endpoints that return 200 with an error payload, and any page whose content is generated server-side from a database. For static assets and simple status endpoints, plain HTTP monitoring is enough.

Keyword monitoring is included on every SurePing plan, including Free, alongside HTTP, ping, port, SSL, and heartbeat monitors. You can mix keyword and HTTP checks on the same URL if you want both signal types.