Monitoring re-audits your tracked URLs on a schedule and emails you when something meaningfully changes — a grade drop, a bot block, or content disappearing. You only get notified when something actually differs from the previous run.
How to set up monitoring
- Open a project and go to Monitoring in the project navigation.
- Set a schedule frequency: Daily or Weekly. For weekly, choose the day and UTC time.
- Choose which types of changes should trigger alerts.
- Enable email notifications and choose what to be notified about.
- Save. Monitoring will run on its next scheduled tick.
Your tracked URLs are monitored automatically — any URL added to a project’s tracked list is included in monitoring runs.
Schedule options
Daily — runs once per day at the time you choose (in UTC).
Weekly — runs once per week on the day and time you choose.
None — monitoring is saved but disabled. No runs will execute until you set a schedule.
You can pause monitoring at any time without losing your settings. A paused project skips scheduled runs until you re-enable it.
Change types
You can choose which categories of change trigger alerts. Each category covers a distinct layer of the audit:
Content — page content and rendered copy changes. Fires when what a bot can read on the page changes between runs.
Crawlability — robots.txt, noindex, HTTP status, and AI bot access changes. Fires when a bot’s access status changes, including new blocks or mismatch findings.
Speed & stability — TTFB, CLS, and INP grade changes. Fires when a performance grade shifts (up or down).
Authority — authority grade, critical gate, and failed check changes. Fires when structured data or entity signals change in a way that affects the authority score.
You can enable any combination. If none are checked, monitoring will run but will not send alerts.
Email notifications
Two notification types are available:
Changed pages detected — sends a summary when one or more tracked URLs show changes matching your selected change types.
Run failures / blocked pages — sends an alert when a URL could not be audited at all, usually because the page returned an error or was unreachable during the run.
You can enable either or both independently.
Reviewing monitoring results
Each completed monitoring run appears in the project’s monitoring history. You can open any run to see a per-URL summary of what changed.
For any URL with changes, open the report and use Compare Mode to see exactly what shifted between the current run and the previous baseline. Change badges appear throughout the report tabs next to anything that differs.
Pausing and resuming
You can pause monitoring at any time from the Monitoring settings. Pausing saves your schedule and alert configuration — runs are just skipped until you resume.
If a URL is removed from your tracked list, it stops appearing in future monitoring runs automatically.
Common questions
Why didn’t I get an alert even though something changed?
Check your change type selections. If the category that changed is not enabled, no alert is sent. Also check your notification preferences and spam folder — alert emails come from no-reply@beseenby.ai.
Can I monitor URLs not in a project? No. Monitoring only runs on URLs that are tracked in a project. To monitor a URL, add it to a project’s tracked list first.
How long does a monitoring run take? Each URL in the run takes approximately 30 seconds to audit. A project with 10 tracked URLs takes roughly 5 minutes per run.