Permission policies for AI bots
Publish clear preferences for search, assistant retrieval, model training, commercial scraping, and archival research.
Control how AI bots interact with your website. Publish clear permissions for crawlers, scrapers, indexing agents, AI assistants, and training-data collectors without making the web harder to use.
User-agent: GPTBot Disallow: / User-agent: Googlebot Allow: / Policy: /botconsent.json
BotConsent turns bot preferences into something your team can manage and crawlers can discover.
Publish clear preferences for search, assistant retrieval, model training, commercial scraping, and archival research.
Create robots.txt and llms.txt-style outputs that point crawlers to your canonical BotConsent policy.
Give people and software a stable URL for your bot permissions, contact route, policy version, and change history.
Review detected agents, policy outcomes, and compliance-ready logs from one operational dashboard.
Start with a plain-language policy builder, then publish structured files and connect enforcement where it matters.
Verify your domain with DNS, meta tag, or file-based ownership checks.
Choose category-level defaults and add bot-specific overrides when needed.
Publish policy files and connect monitoring or edge enforcement.
Review changes, crawler activity, and exportable consent history.
BotConsent is calm infrastructure for the messy edge between discovery, attribution, and reuse.
BotConsent treats consent as an operational record: who changed a policy, what it says, where crawlers can find it, and how suspicious activity should be reviewed. It is designed for Cloudflare-friendly deployment, privacy-conscious defaults, and human-readable governance.
Simple plans for solo site owners, growing teams, and portfolios.
$0
For basic policy publishing
Start free$19/mo
Per site, per month
Get ProCustom
For teams and portfolios
Contact salesAI crawler consent is evolving. BotConsent keeps the first version understandable.
No. BotConsent complements robots.txt by adding AI-specific use cases, hosted policy pages, and richer policy history.
No policy file can force every actor to comply. BotConsent publishes preferences for responsible bots and can feed enforcement workflows for suspicious traffic.
No. The product is designed so founders, publishers, and site owners can set practical defaults, while developers still get structured output and API-friendly workflows.
This website and MVP are prepared for Cloudflare Pages with a static Astro build and a Pages Function for contact form handling.