Keyword Monitoring: Catch the Outages Health Checks Miss

Here's a scenario that happens more than anyone likes to admit: your health check endpoint returns 200 OK. Your dashboard is all green. But your actual website is showing users an error message, a maintenance page, or worse — your competitor's content.

Welcome to the world of failures that status codes can't detect.

When 200 OK Doesn't Mean OK

The Default Error Page

Many web servers and load balancers return 200 OK with a default error page when your application crashes. The server is technically responding — it's just not responding with your content.

The CDN Cache Gone Wrong

Your CDN might serve a cached version of a maintenance page long after the actual maintenance ended. Status code: 200. Content: "We'll be back shortly." Duration: indefinite.

The Defacement

If your site gets compromised, attackers often replace your content while keeping the server running normally. Everything looks fine at the HTTP level.

The Partial Render

A JavaScript error might prevent your SPA from rendering. The HTML shell loads (200 OK), but users see a blank page or an error boundary.

The Third-Party Embed Failure

A failing third-party script (analytics, chat widget, ad network) can sometimes prevent your page from fully loading or display error messages within your layout.

How Keyword Monitoring Works

Keyword monitoring adds a critical layer on top of HTTP checks:

1. Fetch the page (just like a regular HTTP check)
2. Check the status code (just like a regular HTTP check)
3. Search the response body for expected keywords
4. Alert if the keywords are missing or unwanted keywords appear

Two Types of Keyword Checks

Positive Keywords (Must Contain)

Verify that expected content is present:

• Your product name on the homepage
• "Add to Cart" on product pages
• Specific data that proves the API is returning real results
• Your copyright notice in the footer

Negative Keywords (Must Not Contain)

Alert when unwanted content appears:

• "Error", "Exception", "Service Unavailable"
• "Maintenance mode"
• "Default page" or other framework defaults
• "Forbidden" or "Access Denied"

Practical Keyword Monitoring Strategies

For E-Commerce Sites

• Homepage: Check for your brand name and "Shop" or "Products"
• Product page: Check for "Add to Cart" and the price format
• Cart page: Check for "Checkout" or "Proceed"
• Checkout: Check for payment form elements

For SaaS Applications

• Login page: Check for "Sign In" or "Log In"
• Dashboard: Check for user-specific content markers
• API responses: Check for expected JSON keys

For Content Sites

• Homepage: Check for recent article titles
• Article pages: Check for article body content
• Search results: Check for result count or listings

Common Pitfalls

Keywords That Change

Don't monitor for content that changes frequently (like "Today's Deal: Widget X"). Monitor for structural elements that should always be present.

Case Sensitivity

Make sure your keyword check handles case correctly. "Log In" and "log in" are different strings.

Dynamic Content

SPAs and JavaScript-rendered content might not be in the initial HTML response. Consider using a monitoring tool that can render JavaScript, or monitor your API endpoints directly.

The Bottom Line

HTTP status codes tell you if your server is responsive. Keyword monitoring tells you if your site is actually working. For critical pages, you need both.

It takes 30 seconds to add a keyword check to an existing monitor. The first time it catches an issue that a regular health check missed, you'll wonder how you ever lived without it.