Re-check pages on a schedule

A monitor checks the same pages again and again, and lists what changed between two runs.

Docs menu
  1. Run a check first

    A monitor starts from a finished check: its pages, its site and its mode are copied.

  2. Choose a schedule

    Every day for 90 days, every week for a year, or at day 7 and day 30. Every schedule ends. We do not run a monitor for ever.

  3. Open Monitors

    Choose Monitors in the console menu. You see when it ran last and when it runs next, and you can pause, resume or end it.

  4. Check the email setting

    Email on change is on for a monitor you make in the console. Turn it off on the monitor if you would rather look at the list yourself.

  5. Read the changes

    When a page differs from the run before, the change is listed with the page before and after. For example: the page is still live but the link is gone.

What you get

  • A list of changes per monitor, newest first.
  • An email when something changed, if email is on for the monitor.
  • The checks the monitor made, under Checks, like any other check.

Good to know

  • A monitor made in the console emails you when something changes. A monitor made by API does not, unless it is created with notify_email. You get at most one email per monitor per day, and it batches that day's changes. The email says which pages changed and how, and never contains page text. To send the news somewhere else, see "Send events to a no-code tool".
  • Each run uses your balance like any check. If the balance is too low, the monitor pauses and says why.
  • In test mode a monitor runs when you create it and when you run it by hand. It does not follow its schedule.