Audit limits
How many audits you can start per day, why the cap exists and when it renews. The numbers are the same on every plan.
Running audits repeatedly is the point: fix, verify, fix again. So that a single account cannot flood someone else's server, there is a cap on the number of audit attempts. Per account it is 24 audits per 24 hours, per site 5.
The cap is abuse protection, not a way for us to save money. Paid audits are paid for with credits, and credits have nothing to do with the cap: a used-up cap means waiting, not buying more.
The numbers
| What is capped | How many | Per |
|---|---|---|
| Audit attempts per account (all sites together) | 24 | 24 hours |
| Audit attempts per single site | 5 | 24 hours |
| Free audit per domain | 1 | calendar month |
| Sites (projects) per account | 10 | at any time |
What counts are attempts, not finished audits: an audit that ended with an error counts too. Without that, the same site could be crawled indefinitely by letting every audit fail.
The numbers are the same on every plan. A paid account has no more reason to crawl the same site ten times in a row than a free one, and the cap protects the server we are looking at, not our wallet.
How the cap renews
It renews continuously, not at midnight. The window is the last 24 hours: as soon as the oldest attempt is older than 24 hours, one slot frees up. So if you start an audit at 15:42, that attempt drops out of the window at 15:42 the next day.
That is why the app can give you an exact time rather than an estimate. The message about a used-up cap says how many attempts the window allows, how many are left, and when the next one becomes possible, in your browser's time zone.
Until 19 September 2026 it was a calendar day, which had an awkward property: at 23:50 you had ten minutes left and at 00:10 a whole new batch, with no way to tell. That is why it works differently now.
What counts towards the cap and what does not
- Counts: every audit you start, whether it finishes or fails.
- Does not count: rechecking a single fix in the report (the “Verify fix” button). That has its own daily cap per audit and its own free allowance.
- Does not count: reading a finished report, downloading files or the PDF. None of that sends requests to your site.
- Does not count: an audit we never started because the domain did not respond or
robots.txtkept us out. No credits are charged in that case. Availability checks have their own cap of the same size, so they cannot become a way around this one.
When it is not enough
These numbers are a proposal to be revised against real traffic, not a fixed product boundary. If you work at a larger scale, write to us: the cap can be raised by arrangement, and your feedback is exactly what the number changes according to.