Audit settings

Cloud audits don’t read your local squirrel.toml, so the Website → Settings → Audit page in the dashboard is where you control which rules run in the cloud for a given website.

Open it at Dashboard → your website → Settings → Audit. Anyone in the organization who can open the website can change these settings.

Rule selection

Every audit rule is on by default. The page lists all rules grouped by category (sorted by priority). For each rule you can:

• Toggle it on or off individually.
• Toggle a whole category with the category master switch (it shows a mixed state when only some rules in the category are on).
• Enable all / Disable all across every category.
• Search by rule name or id to jump to a specific rule.

The header shows how many rules are enabled out of the total. Changes are staged locally: click Save to apply them.

This setting is per website: it applies to every cloud audit of this website (dashboard-triggered and scheduled). It does not affect CLI audits, which keep using your local config.

Cloud rules

Some rules are powered by cloud services. Most are included in the audit base charge; the opt-in gap rules carry their own charge and are marked with a credit badge. See Credits for the full pricing.

External link checking

A separate card toggles external link checking for cloud audits. When on, audits verify that outbound links resolve, using the dead-links service. It is the same setting as External link checks in the site’s audit level, so the two always agree: on at every level, Quick included, and for a site added before audit levels, unless you turn it off. Change it on a site that is on a level and the site becomes Custom. Each distinct external link a cloud audit can verify costs 1 credit, whether it works or is broken, and the same link on many pages is checked and charged once. A link behind a bot wall or a throttle, which the report lists as unverified, costs nothing, and internal links are free. An audit is charged for at most one external link per page of its page budget, so Max credits per audit caps link checks too. The card links to your org’s credit usage.

Turn it off and this website’s audits skip external links until you turn it back on or choose a preset level. Broken link alerts are a separate setting, under Website → Settings → Alerts.

Max credits per audit

The Max credits per audit card sets a hard spend ceiling for a single cloud audit of this website. Leave it blank for no cap.

• A run the cap can’t fully cover audits fewer pages instead, as many as the cap pays for, so it never goes over. The Run dialog says so before you start, and scheduled runs do the same.
• Only a cap below a one-page audit stops a run. A manual run then doesn’t start and the Run dialog shows an error; a scheduled run is skipped, and you get an in-app notification (“Scheduled audit skipped…”) so a recurring audit can never bill-shock. Raise the cap to proceed.
• When a run proceeds, the cap is also passed to the cloud worker as a runtime ceiling, so spend stops there even if the actual cost climbs.

The estimate is an upper bound: the audit is billed as it runs (50 credits base plus 2 per audited page, plus 1 per external link checked when that is on, at most one per page; links past that are checked free, see Credits), so most audits cost less than the cap. This setting is per website.

Email notifications

A sibling page, Website → Settings → Alerts, holds the Email notifications toggle for this website. It controls the audit completion email, the audit failure email, the scheduled-audit digest, and, on Pro and Team, broken link alerts, which also have their own Broken link alerts switch on that page.

A few emails are account level and arrive whatever this toggle says, including the low-credit warning and the notice that a website’s recurring audits paused themselves. Emails we send lists every automatic email, what triggers it, and where its off switch is.

What runs where

Surface	Honors this website’s audit settings?
Dashboard cloud audits	Yes
Scheduled cloud audits	Yes
CLI audits (squirrel audit)	No, uses your local squirrel.toml

Per-rule option tuning (thresholds and the like) isn’t configurable here yet: it’s tracked as a follow-up.