Site audits in the dashboard
Launch a crawl, watch it run, and work through the issues.
A site audit crawls the project's domain and checks every page against 27 issue types, with Lighthouse on a sample. The crawler's behaviour, the page caps, and the agent tools are documented under Site audits; the checks themselves are listed under Audit issue types.
Launching
Open Site Audit in the project sidebar. The launch form asks for a page budget (default 50) and whether to run Lighthouse (on by default). The budget is capped by plan: 50 pages on Free, 1,000 on Starter, 5,000 on Pro, 10,000 on Scale. Asking for more is trimmed to the cap, and the page says so, rather than refused. The project needs a domain.
Cost scales with the number of pages crawled, plus up to 20 Lighthouse runs (10 URLs, mobile and desktop).
While it runs
The audit page shows the phase (discovery, crawling, lighthouse, finalizing), pages crawled so far, and a live feed of URLs. Crawls take minutes; a large site with a slow server takes longer. If the site takes too long to respond the audit fails with a message suggesting a smaller page limit.
If pages come back as blocked
Bot protection that challenges the crawler is reported honestly as a blocked page, not a broken one. Allowlist the IndexZero-Audit user agent in your WAF (on Cloudflare, a WAF custom rule that skips bot protection when the user agent contains that string) and run the audit again.
Reading results
The finished audit shows issue counts by severity, then each issue type as an expandable group with the explanation, the fix, and the affected URLs. Work through critical issues first. Below that are the crawled pages with status, title, word count, and H1s, and the Lighthouse table with scores and Core Web Vitals per sampled URL. Everything exports to CSV.
Deleting an audit removes its results and its crawl state.