Publish your terms for AI bots
Create a hosted policy page that explains what crawlers may do with your content and where licensing inquiries should go.
Generate crawler rules, publish AI-use permissions, and prepare your content for licensing or blocking.
Use these snippets as a starting point, then publish a canonical policy page.
BotConsent is not a magic shield. It gives your site a clear policy layer, deployable technical signals, and an upgrade path for teams that need hosting, audits, and alerts.
Create a hosted policy page that explains what crawlers may do with your content and where licensing inquiries should go.
Generate robots.txt, llms.txt, Content Signals-style language, and commercial-use terms that fit your policy.
Use the audit and monitoring flows to spot missing bot groups, conflicting directives, and changes that could affect crawler access.
Generate basic policy snippets after email capture.
Publish a hosted policy page for one domain.
Monitor policies across multiple domains.
Manage client crawler policies at scale.
The audit is for website owners who want to know what their current crawler policy says before they buy ongoing monitoring.
Good search coverage. Training and commercial-use terms need clearer signals.
No. BotConsent helps publish preferences, document terms, prepare technical signals, and monitor policy readiness. BotConsent is not legal advice and cannot guarantee crawler compliance.
Yes. That is the default policy posture in the generator: allow search indexing and assistant retrieval, while blocking model training and commercial scraping unless you turn them on.
Cloudflare offers infrastructure-level crawler controls and Pay Per Crawl experiments. BotConsent is independent and helps you draft, publish, and monitor policy language that can complement whatever infrastructure you use.
BotConsent includes common crawler tokens such as GPTBot, OAI-SearchBot, ChatGPT-User, and Google-Extended as editable starting points. You should review official crawler documentation before publishing.
Some do, some do not. A published policy is still useful for good-faith operators, partners, internal documentation, and legal review, but evasive scrapers may ignore it.
Yes. It helps you publish licensing language, create a canonical inquiry path, and keep policy files consistent while the paid-access market continues to mature.