Website Monitor

Lightweight website monitoring — detect changes, downtime, or content patterns without external services.

Usage

Check if a site is up

python3 {baseDir}/scripts/monitor.py check https://example.com

Monitor for changes (compare to last snapshot)

python3 {baseDir}/scripts/monitor.py watch https://example.com --state-dir /tmp/monitor-state

Returns exit code 0 if unchanged, 1 if changed (with diff), 2 if down.

Check for specific content

python3 {baseDir}/scripts/monitor.py match https://example.com/pricing --pattern "Enterprise plan"

Returns exit code 0 if pattern found, 1 if not found.

Batch monitor from file

# sites.txt: one URL per line
python3 {baseDir}/scripts/monitor.py batch sites.txt --state-dir /tmp/monitor-state

Integration with OpenClaw

Heartbeat check

Add to your HEARTBEAT.md:

Run website monitor batch check on sites.txt.
If any site is down or changed, notify me.

Cron job

# Check every 30 minutes
openclaw cron add --every 30m --task "Run website monitor on my sites list and alert me if anything changed"

Features

• 🔍 Change detection with text diff
• ⬆️ Uptime checking (HTTP status + response time)
• 🎯 Pattern matching (regex supported)
• 📁 File-based state (no database needed)
• 📋 Batch monitoring from URL list
• 🪶 Zero dependencies beyond Python stdlib + requests

Dependencies

pip3 install requests

How State Works

When using watch mode, the script saves a hash of each page's text content in --state-dir. On the next run, it compares the current hash to the saved one. If different, it reports the change and shows a text diff.

State files are named by URL hash, so you can monitor hundreds of sites without collision.