Presence and absence assertions
Assert that a keyword or phrase IS on the page, or that it is NOT — both modes supported on the same monitor.
Keyword Monitoring
Know when your content
Know when your content
changes without permission.
Assert the presence or absence of any keyword, phrase, or regex pattern on any page — and get alerted the moment expected text vanishes or unexpected text appears. Content integrity, confirmed on every check.
Free tier included
No credit card
2-minute setup
acme.com / terms HealthyLIVE
CHECKS · 24H288
LAST MATCHPass
PATTERNregex
iad-192ms
sfo-1118ms
fra-1147ms
sin-1181ms
syd-1202ms
What you get
Content checks that go beyond a 200 OK.
A page can return HTTP 200 while serving a defacement, a blank body, or a missing disclaimer. Keyword monitoring looks inside the response and asserts on what should — or should not — be there.
Full regex pattern support
Use regular expressions for pattern-based detection: email formats, credit card patterns, script-injection signatures, or version numbers.
Case-sensitive matching
Distinguish brand capitalisation from common words — "Apple" vs "apple" — with optional case-sensitive mode per rule.
Defacement and injection detection
Detect unexpected content added by attackers or rogue deploys: spam links, malicious redirects, or injected script tags.
Instant multi-channel alerts
Route content-change alerts to Slack, Teams, email, SMS, or any webhook with the exact pattern that failed and the URL that served it.
Configurable check cadence
Run keyword checks as frequently as every 30 seconds on critical pages, or less often on lower-priority content to manage usage.
01 · Protect what must stay on the page
Absent text is
Absent text is
a failed check.
Legal disclaimers, cookie banners, copyright notices, and trust badges can be removed by a bad deploy or a CMS change with no server error at all. Negative keyword monitoring treats their disappearance as a failure and alerts you before a compliance audit — or a customer — notices.
- Assert required legal or compliance text is present on every check
- Detect CMS-driven removals before they reach production users
- Combine presence and absence rules on the same monitor
acme.com / privacy HealthyLIVE
RULEmust-contain
LAST RUNPass
CHECKS · 7D2,016
iad-188ms
sfo-1115ms
fra-1143ms
sin-1179ms
02 · Advanced pattern matching
Regex when a plain
Regex when a plain
string isn't enough.
A fixed keyword misses the category of content you're actually worried about. Use a regular expression to detect any email address, any script-injection pattern, or any version string — and get an alert the moment the pattern matches (or stops matching).
- Full PCRE-compatible regex patterns supported
- Alert on match OR on no-match for the same pattern
- Pattern and matched snippet included in every alert payload
add a keyword rule$ curl -X POST https://api.siteqwality.com/http/job \
-H "Authorization: Bearer $SQ_TOKEN" \
-d '{"url":"https://acme.com/checkout","interval_seconds":300,"assertions":[{"body_contains":"Secure Checkout"},{"body_not_matches":"<script[^>]*evil"}]}'
✓ monitor live · keyword rules active
-H "Authorization: Bearer $SQ_TOKEN" \
-d '{"url":"https://acme.com/checkout","interval_seconds":300,"assertions":[{"body_contains":"Secure Checkout"},{"body_not_matches":"<script[^>]*evil"}]}'
✓ monitor live · keyword rules active
30s
fastest keyword check cadence available
2
assertion modes — must-contain and must-not-contain
PCRE
full regex support on every monitor
$0
free tier — start without a credit card
FAQ
Questions, answered.
Presence monitoring (must-contain) alerts you if a keyword or pattern is NOT found on the page — useful for ensuring required text like a disclaimer stays visible. Absence monitoring (must-not-contain) alerts you if the keyword IS found — useful for detecting injected spam, malicious scripts, or prohibited content.
Yes. Patterns are treated as PCRE-compatible regular expressions when you enable regex mode. You can match entire categories of content — email addresses, script tags, URL patterns — rather than a fixed string.
For plain string rules, case-sensitive mode performs a literal case-sensitive comparison. For regex patterns, it maps to removing the PCRE case-insensitive flag, so your expression behaves as written.
Keyword assertions — including regex and absence rules — are included with every HTTP uptime monitor at no additional cost. You add rules when configuring the monitor and they run on every check.
On a 30-second cadence, a confirmed keyword failure typically reaches your chosen alert channel within about a minute, after the failure is re-verified from other regions to eliminate false positives.
More of the platform
Explore the rest of the platform
Ready?
Start watching in under a minute.
Every product starts free — uptime, cron, synthetic, logs, RUM, incidents, and status pages. No credit card required.