Custom rules

Your standards, enforced on every crawl

The Rules tab holds your workspace’s own checks. Once enabled, they run on every crawl in the workspace, and their findings appear in reports alongside the built-in checks (in the report’s Rules tab, and in regression alerts).

Building a rule

The visual builder walks you through it:

1. Scope — which pages the rule applies to (all pages, or a URL pattern).
2. Condition — what to require or forbid: text, elements, schema, page properties.
3. Severity — error, warning, or notice.
4. Why & fix — the explanation your teammates see when the rule fires.

Before saving, preview the rule against your last crawl — you see exactly which pages would fire, so you can tune it on real data instead of guessing.

Prefer text to dropdowns? There’s a raw editor for the underlying .crawlie rule language — the same open format the OSS crawler uses.

The template library

You don’t have to start blank. The library ships ready-made rules across seven categories — SEO, content quality, brand & voice, trust & compliance, conversion, technical hygiene, and AI & GEO. A few examples:

• Brand name must appear in the title tag
• Product pages must carry Product schema
• No lorem ipsum / placeholder copy anywhere
• No links to staging or localhost hosts
• AI-slop detector on blog content

Add one, tweak the scope, done.

Content rules and page checks

Two kinds of rule, split by plan:

• Content rules (banned phrases, regex patterns — the anti-slop toolkit) run on every plan, and produce a pack score you can track over time.
• Page checks (require/forbid elements, schema, page properties) are a Pro feature. See Plans.

Managing rules

Rules live in your workspace’s rule pack, which you can toggle on or off as a whole or delete. One thing to know: rules are workspace-wide — an enabled pack applies to every crawl in the workspace, not per project.