The terms, in plain language.
The operational limits below are the ones the system enforces, so they are worth reading even if the legal sections are not yet final.
Working draft, not a contract. The service limits described are accurate and enforced. The legal terms have not been reviewed by counsel and this page must not be relied on as terms of service until they have been.
What the service does
Crawld crawls sites you are entitled to have crawled, scores them against a published rubric, and, on paid plans and where you have granted access, proposes changes for your approval. It does not publish changes without your explicit approval at two separate points.
Service limits
| Limit | Value |
|---|---|
| Free scan crawl depth | 10 pages per scan |
| Free scan frequency | One real crawl per domain per day |
| Free scan submissions | 3 per hour per caller |
| Shared scorecard lifetime | 30 days |
| Competitor monitoring | Up to 3 sites, 12 pages each, weekly |
What we ask of you
- Only submit sites you are entitled to have crawled. The scanner causes real requests to real infrastructure. Pointing it at a third party you have no relationship with is a misuse of it, and the per-domain cooldown exists partly to limit the damage that misuse could do.
- Do not attempt to circumvent the abuse controls. Rotating addresses to bypass the domain cooldown, or automating around the CAPTCHA, is grounds for a block.
- Review what you approve. The gates are not decorative. A change you approve is a change you have chosen to make to your own site.
What we do not promise
Being specific here is more useful than a disclaimer paragraph:
- No ranking outcome is promised. Nobody can promise one. The rubric measures things that are within your control; where you rank is not among them.
- A score is a claim about what was measured. Coverage is reported next to every score precisely so that the claim is bounded rather than implied to be total.
- Advisory means advisory. A finding delivered without repository access has not been verified against a build, and the label says so. Applying it is your decision.
- Availability is not contractually guaranteed. If the scanning engine is unavailable, a scan fails and reports that rather than returning a fabricated result.
Payment and cancellation
Plans are billed per site rather than per seat. Cancelling stops future billing and ends ongoing scans, monitoring and queue access. Changes you already merged are yours. They live in your repository or your CMS, not in ours, and cancelling does not reach into them.
Your content
You keep ownership of your content and of the changes generated for your site. We use crawl data to operate the service for you. We do not resell it and we do not train models on it. Content is sent to a large-language-model provider in order to run model-judged checks: see Privacy, which states that plainly rather than in a sub-processor footnote.
Ending the relationship
You can delete your account, which deletes the crawl data and findings held against it, and you can revoke repository or CMS access independently at any time. Revocation takes the associated data with it.