Custom audit rules

Who this is for

Workspace Admin or Owner teams standardising quality gates beyond the built-in checks.

When to use this screen

When you want pass-or-fail criteria (for example "title must exist", "load time under N seconds") evaluated on new audits.

Before you start

Rules must be enabled to run. Use Templates if you prefer curated starters.

In the app

1. Under Audit & Analysis, choose Custom Rules (route /rules).
2. The page loads your workspace list and shows how many rules are enabled.

Create or edit a rule

• Name and Description.
• Category: SEO, performance, security, UX, accessibility, content, custom.
• Severity: critical, high, medium, low, info, warning.
• Condition: Field, Operator (contains, equals, greater_than, matches_regex, exists, and others), Value, Fail message, optional Recommendation.

Save to persist; toggle enable or disable without deleting.

Templates

Templates seeds Rule templates instead of blank conditions.

Test against sample JSON

Test (flask icon). Paste page JSON to see whether the rule triggers and which field value was read.

Behaviour on audits

Enabled rules evaluate when new audits complete. Violations surface alongside standard findings in the audit UI.

Common pitfalls

• Rule never fires. Confirm it is enabled, that the Field path matches the API page JSON, and that the Operator suits the data type.
• Too much noise. Raise the Severity threshold or narrow the Category ownership.

Related

• Compare two audits to prove a fix cleared a rule.
• Reading audit run results.