Monitors

A monitor is a scheduled audit. Pick a landing page, pick a cadence (weekly / monthly), and PlumPMM re-audits the URL on that cadence and emails you when scores move beyond a threshold you set.

Monitors are how positioning becomes measurable over time instead of one-shot. A page that audits at 8.4 today can drift to 7.1 over six weeks of marginal copy edits — a monitor catches that before the regression compounds.

How a monitor works

schedule fires → run audit → compare to last run → email if delta ≥ threshold
                                                  → auto-pause if 3 consecutive failures

The scheduler ticks per-org (not real-time) and picks up any monitor whose next_run_at has passed. The audit itself is the same 13-dimension run as a manual audit — same scoring, same LLM cost (1 audit-unit per run).

After the run, PlumPMM diffs the new overall rating against the previous run’s. If the absolute delta is ≥ your threshold, you get an email with the score change, the dimensions that moved most, and a deep link to the run. Otherwise the run is silent — the notify_on_no_change flag exists if you’d rather get a “still 8.4, no signal” email every cadence anyway.

Cadences

Two cadences, each with their own scheduling fields:

Cadence	Time control	Day control
Weekly	Hour of day (in your timezone)	Day of week (0=Sunday … 6=Saturday)
Monthly	Hour of day	Day of month (1–28; 28 caps because not every month has 29+)

The cadences your plan allows are gated separately from how many monitors you can run — see the next section.

Per-tier limits

Plan	Monitors	Cadences allowed
Free	0	—
Solo Founder	20	weekly, monthly
Team	50	weekly, monthly
Business	Unlimited	weekly, monthly

If you downgrade and your active monitor count or cadence falls outside the new plan, the oldest excess monitors are auto-paused with a pause_reason: "plan_downgrade". They stay configured (not deleted) — re-upgrade and they pick back up where they left off.

Alert thresholds

The delta_threshold is a 1–10 integer matching the audit’s rating scale. Set it to 2 to alert on any meaningful score swing; set to 5 to alert only on dramatic regressions. The threshold compares overall ratings — dimension-level swings show up in the email body either way.

Auto-pause

A monitor pauses itself in two cases:

pause_reason: "consecutive_failures" — three audit runs in a row failed (scrape errored, LLM call hiccuped, etc.). PlumPMM won’t keep burning audit-units against a broken page. Fix the URL or remove the monitor; click Resume when ready.
pause_reason: "plan_downgrade" — you downgraded past this monitor’s eligibility. See the per-tier limits above.

A paused monitor doesn’t tick. The Monitor tab on the page workspace shows the pause reason prominently, with a one-click resume.

URL-changed handling

If the landing page’s URL changes between the schedule’s last run and now, the monitor flags url_changed_since_last_run: true so the UI can warn you. The next run audits the new URL and resets the baseline — no false alert about a “score jump” when the alert is really “different page.”

Notification email

By default the alert goes to the email on file for whoever set up the monitor. You can override per-monitor with notify_email — useful when the right person to see a positioning regression isn’t the same person who configured the schedule (e.g., monitor set up by an editor, alerts go to the marketing lead).

Plan availability

Per-plan caps are listed above. Free has no monitors at all.