Scheduled redirect monitoring
A monitor is a saved set of URLs that runs on an interval from 30 minutes to 30 days. Each run fires a webhook on change and optionally appends results to Google Sheets.
How monitors work
A monitor is a saved set of URLs with a check interval. Every time the interval fires, we run a batch inspection on all URLs, store the results, and optionally export them to Google Sheets and fire a webhook.
You can pause, resume, trigger manually, and view the full run history for any monitor. If a monitor fails 5 times in a row, it auto-pauses to prevent runaway checks.
Use cases
Post-migration monitoring
After a site migration, set up a monitor on your top 100 pages. Check every hour for the first week to catch redirect issues before they hurt rankings.
Ongoing SEO health
Monitor your key landing pages weekly. If a redirect chain breaks or a page starts returning 404, you'll know within hours instead of weeks.
Competitor tracking
Monitor competitor URLs to detect domain changes, acquisitions, or rebrand redirects. See where their traffic is being sent.
Affiliate link auditing
Check your affiliate links regularly to make sure they still resolve correctly. Broken affiliate links mean lost revenue.
Monitor specifications
| Minimum interval | 30 minutes |
| Maximum interval | 30 days |
| URLs per monitor | Up to 500 |
| Monitors (Pro) | 50 |
| Monitors (Business) | 250 |
| Usage counting | Each run counts against monthly quota |
| Auto-pause | After 5 consecutive failures |
| Google Sheets | Auto-append results per run |
API-first
Every monitor field is settable via POST /v1/monitors. Pause, resume, trigger, and list runs all have endpoints. Drop a create call into your deploy pipeline to start verifying redirects after every release.
# Create a monitor
POST /v1/monitors
{
"name": "Top pages",
"urls": ["https://example.com", ...],
"interval_minutes": 360,
"sheets_append": true,
"webhook_url": "https://hooks.slack.com/..."
}Set up your first monitor
Monitors are available on Pro and Business plans.