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.
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#
Good examples#
| Page | Expected body |
|---|---|
| Marketing home | Start your free trial |
| Pricing | $19/month |
| Status page | All systems operational |
| API health endpoint | "status":"ok" |
| Checkout | Place order |
Tips#
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.
Related Articles
Advanced Monitoring Fields
The four advanced site fields — response-time threshold, HTTP method, custom headers, and expected body — explained with examples.
Money Pages
Prioritise monitoring for your highest-value pages.
Change Detection & Volatility Alerts
Detect sudden performance changes and content modifications.
SLA Dashboard
View SLA compliance across all your sites in one place.