Monitoring / Keyword

Confirms the real page is there, not just a 200

Set a phrase that should always appear on your page — a tagline, a price, a product name — and every check confirms it's still there, not just that the server responded.

Screenshot placeholder Expected Content Field Set once per site

Built to work even on JavaScript-heavy pages

The page's visible text is checked for your phrase first. If that fails — common on pages that render content client-side — the page's title and meta description are checked as a fallback, since those are usually present in the raw HTML before anything renders.

  • Exact phrase match, or a fuzzy match if most of the significant words are present
  • Waits for a second consecutive miss before flagging it — a render hiccup doesn't false-alarm
  • Catches hijacked or silently replaced content a status-code check alone would miss

The details

  • One phrase per site — set it once, checked on every cycle
  • Whitespace and hidden characters are normalized before comparing
  • A first miss is recorded silently; a second consecutive miss raises a warning

Questions people ask

Something specific and stable — a tagline, product name, or address — not something that's likely to change with routine content edits.

If a redesign removes the phrase, you'll get one silent flag on the first check and a real alert on the second — update the keyword once you've confirmed the redesign was intentional.

Yes, via a fallback check against the page's title and meta description, which are usually present even before JS runs.

Try it on a real phrase.

Bring a URL and a phrase from the page — we'll show you exactly how the check reads it.

Book a Demo