Describe the standard
Use the visual builder for titles, schema, phrases or page metrics.
Reach / Rules▊
Add the checks your team actually cares about, from product schema to tired AI phrases. Crawlie runs them on every crawl, so good intentions become part of the process.
Use the visual builder for titles, schema, phrases or page metrics.
Dry-run against your last crawl and see exactly what it would flag.
Every future crawl scores against your rules, with alerts on regressions.
Why it wins
Start with a template or build your own check. Choose the pages, the condition and how serious a miss should be.
Flag clichés, filler, repeated phrasing and the habits that make scaled content feel mass produced.
Test a rule against your last crawl, look at the matches, then switch it on when it feels right.
Content rules
Rule packs are plain .crawlie files. They run the same way every time, work in CI, and can live in git beside the site.
Don’t start from blank
Pick a useful starting point, change the scope, then test it against your latest crawl before it goes live.
Browse the built-in checks →Brand name in every titleKeep search snippets consistent
Ban tired AI phrasesFlag clichés and filler automatically
Authors on advice pagesRequire a named author on /guides/*
Product schema on product pagesCheck every /products/* route
AI clichés“unlock the power of”
Rule of three“fast, reliable and scalable”
Filler heavyfiller ratio above 0.04
No black box at runtime
Rules are deterministic. Every point traces back to the rule and the exact evidence that fired it, so writers can fix the sentence instead of debating a mystery score.
One open format
The `.crawlie` file can live in git beside the site. Your cloud workspace, local crawler and CI job all read the same rulebook.
Agent-native
Everything on this page is a tool call away. The hosted MCP server exposes 18 tools — crawls, reports, fixes, monitoring — and the REST API speaks the same JSON. One key, no scraping, no glue code.
> flag AI clichés on every crawl
list_rules → 148 built-in checks
explain_issue slop-cliche → why + fix
+ brand-voice.crawlie committed to git
crawl_site → scores your rules too
deterministic · same words, same score
Phrases, regular expressions, page metrics and required structured data, scoped to the pages you choose — like requiring Product schema on /products/* or banning "in today's fast-paced world" everywhere. Each rule gets a severity: notice, warning or error.
A plain-text rule pack. It can live in git beside your site, and the same file runs in your cloud workspace, the open-source CLI and CI — one rulebook, enforced everywhere.
Yes. Built-in content rules flag tired AI clichés, heavy filler ratios, repeated n-grams and low lexical diversity — the habits that make scaled content feel mass-produced. Every point traces to the rule and the exact evidence that fired it.
Completely. Rules are not an LLM judgment call — the same words in produce the same result out, every crawl, in every environment. That makes them safe to gate CI on.
Yes — dry-run any rule against your latest crawl and see exactly which pages it would flag before switching it on. After that, every future crawl scores against it, with alerts on regressions.
Free to start on the Hobby plan — 5,000 crawl credits a month, no card required.