How does automatic re-auditing work
Toggle Auto re-audit on any lead and LemAudit re-runs the [audit pipeline](/help/audits/how-do-seo-audits-work) every 30 days. The new score and findings ov…
Toggle Auto re-audit on any lead and LemAudit re-runs the audit pipeline every 30 days. The new score and findings overwrite the current set; the previous version stays in the lead's audit history chart for trend comparison.
What auto re-auditing is for
The job is freshness. A lead audited 6 months ago and never refreshed is a stale lead. The prospect may have fixed everything, or made it worse. Your outreach draft will then reference issues that no longer exist. A 30-day cadence keeps the data current enough to pitch from without burning your audit quota every week.
Think of it like an automatic credit-score check. You do not need it daily; you need it before you ask the bank a question.
How LemAudit schedules it
A daily cron at 3am UTC runs the auto-reaudit-loop edge function. It selects every lead with auto_reaudit = true and last_audit_at older than 30 days, then queues each one through the same run-audit pipeline a manual re-audit would. We rate-limit to 100 re-audits per agency per night to avoid quota spikes; overflow rolls into the next night's batch. Each completed re-audit fires the same webhook (`audit.completed`) so your downstream tools see the refresh too.
The audit_history table keeps the last 20 runs per lead, which powers the trend chart on the lead detail page.
Worked example
A B2B agency turned auto re-audit on for 80 cold leads from a Q1 batch. 30 days later they got an alert (via webhook) for 6 leads whose scores had dropped by more than 10 points. They opened 1 — a coaching site that had added a heavy unoptimised video — and used the score drop as the hook of a follow-up email. The prospect replied within 4 hours and booked a call.
When this isn't right
Auto re-auditing every lead in your pipeline burns through quota fast — limit it to high-value Hot leads or active outreach targets, not the whole list. For sub-30-day cadences (e.g. weekly), do them manually; the cron is fixed at 30 days to keep LemAudit from looking like a misbehaving crawler to your prospects' analytics tools. For pure rank-tracking (positions in SERPs), use a dedicated tool — LemAudit measures site health, not Google ranks.