Checks for the services SaaS teams operate every day
Keyword Monitoring
Keyword monitoring confirms that important content is present in the response, not only that the endpoint returns a success code.
How it helps
Use keyword checks for pages where a plain HTTP status is too weak, such as customer portals, checkout pages, or rendered marketing content.
WebGuard can combine keyword validation with expected HTTP status ranges, request timeouts, methods, headers, body, and authentication.
When the keyword disappears, the incident flow and notification channels handle the failure like other monitor types.
Works well with
HTTP Monitoring
Monitor API and website endpoints with latency, method, header, body, auth, and status-code validation.
Expected HTTP Status Ranges
Define accepted status codes or ranges such as 200-299, 301, and 302 for each HTTP or keyword monitor.
Incident and Status Notifications
Receive incident, recovery, SSL, and domain expiry updates through Slack, Telegram, Discord, Microsoft Teams, webhooks, and in-app notifications.