same, changed, new, removed, or error. It’s the right choice for pricing pages, changelogs, docs pages, job posts, status pages, or any known URL where a small change matters.
This page covers the scrape target. Scheduling, goals and judging, change tracking, notifications, and pricing are shared across all monitor types. See the Monitoring overview.
Create a page monitor
Create a monitor with ascrape target that lists one or more explicit URLs:
CLI
Scrape target
Ascrape target requires type and a urls array with at least one URL. Scrape options are passed through to the underlying scrape jobs. Monitor-triggered scrapes default maxAge to 0, so each check performs a fresh scrape unless you explicitly set a different maxAge.
Scrape target
Detecting field-level changes
By default a page monitor diffs the page’s markdown. To alert only when a specific field changes, such as a price, a headline, an in-stock flag, or the items in a list, add achangeTracking format to the target’s scrapeOptions. See Change tracking for JSON mode and mixed mode.
Shared configuration
- Schedules: cron or natural-language cadence, minimum 5 minutes.
- Goals and judging: alert only on meaningful changes.
- Notifications: webhook and email delivery.
- Check results: inspect each check and its per-page diffs.
- Pricing: 1 credit per URL per check, plus optional judging.

