# Uptime & Liveness Monitoring

**Two ways a page fails. Most tools only watch one.**

Uptime monitoring catches the obvious failure: the page is down. Liveness monitoring catches the invisible one: the page returns 200, looks perfect, and the structured data you are paying for stopped appearing on it three weeks ago. MetaPilot watches both.

---

## The Problem

Schema breaks silently. A cache purge, a CDN change, a theme update, a route someone disabled, a URL that moved — and your JSON-LD is simply gone.

Nothing errors. Nothing 500s. Your monitoring is green, your rich results quietly stop, and you find out when someone asks why traffic dropped. There is no error page for **"the thing you paid for is not on the page anymore"**, which is exactly why nobody catches it.

---

## How It Works

1. **Nothing to set up** — No watchlist to build and nothing to switch on. MetaPilot checks your homepage from the moment it has your sitemap, on every plan including Free. Structured-data liveness follows your auto-pilot flag: switch auto-pilot on for a page and the Monitoring badge lights up.

2. **MetaPilotBot polls on your plan's cadence** — Availability is checked as often as every 5 minutes on paid plans. Liveness runs hourly at the top end, because markup disappears far less often than a server does.

3. **You get one alert per event** — Not one per failing check. One when it breaks, one when it recovers, addressed to whichever members opted in. Everything in between updates the open incident silently.

---

## What You Get

- **Uptime monitoring: did the page answer?** MetaPilotBot fetches your homepage, records status code and response time. Appends `?metapilot-uptime=` to bypass cache and reach your origin.
- **Every page on auto-pilot is watched, on every plan** — No cap on pages covered. Auto-pilot is the switch.
- **Liveness monitoring: did it answer with your metadata on it?** Re-fetches the page and confirms your markup is genuinely in it — not just that it was generated, but that it is *there*.
- **We know what should be on the page** — Because we put it there. A generic monitor can only tell you the page loaded; only MetaPilot knows which schema types were supposed to be present.
- **Alerts that do not cry wolf** — 3 consecutive failing uptime checks before an incident opens; 2 consecutive liveness checks before markup is called gone.
- **Alerts that do not double up** — If a page is unreachable you get the uptime alert, not a second email about missing schema on an unreachable page.
- **A real uptime percentage, not a green dot** — Every sample kept for your plan's retention window (7 days on Free, up to 365 on Business).
- **A deleted page is named as one** — A managed page returning 404 reads as **Page gone (404)** on its own row, not as a generic failure.
- **No false alarms on new pages** — A page whose markup has never been confirmed live is treated as propagating, not broken.
- **Everything injected is covered** — FAQ sections, How-To sections, and the Ask AI widget are checked the same way, with no separate opt-in.

---

## Plan Availability

| Plan | Uptime check cadence | Liveness check cadence | Sample retention |
|---|---|---|---|
| Free | Every 30 minutes | Daily | 7 days |
| Starter | Every 5 minutes | Every 6 hours | — |
| Growth | Every 5 minutes | Every 3 hours | — |
| Business | Every 5 minutes | Hourly | 365 days |

- **Uptime**: homepage, on every plan including Free. No watchlist required.
- **Structured-data liveness**: unlimited pages on every plan. Every page on auto-pilot is watched.

---

## Frequently Asked

**What is the difference between uptime and liveness?**
Uptime asks "did the page answer?" Liveness asks "did the page answer *with our metadata on it*?" A page can pass the first and fail the second for weeks.

**Why only the homepage for uptime?**
Uptime answers: is the site up at all? Every other page you care about is covered by liveness monitoring when you put it on auto-pilot.

**Do I have to pick pages to monitor?**
No. Uptime is your homepage automatically. Liveness follows whichever pages are on auto-pilot, with no limit on how many.

**Will a flaky minute wake me up?**
No. It takes 3 consecutive failing checks to open an uptime incident. A deploy blip or single 502 never fires an alert.

**Who gets the alerts?**
Members of your organization who have opted in, per alert type. Opted in by default — a teammate who never opened settings still hears about an outage.

**What if my CDN or firewall blocks your bot?**
Checks fail for the wrong reason. MetaPilotBot identifies itself honestly and publishes its details on the bot page so you can allowlist it in a minute.

**Where is the "monitor this page" button?**
There isn't one. Turn auto-pilot on for a page and liveness monitoring comes with it automatically.

**Does liveness monitoring need the Cloudflare Worker?**
No. Both checks are outside-in fetches of your URL, compatible with any publishing channel.

---

## Know Before Your Customers Do

There is nothing to arm. Connect your sitemap, turn auto-pilot on where it matters, and hear about it the first time either kind of failure happens.

[Start free](#) · [Run a free audit](#)