Scheduled Audits and Email Alerts Are Here
In the monitoring guide, we talked about building audit habits and listed scheduled audits as "coming." They're here now. Along with email alerts.
No more calendar reminders. No more forgetting to check.
What Shipped
Three things:
Scheduled Audits
You can now set up recurring audits for any domain. Pick a frequency:
| Frequency | Best For |
|---|---|
| Daily | High-traffic sites, post-deploy monitoring |
| Weekly | Active blogs, e-commerce catalogs |
| Monthly | Documentation sites, marketing pages |
Each schedule is configurable:
- Max pages: Set a crawl limit per audit
- Ignored routes: Exclude patterns you don't care about (staging paths, admin pages, etc.)
- Per-domain: One schedule per domain per account. No duplicates.
The system handles deduplication automatically. If multiple schedules target the same domain, Glimpse runs one crawl and evaluates alerts independently for each schedule.
Email Alerts
Every scheduled audit can trigger email alerts. You configure two thresholds:
- Score change threshold (default: 10 points): Alert if your health score changes by this many points in either direction. A jump from 72 to 85 triggers it. So does a drop from 85 to 72.
- Minimum score threshold (default: 70): Alert if your score falls below this number.
Or skip thresholds entirely and enable "always notify" to get an email after every audit regardless of score.
The email includes:
- Your current health score with color coding (green/amber/red)
- Score change from the previous run
- Why the alert was triggered
- Your top 5 issues by severity, with affected page counts
- A direct link to the full audit report
You can send alerts to multiple email addresses. Add your team, your client, whoever needs to know. If you don't specify recipients, alerts go to your account email.
Dashboard Integration
The schedules dashboard at /dashboard/schedules is where you manage everything:
- Create, edit, pause, and delete schedules
- View run history for each schedule (last 10 runs)
- See health scores across runs with previous-score comparison
- Check which runs triggered alerts and why
Each domain page also shows its schedule status—active or paused, next run time, last run result.
How the Alert Logic Works
Alerts use OR logic. An alert fires if any condition is met:
alwaysNotifyis enabled → alert on every completed audit- Score <
minScoreThreshold→ alert when score is too low - Score changed by >=
scoreChangeThreshold→ alert on significant movement
Some examples:
| Previous Score | Current Score | Threshold | Min Score | Alert? | Reason |
|---|---|---|---|---|---|
| 82 | 71 | 10 | 70 | Yes | Score dropped 11 points AND below 70 |
| 82 | 78 | 10 | 70 | No | Only dropped 4 points, still above 70 |
| 65 | 68 | 10 | 70 | Yes | Below min threshold of 70 |
| 75 | 88 | 10 | 70 | Yes | Score changed by 13 points (improvements count too) |
The logic runs independently per schedule. Two schedules for the same domain can have different thresholds and different recipients.
Use Cases
Agency Monitoring
Set up weekly audits for all client sites. Configure alerts to fire only when something breaks (score drop >= 10 or below 70). Your team gets notified without checking every site manually.
Different clients get different alert recipients. Send the alert to your account manager and the client's technical contact.
Post-Deployment Checks
Pair daily audits with your deploy schedule. If a Friday deploy breaks meta tags or creates redirect chains, you'll know by Saturday morning. Fix it before Monday traffic arrives.
Ongoing SEO Tracking
Monthly audits for stable sites. Weekly for active ones. Track your score trend over time. When a stakeholder asks "how's the site doing?"—you have the data.
Regression Detection
The score comparison catches problems that manual spot-checks miss:
- CMS updates that change meta tag output
- Plugin updates that break canonicals
- Content imports that create duplicate pages
- Theme changes that drop structured data
If the score changes by 10+ points, something happened. The alert tells you to go look.
How to Set Up
- Sign in to your Glimpse account
- Go to Dashboard > Schedules
- Click New Schedule
- Enter your domain URL
- Pick a frequency (daily, weekly, or monthly)
- Set your max pages limit
- Configure alert thresholds:
- Score change threshold (how many points of change triggers an alert)
- Minimum score threshold (alert if score falls below this)
- Or check "Notify on every audit" to always get emails
- Add alert recipients (optional—defaults to your account email)
- Save
Your first audit runs at the next scheduled time. After that, it repeats on your chosen frequency.
Under the Hood
A cron job runs daily and checks which schedules are due based on their nextRunAt timestamp.
For domains with multiple schedules, the system deduplicates: it runs one crawl using the highest maxPages across all schedules, and only ignores routes that every schedule agrees on. This avoids redundant crawling.
The crawl itself is fire-and-forget from the cron endpoint's perspective. After the crawl completes, the system evaluates alert conditions for each schedule independently and sends emails via Amazon SES. Each schedule gets its own alert evaluation with its own thresholds.
Run records capture the health score, previous score, whether an alert was sent, and the reason. This history is visible in your dashboard.
What's Next
Scheduled audits and email alerts are the foundation. We're working on:
- Slack and Discord notifications: Webhook-based alerts for team channels
- CI/CD integration: Trigger audits from your deployment pipeline
- Trend dashboards: Visualize score and issue history over time
- PDF export: Generate reports for stakeholders
Get Started
Set up your first schedule at get-glimpse.com/dashboard/schedules.
Or if you haven't tried Glimpse yet, run a free audit at get-glimpse.com to see where your site stands first.
Questions or feedback? Email ashish.so@redon.ai