A 200 is not a working site
Why a 200 is not a working site
HTTP 200 means the server returned a response. It does not mean the client site did the job your agency was hired to protect. That gap is where agencies lose accounts.
The status code stops too early
An uptime check is useful. It tells you the URL answered. The client’s question is different: did the lead arrive, did the sale complete, did the certificate stay valid, did the page still look like the one they approved? Any of those can fail while the homepage returns 200.
MetricPoints keeps the uptime check and adds the paths an agency gets called about. Form checks, configured journeys, TLS and DNS, visual changes, and optional WordPress, browser, and server evidence all sit in the same portfolio.
- A form can show a success message and never hand the lead off.
- Checkout can load while payment scripts fail.
- A certificate, DNS change, or shared-server failure can sit behind a page that still answers.
Use an uptime tool for the ping. Use this for the account.
UptimeRobot, Pingdom, and Better Stack already own the generic “website monitoring” query, and they should: a fast ping and a status page are their job. MetricPoints is for the agency that has to explain a broken client site before the client discovers it.