Batch Audits let you run audits on up to 50 URLs in one go. Results are saved to your project and grouped as a single batch run, so you can review them together or open individual reports for any URL in the batch.
How to run a batch audit
- Open a project and go to Batch Audits.
- Choose your input method:
- Paste a list — enter one URL per line, up to 50 URLs.
- Upload a CSV — the first column of each row is used as the URL; headers are ignored.
- Start the run. URLs are processed sequentially — expect about 30 seconds per URL.
- Results appear as the run progresses. You do not need to keep the page open.
Tracking completed pages
After a batch completes, a Track all completed pages button appears at the top of the batch detail. This adds every successfully audited URL to your project’s tracked list in one step, making them available for monitoring.
You can also open the report for any individual URL in the batch to view its full results.
Batch statuses
Each batch run shows one of these statuses:
| Status | Meaning |
|---|---|
| Running | The batch is actively processing URLs |
| Pending | The batch is queued and will start shortly |
| Completed | All URLs finished successfully |
| Completed with issues | Some URLs finished, some failed |
| Failed | The batch could not run |
| Canceled | The batch was stopped before completing |
URL-level failure reasons
When individual URLs fail within a batch, the batch detail shows a failure summary with categorized reasons:
DNS unresolved — the domain could not be found. Check for typos or whether the domain is active.
Blocked / challenged — the server returned a bot challenge or access denial. The page may be behind Cloudflare or another bot protection system that blocked the audit request.
Timeout — the page took too long to respond. Check whether the URL is accessible from outside your network.
TLS / certificate — an SSL/TLS error prevented the connection. Check whether the certificate is valid and not expired.
Render capacity — the audit service was temporarily at capacity for content rendering. Re-running the affected URLs usually resolves this.
Service unavailable — the server returned a 5xx error. The page may have been down during the run.
Aborted — the audit was stopped mid-run. Re-running will attempt the URL again.
Other failure — an unexpected error. Use the Show technical details toggle in the batch row for more information.
Common uses
Auditing a site section — paste the URLs for a product category, blog index, or landing page set to get a snapshot of AI visibility across the whole section at once.
Pre-launch checks — before going live with new pages, batch-audit the staging or preview URLs to catch crawlability or performance issues early.
Competitor research — audit a set of competitor URLs to benchmark their AI visibility against yours.
After a site migration — batch-audit the redirected URLs to confirm the new destinations are accessible and performing as expected.
Limits
Batch runs are capped at 50 URLs per run. If you need to audit more, run multiple batches. On Plus and Pro plans, batches count against your monthly audit quota.