Open Bulk Scanner in the sidebar. Upload a CSV with 1 domain per row (max 50 per batch) and click Start Scan. LemAudit audits each domain in parallel and creates 1 lead per row in your pipeline. A 50-domain batch finishes in 6–10 minutes.

What "bulk" actually does

The scanner runs the same audit pipeline for each row in your CSV. Every row becomes 1 row in your leads table. It carries the same health score, the same findings list, and the same AI outreach drafts a manual audit would produce. The only difference is throughput.

Think of it like batch-printing photos. Same printer, same paper, you just queue 50 in one go instead of clicking print 50 times.

How LemAudit processes the batch

CSV uploads land in the bulk_scans table with status = 'queued'. The bulk-scan-runner edge function processes rows in chunks of 5 in parallel. Each audit has a 30-second hard timeout, so 1 stuck domain cannot stall the whole batch. Failed rows are marked but do not stop the run. You see them in the result table with a red error badge. Re-audit them later when you fancy. Every row counts toward your monthly audit cap, including failures.

Bulk scanning is gated to Growth and Agency plans; Starter sees the menu item with an upgrade link.

Worked example

A B2B agency targeting independent insurance brokers exported 47 domains from a directory site, pasted them into a CSV, and uploaded. Total wall-clock: 7 minutes 42 seconds. 41 audits succeeded, 6 failed (4 sites returned 403, 2 timed out on Cloudflare). Of the 41 successful audits, 12 scored under 60 — they emailed those 12 first and booked 3 calls within the week.

When this isn't right

50 is the per-batch cap; for 500-domain lists, run 10 batches over a few days to avoid burning your monthly quota in 1 sitting. If your CSV came from a discovery tool that already has email addresses (Apollo, Hunter), you do not need LemAudit to find the contact. Just use the audit data. For ongoing scheduled rescans, use the automatic re-audit loop instead of re-uploading the same CSV.