01
The price silently changes
A pricing bug or bad deploy swaps £249 for £24.90, or drops the number entirely. The page loads perfectly. Your margin does not.
Keyword Monitoring
PulseStack reads the actual page, not just the status code. Tell it the text that must be present, like a price, an "in stock" label or a legal notice, and get alerted the instant it disappears or something it should never see appears.
Included on every paid plan from £15 per month. 14-day trial, checks as fast as every 30 seconds.
Every one of these returns HTTP 200. Every one of them costs revenue or trust while your uptime dashboard stays a calm, reassuring green.
A pricing bug or bad deploy swaps £249 for £24.90, or drops the number entirely. The page loads perfectly. Your margin does not.
The “In stock” label vanishes after a CMS glitch and customers assume the item is gone. No 500, no alert, just quiet abandoned carts.
A client-side app ships a blank container when the API times out. The HTML is 200 and near empty. Keyword monitoring sees the missing content instantly.
A required disclaimer, cookie notice or regulated statement gets edited out. Compliance risk that no status check will ever surface for you.
A stack trace, “Undefined index” or a payment gateway error leaks onto the live page. Watch for text that should never exist and get paged when it does.
Injected content or an altered headline shows up. Monitoring for unexpected strings turns keyword checks into an early tamper-detection tripwire.
A keyword monitor fetches the page from multiple locations, reads the returned content and tests it against your rule. Presence or absence, one string or several. If reality diverges from what you declared, it opens an incident and notifies your channels.
rule:
url: shop.example.com/product/atlas-pro
must_contain:
- "In stock"
- "£249"
must_not_contain:
- "Out of stock"
- "Undefined"
interval: 30s
locations: [ uk, eu, us ]
threshold: 2 consecutive
notify: [ slack, email, pagerduty ]No agent, no code, no tag on your site. Point it at a URL and declare the text.
Paste the page you care about. A product page, a checkout, a compliance notice, a marketing hero.
List the text that must appear and the text that must never appear. Combine several strings if you like.
Choose from eight native destinations and set a consecutive-failure threshold to silence noise.
Checks run from multiple locations on your interval. You only hear from it when content actually breaks.
No add-on maze. The capabilities below come with the monitor on every paid plan.
Content is only half the story. PulseStack watches availability, ports, DNS and expiry from the same account, the same alerts and the same status pages.
Status codes and uptime for any endpoint.
Presence or absence of specific page text.
Reachability of a host at the network layer.
A specific port open and answering.
Endpoint health with custom request headers.
Cron and background jobs that must check in.
Record resolution and unexpected changes.
Registration countdown before it lapses.
HTTP and API monitors support custom request headers for authenticated checks.
Guard prices and “In stock” labels on your best sellers. Catch the pricing bug before customers screenshot it, and the out-of-stock glitch before carts empty.
Prove a deploy actually rendered. Watch for stack traces and error strings leaking to production, and confirm client-side apps hydrate instead of shipping blank shells.
Make sure the disclaimer, cookie notice or regulated statement is still on the page. Get paged the moment a required string is edited out.
A plain uptime check and a human eyeball both miss the failures that matter most. Here is the honest difference.
| Capability | Plain HTTP check | Manual checking | PulseStack keyword |
|---|---|---|---|
| Detects a 500 or downtime | Yes | Eventually | Yes |
| Catches a missing price on a 200 page | No | Only if you look | Yes |
| Spots a blank client-side render | No | Sometimes | Yes |
| Alerts on an error string appearing | No | By luck | Yes |
| Runs every 30 to 60 seconds | Varies | No | Yes |
| Checks from multiple locations | Varies | No | Yes |
| Notifies eight native channels | Varies | No | Yes |
Fires on failure and recovery, after your threshold.
SMS and voice are an add-on, included on Team and Enterprise.
Read the room inside. Start watching the words that pay your bills.
Keyword monitoring continuously scans your web pages to verify that specific words, phrases, or text patterns are present (or absent) in the HTML content. You define the keywords or phrases to watch, choose a check interval (from every 30 seconds to hourly), and our monitors fetch your page from multiple global locations. If a keyword appears or disappears unexpectedly, you receive an instant alert through your configured channels.
PulseStack™ detects a wide range of content issues: missing keywords or phrases that should be present on a page, unexpected text appearing after a hack or defacement, rendering failures where JavaScript frameworks fail to load content, removal of legal disclaimers or compliance text, pricing changes on e-commerce pages, product availability status shifts, and significant drops in word count that indicate broken pages.
Uptime monitoring checks whether your server responds with an HTTP 200 status code. A page can return 200 OK while serving completely wrong content, an empty page from a rendering failure, or a Cloudflare challenge page instead of your actual site. Keyword monitoring goes deeper by verifying that the actual text content on the page matches what you expect. The two work best together for complete coverage.
Yes. You can set up both presence and absence rules. Presence rules alert you when a required keyword disappears (for example, your brand name or a legal disclaimer). Absence rules alert you when an unwanted keyword appears (for example, error messages like 'undefined', competitor names injected by a hack, or debug text like 'lorem ipsum' accidentally pushed to production).
With 30-second check intervals on paid plans (3-minute intervals on the free plan), content changes are typically detected within one check cycle. Our multi-location monitoring means the check runs simultaneously from 7 global locations, so even regional content delivery issues are caught within seconds of occurring. Alerts are dispatched immediately upon detection.
PulseStack™ supports 16+ alert channels including email, SMS, phone calls, Slack, Discord, Microsoft Teams, Telegram, PagerDuty, OpsGenie, webhooks, and more. You can configure different channels for different monitors, set escalation rules, and require consecutive failures before alerting to reduce noise from transient issues.
Absolutely. Keyword monitoring protects your SEO in several ways: it verifies that target keywords remain present on optimised landing pages, detects rendering failures that serve empty content to search engine crawlers, catches accidental noindex tags or removed meta descriptions, and alerts you when CMS updates inadvertently change page content. Many SEO teams use it alongside traditional rank tracking for complete visibility.
E-commerce sites are one of the biggest beneficiaries of keyword monitoring. You can monitor product availability text ('In Stock', 'Out of Stock'), track pricing changes across product pages, verify that promotional banners and discount codes display correctly, ensure payment gateway status messages work, and detect when product descriptions are accidentally removed or corrupted during bulk imports.
There is no hard limit on keywords per monitor. You can define as many keyword rules as needed for each monitored URL. Each keyword can be set as a presence rule (must exist) or absence rule (must not exist), and you can combine multiple rules on the same page. This flexibility lets you create comprehensive content verification for critical pages.
Yes. PulseStack™ fetches pages using a real browser engine that fully executes JavaScript, so single-page applications built with React, Vue, Angular, or Next.js are monitored accurately. This is critical because many content failures are caused by JavaScript rendering issues that only appear in the final rendered output, not in the raw HTML source.
Keyword monitoring is included on every paid plan from £15 per month, with a 14-day trial and checks as fast as every 30 seconds. Set your first rule today.