# Keyword Monitoring: Get Alerts When a Trigger Word Appears or Disappears on Any Page Source: PageCrawl.io Blog URL: https://pagecrawl.io/blog/keyword-monitoring-website-trigger-word-alerts --- A product page says "Out of Stock" today. The moment that string changes to "Add to Cart", you want to know, not an hour later when you happen to refresh. A supplier's recall page does not currently contain the word "recall" for your SKU. The day it does, your team needs a notification before a customer calls. A regulator's guidance page does not mention your category yet. When it does, your compliance lead wants the alert in their inbox. These are all the same problem with different stakes: you care about a single word or phrase, and you care about the exact moment it appears or disappears. Watching a whole page for "any change" buries that signal under noise from rotating banners, timestamps, view counts, and ad slots. You get fifty alerts a week and stop reading them, then miss the one that mattered. This guide covers keyword monitoring, sometimes called trigger-word monitoring: how to detect when a specific word or phrase shows up or vanishes on a page, the conditions that turn that into a clean alert, and a step-by-step PageCrawl setup that works on ecommerce, compliance, and PR use cases. ### What Keyword Monitoring Actually Means Keyword monitoring is narrower than full-page change detection. Instead of asking "did anything on this page change?", you ask one of two questions: - **Appearance**: did the word or phrase show up on the page when it was not there before? ("recall", "discontinued", "now hiring", your competitor's name, a new price point.) - **Disappearance**: did the word or phrase go away? ("Out of Stock" vanishing means the item is back, "Coming Soon" vanishing means it shipped.) Both reduce to the same mechanism: you track a piece of text, and you fire an alert based on a condition (contains, does not contain, changed from X to Y). The skill is in scoping what text you watch and writing the condition so it only triggers on the event you care about. ### Where Trigger-Word Alerts Earn Their Keep #### Ecommerce and restock The classic case. A button label, a stock badge, or an availability line carries the whole signal. "Sold Out" disappearing or "In Stock" appearing is the buy trigger. This is the foundation of every [out of stock monitoring](/blog/out-of-stock-monitoring-alerts-guide) workflow and powers restock alerts for everything from [sneakers](/blog/sneaker-restock-alerts-nike-adidas) to [LEGO sets](/blog/lego-restock-alerts-in-stock-notifications) to [baby formula](/blog/baby-formula-stock-tracker-alerts). It also drives competitor watching: a [competitor's pricing page](/blog/competitor-price-monitoring-ecommerce-guide) gaining the word "Free shipping" or a new tier name is a strategy change you want to catch early. #### Compliance and regulatory Regulators and standards bodies publish in prose, and the words matter. A guidance page that newly contains your product category, an [FDA recall list](/blog/fda-maude-medical-device-recall-alerts) that gains your manufacturer name, or a [privacy law tracker](/blog/gdpr-ccpa-privacy-law-change-tracking) that introduces "data transfer" near your jurisdiction. Trigger-word monitoring turns a 40-page document into a single boolean: does it now mention the thing I am responsible for? Teams use this across [regulatory compliance monitoring](/blog/regulatory-compliance-monitoring), [SEC filing alerts](/blog/sec-filings-monitoring-edgar-alerts), and [product recall tracking](/blog/product-recall-monitoring-consumer-safety). #### PR, brand, and reputation A press page, a review section, or a forum thread gaining your brand name, an executive's name, or a charged word ("lawsuit", "breach", "boycott") is a PR signal. The earlier you see it, the more options you have. This overlaps with [online reputation monitoring](/blog/online-reputation-monitoring) and [brand mention alerts](/blog/hacker-news-product-hunt-brand-mention-alerts), but keyword monitoring is the precise version: you name the words and you get told the instant they land. ### Two Ways to Watch for a Keyword There are two technical approaches, and picking the right one keeps your alerts clean. #### Method 1: Watch the whole page text, alert on a keyword condition You track the full page as text and apply a condition like "send an alert only when the page contains 'recall'." The monitor still checks the entire page, but the notification rule filters down to your keyword. This is the right choice when the word could appear anywhere on the page and you do not know in advance which element will hold it. Compliance documents and news pages fit here. **Best for**: long documents, pages where the keyword's location is unpredictable, "does this page mention X at all" questions. #### Method 2: Track a specific element, alert when its text changes You point a selector at the exact element that holds the value (a stock badge, a price span, a status line) and you watch only that. This produces the cleanest possible signal because nothing else on the page can trigger it. It depends on writing a good selector, which is its own small skill covered in the [CSS selector guide](/blog/css-selector-guide-target-elements-monitoring) and the [XPath and CSS reference](/blog/xpath-css-selectors-web-monitoring). XPath is especially handy here because it can select by text content directly, for example `//button[contains(text(), "Add to Cart")]`. **Best for**: stock status, prices, version numbers, any value that lives in one known, stable element. Here is how the two compare in practice. | Factor | Whole-page text + condition | Specific element + change | |--------|------------------------------|----------------------------| | Setup effort | Low (no selector needed) | Medium (write a selector) | | False alerts | Higher (page noise) | Lowest | | Catches keyword anywhere | Yes | No, only in the element | | Best for | Compliance docs, news, forums | Stock, price, status, version | | Handles unpredictable location | Yes | No | A practical rule: if you can point at one element that always holds the word, use Method 2. If the word could land anywhere in a block of prose, use Method 1. ### Setting Up Keyword Monitoring in PageCrawl PageCrawl handles both methods. New monitors come with screenshots enabled and sensible default actions (cookie banner and overlay removal) already on, so the page you capture matches what a real visitor sees. Here is the full walkthrough. #### Step 1: Create the monitor and choose what to track Add the page URL. For Method 1, leave the tracking mode on full-page text, which captures the readable text of the page. For Method 2, choose element tracking and use the visual selector to click the exact element (the stock badge, the price, the status line). PageCrawl generates the selector for you, or you can paste one in. For prices specifically, switch to price tracking mode. It extracts the numeric value so you can write conditions like "alert when the number drops below 50" instead of matching raw text. This is the same mode behind every [price drop tracker](/blog/amazon-price-tracker-drop-alerts) workflow. #### Step 2: Add a keyword condition This is where keyword monitoring becomes precise. In the monitor's alert rules, add a condition based on the text: - **Alert when the page (or element) contains a word.** Use this for appearance triggers: notify when the page gains "recall", "lawsuit", or a competitor name. - **Alert when it no longer contains a word.** Use this for disappearance triggers: notify when "Out of Stock" or "Sold Out" leaves the page, which means the item is back. - **Alert only when the value changes to a specific string.** Use this when a status field flips between known states, for example from "Pending" to "Approved". You can stack conditions. A common compliance setup is "alert when the page contains 'recall' AND contains our brand name", so a recall page that mentions other manufacturers stays quiet. #### Step 3: Tune the check frequency to the stakes Match the interval to how fast you need to react. A high-demand restock might justify the most frequent checks your plan allows. A regulatory page that updates monthly is fine on a slower cadence. Checking more often than the page changes only adds noise and burns through your monthly check budget. #### Step 4: Route the alert to the right channel Send the notification where the responsible person will actually see it. PageCrawl supports email, [Slack](/blog/website-change-alerts-slack), Discord, Teams, Telegram, and [webhooks](/blog/webhook-automation-website-changes). For automation, route the webhook into [n8n](/blog/n8n-website-monitoring-automate-change-detection) or [Zapier](/blog/zapier-website-monitoring) to open a ticket, post to a channel, or kick off a downstream workflow. Compliance teams often send the alert to a shared inbox plus a logged channel so there is a record of when the keyword first appeared. #### Step 5: Verify with the screenshot and change history When an alert fires, open the change in PageCrawl. The screenshot shows exactly what the page looked like at the moment the keyword appeared or vanished, and the diff highlights the changed text. This matters most for compliance and PR, where you may need to prove what a page said and when. The change history keeps every prior state, so you have a timeline rather than a single snapshot. ### Writing Conditions That Do Not Cry Wolf The difference between a useful keyword monitor and an ignored one is the condition. A few patterns that keep alerts clean. #### Anchor the keyword to context "Available" appears on most ecommerce pages somewhere (in footers, in shipping copy). If you want "the product is available", track the specific availability element with Method 2, or require a more specific phrase like "In Stock" or "Add to Cart". The more unique the string, the fewer false positives. #### Use "does not contain" for restock Counterintuitively, the cleanest restock trigger is often the disappearance of a negative word, not the appearance of a positive one. "Out of Stock" leaving the page is unambiguous. "Add to Cart" appearing can fire on pages that show the button even when greyed out. Test both on the real page before committing. #### Combine keywords for compliance precision On a multi-item recall or guidance page, require two conditions: the trigger word and your identifier (brand, SKU, manufacturer). This is the same logic that makes [FDA drug shortage list](/blog/fda-drug-shortage-list-monitoring) and [SEC EDGAR](/blog/sec-filings-monitoring-edgar-alerts) monitors readable instead of overwhelming. #### Watch out for dynamic and hidden text Some pages carry text in hidden elements (structured data, A/B test variants) that a user never sees but a raw text match would catch. PageCrawl renders the page in a real browser before extracting text, and the default overlay and cookie actions strip common noise, but if a keyword monitor fires on something invisible, narrow to a specific visible element with a selector instead of the whole page. #### Mind upper and lower case and word boundaries "recall" matching inside "recalling" or "recalls" can be useful or noisy depending on your goal. If you only want the exact word, prefer element-level tracking where you control the surrounding text, or test that your condition behaves the way you expect on a sample of real page states before you rely on it. ### A Few Worked Examples #### Catch a recall for your product Track the manufacturer's recall page as full-page text (Method 1). Add two conditions: contains "recall" AND contains your model number. Set checks to a frequency that matches how often the page updates, and route the alert to your safety and support leads. When both conditions hit, you get the notification plus a screenshot proving the page state. #### Know the second a competitor changes a plan name Track the competitor's [SaaS pricing page](/blog/saas-pricing-page-monitoring-competitor-changes) as full-page text. Add a condition for the appearance of any new tier word you expect ("Enterprise", "Teams", "Pro"), or just watch the page and read the highlighted diff when it changes. Pair it with [competitor website tracking](/blog/how-to-track-competitor-websites-guide) for the full picture. #### Get the restock alert before it sells out again Track the product's stock element with a selector (Method 2). Alert when the element no longer contains "Sold Out". Send it to a channel you watch in real time. This is the exact pattern behind dedicated [in-stock alert](/blog/amazon-in-stock-alerts) workflows, just generalized to any site. ### Choosing your PageCrawl plan PageCrawl's **Free plan** lets you monitor **6 pages** with **220 checks per month**, which is enough to validate the approach on your most critical pages. Most teams graduate to a paid plan once they see the value. | Plan | Price | Pages | Checks / month | Frequency | |------|-------|-------|----------------|-----------| | Free | $0 | 6 | 220 | every 60 min | | Standard | $8/mo or $80/yr | 100 | 15,000 | every 15 min | | Enterprise | $30/mo or $300/yr | 500 | 100,000 | every 5 min | | Ultimate | $99/mo or $999/yr | 1,000 | 100,000 | every 2 min | Annual billing saves two months across every paid tier. Enterprise and Ultimate scale up to 100x if you need thousands of pages or multi-team access. At an engineering hourly rate, Standard at $80/year pays for itself the first time you catch a breaking API change, a deprecated endpoint, or a silent config change before it takes down production. 100 monitored pages is enough to cover the changelogs and docs of every third-party API your stack depends on. Enterprise at $300/year adds higher check frequency, 500 pages, and full API access. All plans include the **PageCrawl MCP Server**, which plugs directly into Claude, Cursor, and other MCP-compatible tools. Developers can ask "what changed in the Stripe API docs this month?" and get a summary pulled from your own monitoring history. AI assistants can create monitors through conversation on every plan, including Free, and paid plans add on-demand checks and monitor management, turning your tracked pages into a living knowledge base instead of a pile of alert emails. ### Getting Started Pick the one keyword that would actually change your day if it appeared or disappeared. For a buyer that might be "Sold Out". For a compliance lead it might be "recall" next to a SKU. For a PR team it might be the brand name on a press page. Set up a single monitor on the page that carries that word. If the word lives in one known element, point a selector at it; if it could appear anywhere in a block of text, watch the full page and add a "contains" condition. Run it for a week, check whether the alerts you get are the ones you wanted, and tighten the condition if anything fires that should not. Once the first monitor is dialed in, the pattern scales to dozens of pages without scaling the noise. The free tier covers 6 pages and 220 checks a month, which is enough to prove the approach on your most important keywords before you expand. From there, the same setup extends to [API monitoring](/blog/api-monitoring-track-changes-alerts), competitor tracking, and full compliance coverage without changing how you work. --- Need more? The complete PageCrawl.io help center, with every article, is available as a single document at https://pagecrawl.io/llms-full.txt. Read it for context on anything this page does not cover.