StatusEagle
Keyword monitoring

Keyword monitoring for pages that are “up” but broken

A checkout that renders an error template still returns HTTP 200, so a status-code check calls it healthy. Keyword monitoring reads the page and alerts you when the text that proves it works disappears, or when an error message shows up.

Keyword · shop.example.com/cart
Live check snapshot
Active
Looking for“Proceed to checkout”
Modemust be present
HTTP status200
Keyword foundNo
Confirmed from2 of 3 locations

Example check · demo data

In brief

Keyword monitoring fetches a web page on a schedule and checks whether a specific word, phrase or pattern is present or absent in the response. It alerts you when the content is wrong, even if the server returns a successful status code.

1

Why a 200 status isn’t proof a page works

Most modern stacks catch errors and render something friendly instead of crashing. That’s good for visitors and bad for monitoring: the error page is served with 200 OK. We see the same handful of cases over and over:

In every case the server is up. Only the content tells you something is wrong.

A CMS loses its database connection, but the page cache keeps serving an empty template.
A product API times out and the storefront renders “No products found”.
A deploy ships a blank page because a JavaScript bundle failed to build (the HTML shell still loads).
A CDN serves a stale maintenance page long after maintenance ended.
A hacked site starts serving injected spam links alongside the real content.
2

How StatusEagle keyword monitoring works

Fetch. On each interval, a monitoring location requests the URL and reads the response body.
Match. The body is searched for your keyword. Choose whether it must appear (e.g. a price, a button label) or must not appear (e.g. “Fatal error”, “Database error”).
Match options. Plain text, case-sensitive matching, or a regular expression when the text varies.
Verify. A failed match is re-checked from the same location, then from another location, before it becomes an alert.
Alert. Your team is notified through the channels on the monitor, and an incident records what was expected and what was found.
3

Choosing a good keyword

The keyword should appear only when the page works properly. Good choices, from our own setups:

Avoid words that also appear in your error template (your company name, the navigation), and avoid content that changes often, like prices during a sale.

PageMust be presentMust NOT be presentProduct pageCheckoutLoginBlog / CMSJSON health endpoint
“Add to cart”“Out of stock” on a hero product
“Order summary”“Something went wrong”
the name of the password field“Service unavailable”
a string from your footer“Error establishing a database connection”
"status":"ok""degraded"
4

When to use a regular expression

Use regex when the text you expect varies but has a stable shape. For example, match any price with \$\d+\.\d{2}, or match a JSON field regardless of spacing with "status"\s*:\s*"ok". Keep patterns simple; a regex that’s too clever becomes the thing that breaks.

5

What keyword monitoring can’t see

Content rendered by JavaScript. The check reads the HTML the server returns. If text is injected later by a script, the monitor won’t see it. Check a server-rendered string instead, or monitor the API that supplies the data.
Multi-step flows. A keyword check is one request. It can confirm the checkout page loads correctly, not that a full purchase completes.
Per-user content. Pages that differ by cookie or geography may show different text to the monitor than to your customers.
FAQ

Frequently asked questions

Still deciding? Start monitoring free and verify your first service in ~2 minutes.

Keyword monitoring checks a web page on a schedule for a specific word, phrase or pattern, and alerts you when it is missing (or when an unwanted string appears), even if the page returns HTTP 200.

GET STARTED IN MINUTES

Your first monitor takes about two minutes.

Free plan: 10 monitors, 3 locations, 1 status page. No credit card.