What Monitor does

Monitor watches the pages you have already published. The content workspace is about getting a page live; Monitor is about noticing when a live page stops being what you intended.

What it does

It crawls your site on a schedule and, for every page, records what it found: the status code, the rendered HTML, the metadata, the links, the structured data, and how the page conforms to the checks a search engine and a crawler actually apply.

Then it compares each crawl against the last, so the question it answers is not “what does this page look like” but “what changed, and does it matter”.

What it catches

The failures that are invisible from inside your CMS:

A page that started returning a 404 or a redirect after a slug change.
A noindex left on after a staging deploy.
A canonical pointing at the wrong URL.
A title or description rewritten by a plugin update.
Internal links that broke when a page moved.
A page that renders for a browser and is empty to a crawler.

None of these show up in wp-admin. All of them show up in your traffic, weeks later.

How it differs from uptime monitoring

Uptime monitoring asks whether the server answered. Monitor asks whether the answer was right. A site can be up, fast, and quietly returning noindex on its highest-value page.

How it is billed

Per page under watch, not per seat — the cost is driven by how many pages are crawled and how often, which has nothing to do with how many people are in your workspace. It is arranged directly rather than bought self-serve, and it does not change your per-seat bill. See plans and pricing.

Getting started

Adding a site to Monitor covers putting a site under watch and reading the first crawl. The first result is a baseline — the value starts with the second one, because that is the first comparison.