Monitoring

    Expected Body Content

    Assert a substring exists in the response body. 500-char cap. Use for "page renders" checks; for richer rules use Money Page Monitor.

    Part of API endpoint monitoring — the full answer, the facts and the alternatives in one place.

    Updated 2026-06-15
    2 min read
    body
    content check
    assertion

    Expected Body Content#

    A simple way to confirm the page actually rendered instead of just returning 200 OK with an empty shell or an error template.

    How it works#

  1. Enter up to 500 characters of plain text
  2. On every check, LemWatch downloads the response body and looks for the substring
  3. If the substring is missing, we fire a "content missing" alert with the actual snippet we did receive
  4. Good examples#

    PageExpected body
    Marketing homeStart your free trial
    Pricing$19/month
    Status pageAll systems operational
    API health endpoint"status":"ok"
    CheckoutPlace order

    Tips#

  5. Pick a string that only appears on the healthy page — avoid common words like "the" or "home"
  6. Case-sensitive — match the actual rendered casing
  7. For HTML pages, prefer visible copy over class names (class names change with redeploys)
  8. When to use Money Page Monitor instead#

    For richer assertions — regex, multiple required strings, forbidden strings, JSON path checks — use the Money Page Monitor custom rules engine. Expected body is the quick single-string version.

    Persistence note#

    This field used to silently revert because it was missing from the form schema. Latest build saves it correctly and shows it on edit — see Advanced Monitoring Fields.

    Was this article helpful?