Why it matters
Marketing sites, docs, and app shells are often the first place customers look. If the page returns an error or times out, trust erodes even when backend APIs are fine.
Website monitoring gives the team an external witness for the pages that represent the product in public.
How it works
The monitor requests a URL such as https://www.example.com using HTTPS. It records status code, timing, and optionally whether a keyword appears in the HTML.
Redirects, TLS problems, and DNS failures all surface as failed checks. Keyword assertions catch soft failures where a page returns 200 with an error message in the body.
Practical example
An agency monitors each customer marketing site every two minutes. A keyword assertion looks for the customer brand name in the HTML. When a deploy ships a broken theme and the keyword disappears, the agency is alerted before the customer calls.
Common misconception
A 200 status always means the site is fine
Error pages, maintenance placeholders, and application failures can still return HTTP 200. Pair status checks with keyword or content assertions when the HTML matters.
How Fajita handles this
Fajita website monitors check availability, status codes, and response time. See website monitoring for setup steps.