01
The price silently changes
A pricing bug or bad deploy swaps GBP 249 for GBP 24.90, or drops the number entirely. The page loads perfectly. Your margin does not.
Keyword Monitoring
PulseStack reads the HTML of the 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 GBP 9 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 GBP 249 for GBP 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 server-rendered page falls back to a blank container when its data call times out. The HTML is 200 and near empty. Keyword monitoring sees the missing content in the raw HTML.
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 HTML (no JavaScript is run) 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"
- "GBP 249"
must_not_contain:
- "Out of stock"
- "Undefined"
interval: 30s
locations: [ london, new-york, sydney ]
down_when: 2 of 3 locations fail
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. Re-tests and two-location confirmation silence the 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.
A TCP connection to a host and port.
A specific port open and answering.
Endpoint health with custom request headers.
Cron and background jobs that must check in.
Certificates close to expiry or invalid.
A record still holds the value you expect.
Domains close to their renewal date.
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 server-rendered pages still carry their content 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 server-rendered page | 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, once two locations agree.
SMS alerts are included on Team and Enterprise.
Read the room inside. Start watching the words that pay your bills.
Keyword monitoring checks your web pages to verify that a specific word or phrase is present (or absent) in the HTML content. You set the keyword for each monitor, choose a check interval (from every 30 seconds on Pro and above to once a day), and our monitors fetch your page from London, New York and Sydney. If the keyword disappears, or an unwanted one appears, you receive an alert through your configured channels.
A keyword monitor catches any issue that makes your chosen word or phrase disappear or appear: missing text that should be present on a page, unexpected text appearing after a hack or defacement, server-rendered pages that come back empty or broken, removal of legal disclaimers or compliance text, a changed price on an e-commerce page, and product availability status shifts.
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 60-second checks on Starter and 30-second checks on Pro, Team and Enterprise, a missing or unexpected keyword is typically detected within one check cycle. The check runs from 3 locations (London, New York and Sydney), a failed check is re-tested a few seconds later, and the monitor is marked down when at least two locations fail, so a one-off blip in a single region does not trigger an alert. Alerts are sent as soon as the failure is confirmed.
PulseStack™ supports 8 native alert channels: email, SMS, Slack, Discord, Microsoft Teams, Telegram, PagerDuty and webhooks, with Zapier and Google Chat connecting through webhooks. You can configure different channels for different monitors, and failed checks are re-tested and confirmed from at least two locations before an alert is sent, which reduces 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.
Each keyword monitor watches one word or phrase, set as a presence rule (must exist) or an absence rule (must not exist). To watch several phrases on the same page, add a keyword monitor for each one. Each counts towards your plan's monitor allowance.
Keyword checks fetch the page's HTML in the same way a search engine crawler does, without running JavaScript. Server-rendered pages work as they are. If your site builds its content in the browser (a single-page app), point the keyword check at a server-rendered page, or at an API endpoint that returns the text you want to watch.
Keyword monitoring is included on every paid plan from GBP 9 per month, with a 14-day trial and checks as fast as every 30 seconds. Set your first rule today.