How to Setup Keyword Monitoring

Keyword monitoring checks whether specific text appears or disappears on any webpage and alerts you immediately when content changes. Set up keyword monitoring in MonitoringDaddy to catch defaced pages, broken deployments, missing offers, and blocked content that still returns HTTP 200 — all before your users notice.

What Is Keyword Monitoring?

Keyword monitoring (also called a response-contains check) works by fetching a URL on a scheduled interval, scanning the full HTML response body, and verifying whether a specific string is present or absent. The moment the result changes — the text disappears when it should be there, or appears when it should not — an alert fires to your chosen channel.

Unlike an HTTP status check, keyword monitoring looks inside the page. A server can return 200 OK while serving a maintenance splash, a blank screen, or a defaced homepage. A keyword check catches all of those scenarios because it verifies actual content, not just the response code.

Why Keyword Monitoring Matters

Teams that rely on website uptime monitoring alone can miss a whole class of silent failures. A server can return HTTP 200 while serving a broken, empty, or defaced page — and no status-code check will catch that. Common situations where only a keyword check alerts you:

• Website defacement — An attacker replaces your homepage content while HTTP status stays 200.
• Broken deployments — A bad push empties a template partial; the page loads but key content is gone.
• CMS accidents — An editor accidentally unpublishes a block or clears a pricing field.
• CDN serving stale content — Your origin updates but the CDN continues to serve an old version without the latest terms or announcement.
• Geo-blocking or bot-blocking — Your site returns a CAPTCHA page behind a 200 status code.
• Unauthorized SEO or pricing changes — Target keywords, plan names, or promotional text change without authorization.

How Keyword Monitoring Works

At each interval tick, MonitoringDaddy sends an HTTP GET request to your target URL from an external monitoring node. The full response body is received and scanned for your configured string. If you use the URL does NOT contain keyword trigger, an alert fires when the string is absent. If you use URL contains keyword, an alert fires when the string appears — ideal for detecting error messages or injected spam. A recovery notification is sent automatically once the condition resolves.

Before You Begin

• Use View Source (Ctrl+U) to confirm your keyword appears in the raw HTML, not only in a JavaScript-rendered layer.
• Choose a stable, unique phrase — a permanent heading or product name works better than a single common word.
• Decide the alert mode: "must be present" (alert on missing) or "must be absent" (alert on appearing).
• Have at least one alert channel ready — an email address or a Slack / Discord webhook URL.

Step-by-Step Keyword Monitoring Setup

Step 1: Monitor Name

Give the monitor a clear, descriptive name — include the page and what you are watching, for example Pricing Page – "Get Started" CTA.

Step 2: URL

Enter the full, absolute URL of the page to monitor, including the protocol.

Step 3: Monitoring Interval

Choose how frequently the page should be checked:

• 5 minutes — recommended for critical pages such as homepages or checkout flows
• 15 minutes — suitable for blog posts and lower-priority pages
• 1 minute — maximum sensitivity for high-value pages

Step 4: SSL Certificate Monitoring

Set SSL certificate monitoring to OFF. This monitor checks page content, not certificate validity.

Step 5: Domain Name Monitoring

Set domain name monitoring to OFF. Domain expiry tracking is a separate concern unrelated to keyword checks.

Step 6: Alert Condition

From the alert condition dropdown, select:

This instructs the engine to scan the response body for your keyword, rather than checking only the HTTP status code.

Step 7: Text Lookup — Enter Your Keyword

Type the exact string you want the monitor to search for inside the page response.

• Use a phrase of 3–8 words rather than a single common word to avoid false matches.
• Copy the string directly from the page source to ensure exact character matching.
• Avoid strings that change regularly, such as dates, dynamic counters, or session tokens.
• Be aware of case sensitivity — copy the keyword exactly as it appears in the HTML source.

Step 8: Contains or Does Not Contain

• URL contains keyword — Alert fires when the keyword APPEARS. Use to detect unwanted strings: error messages, maintenance banners, CAPTCHA walls, or injected spam.
• URL does NOT contain keyword — Alert fires when the keyword IS MISSING. Use to detect removed CTAs, missing product descriptions, or broken template partials.

Step 9: Alert Channels

Add at least one notification channel:

• Email alerts — recommended as a baseline
• Webhook alerts — Slack, Discord, Microsoft Teams, PagerDuty, or any custom endpoint

Step 10: Request Method

Set the HTTP method to GET. Only change this if you are monitoring a REST API endpoint that requires a different method.

Step 11: Headers and Authentication

Leave headers and authentication EMPTY for public pages. If the page requires a login, add a Bearer token or session cookie here.

Step 12: Cache Buster

Set the cache buster to ENABLED. This appends a unique query parameter to each request, preventing CDNs and reverse proxies from serving stale responses that could mask real content changes on the origin server.

Recommended Keyword Monitoring Configuration

Best Practices for Keyword Monitoring

Choose Stable, Unique Text

The best keyword anchor is a short phrase specific to the page's core purpose that is unlikely to change in normal operation — a tagline, a section heading, or a product name. Avoid dynamic content like timestamps, counters, or personalized greetings.

Monitor for Negative Keywords (Should-NOT-Contain)

Add a second monitor using the URL contains keyword trigger to detect strings that should never appear on a live page:

• 403 Forbidden / Access Denied
• Under Maintenance
• Hacked By
• Error establishing a database connection

These "should-NOT-contain" monitors act as a second defence layer against errors that return HTTP 200 with an error body.

Stack Multiple Monitors per Critical Page

Set up two or three keyword monitors on your most important pages — the hero heading, a key benefit, and the footer CTA — so a partial template failure that removes only one section is still caught.

Troubleshooting Keyword Monitors

Alert fires but the keyword appears in the browser

The most common cause is JavaScript rendering. MonitoringDaddy fetches raw HTML; content injected by JavaScript after page load is invisible to the monitor. Use View Source (Ctrl+U) to confirm the keyword is in the static markup, and switch to a server-rendered string if it is not.

Intermittent or false-positive alerts

The keyword may be inside an A/B test variant that is sometimes absent. Switch to a stable, always-rendered string. For should-NOT-contain monitors, verify the negative keyword does not appear in HTML comments or script blocks during normal operation.

Monitor stays in error state after you fix the page

Wait for the next check interval — recovery is sent automatically once the keyword is detected. You can also trigger an immediate recheck from the MonitoringDaddy dashboard.

Next Steps

Now that your keyword monitor is live, consider building a complete monitoring stack for your most critical pages. Start with website uptime monitoring to catch server-level failures, add keyword monitoring to verify content integrity, and use REST API monitoring if your site depends on backend services. You can run as many monitors as your plan allows — see the pricing page for details on check frequency and monitor limits.

Frequently Asked Questions