Keyword and status-code checks
A page that answers 200 can still be broken: an empty product list, a database error printed on the page, a checkout that says "temporarily unavailable". heyUptime lets you say which status codes count as up and which text must, or must not, appear in the page, and treats anything else as down.
Accepted status codes
In short: Leave the field empty and anything below 400 is up. Fill it in and only the codes you list count.
Write the codes you expect, separated by commas. Three formats are accepted and can be mixed:
- A single code: 200, or 200, 204
- A range: 200-299
- A class: 2xx, 3xx
| Accepted codes | Page answers | Result |
|---|---|---|
| (empty) | 301 redirect | Up |
| 200 | 301 redirect | Down: HTTP 301 (expected 200) |
| 2xx | 204 No Content | Up |
| 401 | 401 Unauthorized | Up (an endpoint that should refuse anonymous requests) |
| 200, 3xx | 503 | Down: HTTP 503 (expected 200, 3xx) |
A keyword that must appear
Enter up to 200 characters of text that a healthy page always contains, such as "Add to cart", your company name in the footer, or a JSON field like "status":"ok". The comparison ignores letter case. If the page answers with an accepted status but the text is missing, the check fails with the message: The page answered 200 but doesn't contain "Add to cart".
A keyword that must not appear
Switch the mode to "must not contain" for error text that only shows up when something is wrong: "Error establishing a database connection", "Out of stock", "Fatal error", "maintenance mode". When the text is found, the alert says: The page contains "Fatal error", which means something is wrong.
GET, HEAD or POST
GET is the default and reads the whole page. HEAD asks only for the headers, which is lighter on your server but means keyword checks can't run (there is no body to search). POST suits endpoints that only answer to a submission; heyUptime sends the request with an empty body.
| Method | Reads the body | Keyword checks | Good for |
|---|---|---|---|
| GET | Most pages and JSON endpoints | ||
| HEAD | Large pages where only the status matters | ||
| POST | Form handlers and webhooks that reject GET |
How failures are reported
A wrong status code or a missing keyword is confirmed like any other failure: the page is requested again 5 seconds later, and only a second failure opens an incident. The alert's cause line names the exact rule that failed, so the person who reads it knows whether to look at the server, the deploy or the content.
Questions
Can I monitor a JSON API endpoint?
Yes. Add the endpoint's URL as a website monitor, set the accepted code to 200 and the keyword to a field a healthy answer always contains, such as "status":"ok".
Is the keyword check case-sensitive?
No. "add to cart" matches "Add to Cart". Leading and trailing spaces are trimmed.
Does a 301 or 302 redirect count as up?
By default, yes: anything below 400 is up. If you want to be told when a page starts redirecting, set the accepted codes to 200.
Can I check for more than one keyword?
One keyword per monitor. If you need two rules on the same page, add the page twice with a different keyword on each; each monitor counts towards your plan's limit.
Catch the outages a 200 hides.
Add a page, type the text that should always be there, and heyUptime tells you the moment it isn't. Free for 14 days, no card.
Related
Updated October 8, 2026.