{ "slug": "licensing-content-for-ai-training", "title": "Licensing Content for AI Training: RSL, Terms, and Provenance", "description": "How to publish machine-readable licence terms for AI use — what RSL is, what it does and does not do, how it differs from robots.txt and Content Signals, and where provenance standards fit.", "kind": "sub", "order": 11, "target_query": "how to license website content for AI training", "secondary_queries": [ "RSL really simple licensing explained", "machine readable license for AI crawlers", "terms of service AI training clause" ], "tags": [ "licensing", "rsl", "provenance", "policy", "monetization" ], "published": "2026-07-26", "updated": "2026-07-26", "words": 1042, "premium": false, "license": "https://changegamer.ai/license.xml", "canonical": "https://changegamer.ai/articles/licensing-content-for-ai-training", "markdown": "https://changegamer.ai/articles/licensing-content-for-ai-training.md", "takeaways": [ "Four layers, four different jobs: `robots.txt` controls access, Content Signals declare usage preference, a licence states terms, and a payment gate enforces a price. None substitutes for another.", "RSL (Really Simple Licensing) is a machine-readable licence document, typically an XML file discovered via a `License:` directive in robots.txt. It declares terms and compensation; it does not collect money.", "A licence is only useful if it is discoverable, free to read, unambiguous about the unit being licensed, and versioned.", "Provenance standards (C2PA Content Credentials) prove where an asset came from. That is a different guarantee from a licence and increasingly asked for alongside one.", "Publish the licence even if you never sell anything: it converts \"we assume this is allowed\" into a documented position." ], "outline": [ { "depth": 2, "text": "The four layers, ordered by force", "anchor": "the-four-layers-ordered-by-force", "url": "https://changegamer.ai/articles/licensing-content-for-ai-training#the-four-layers-ordered-by-force" }, { "depth": 2, "text": "RSL: a licence a machine can read", "anchor": "rsl-a-licence-a-machine-can-read", "url": "https://changegamer.ai/articles/licensing-content-for-ai-training#rsl-a-licence-a-machine-can-read" }, { "depth": 2, "text": "Human terms and machine terms must match", "anchor": "human-terms-and-machine-terms-must-match", "url": "https://changegamer.ai/articles/licensing-content-for-ai-training#human-terms-and-machine-terms-must-match" }, { "depth": 2, "text": "Provenance: proving origin, not permission", "anchor": "provenance-proving-origin-not-permission", "url": "https://changegamer.ai/articles/licensing-content-for-ai-training#provenance-proving-origin-not-permission" }, { "depth": 2, "text": "What licensing gets you, honestly", "anchor": "what-licensing-gets-you-honestly", "url": "https://changegamer.ai/articles/licensing-content-for-ai-training#what-licensing-gets-you-honestly" }, { "depth": 2, "text": "A minimum viable rights stack", "anchor": "a-minimum-viable-rights-stack", "url": "https://changegamer.ai/articles/licensing-content-for-ai-training#a-minimum-viable-rights-stack" } ], "faq": [ { "question": "Does a licence file stop AI companies training on my content?", "answer": "Not mechanically. Like robots.txt and Content Signals, it is a declaration rather than an enforcement mechanism. Its value is that it states terms in a form a machine can read and a human can cite, which is the precondition for any conversation — commercial or legal — about use." }, { "question": "Is RSL a standard?", "answer": "It is a published specification (rslstandard.org), announced in 2025 and in early adoption as of 2026 — not an IETF or W3C standard. Publishing one is cheap and low-risk; assuming universal support for it is not." }, { "question": "Do I still need terms of service language?", "answer": "Yes. The machine-readable document and your human-readable terms should say the same thing and reference each other. A licence file that contradicts your terms of service is worse than either alone." }, { "question": "What should the licence actually license?", "answer": "Be explicit about the unit and the rights: individual documents versus the whole corpus, training versus retrieval-time grounding versus redistribution, named licensee versus anyone, perpetual versus term-limited, updates included or not. Vagueness here is what makes licences unusable to a buyer with a legal department." } ], "body": "Every site already has an implicit answer to \"may AI companies use this?\" — usually \"nobody asked\". Publishing a licence replaces the guess with a statement. This is the rights layer of [the agent-ready website](/articles/agent-ready-website).\n\n## The four layers, ordered by force\n\n| Layer | Where it lives | What it says | Enforced by |\n|---|---|---|---|\n| Access | `robots.txt` `Disallow` | \"Do not fetch this\" | Voluntary compliance |\n| Usage preference | Content Signals in `robots.txt` | \"You may fetch it; here is what you may use it for\" | Voluntary compliance; possible legal relevance |\n| Licence | RSL document (e.g. `/license.xml`) | \"These are the terms and the compensation\" | Contract/copyright law, if pursued |\n| Price | HTTP 402 / paid API | \"Pay this to get it\" | Actually enforced by your server |\n\nSites conflate these constantly. A `Disallow` is not a licence. A licence is not a paywall. Content Signals — the `search` / `ai-input` / `ai-train` directives Cloudflare announced on 24 September 2025 and defaulted on for over 3.8 million domains at `search=yes, ai-train=no` — are preferences, and Cloudflare says so explicitly while noting they \"might have legal rights in various jurisdictions\", citing the EU text-and-data-mining opt-out in Directive 2019/790. Details in [content signals explained](/resources/content-signals-explained).\n\nUse all four, deliberately, and make sure they agree. Contradiction between layers is the thing a counterparty will point at.\n\n## RSL: a licence a machine can read\n\nRSL (Really Simple Licensing) is an XML licence document — commonly served at a path such as `/license.xml` — declaring licensing terms, usage boundaries and compensation requirements. It is discovered through a `License:` directive in `robots.txt`, and can also be advertised via HTTP headers, RSS, or an HTML ``. The spec lives at rslstandard.org; it was announced in 2025 and remains in early adoption as of 2026.\n\n```\n# robots.txt\nLicense: https://example.com/license.xml\n```\n\nWhat to make sure your document actually pins down — this is where most published licences are too vague to be usable:\n\n1. **The unit.** A single document? A category? The complete corpus as one deliverable? \"Our content\" is not a unit.\n2. **The rights, separately.** Training a model, retrieval-time grounding (RAG), indexing for search, redistribution, and creating derivative works are five different permissions. Grant or withhold each explicitly.\n3. **The licensee.** Named entity, or anyone who pays? Named licensees are what enterprise buyers expect; open terms are simpler to operate.\n4. **Term and updates.** Perpetual for the snapshot bought, or a subscription including future updates? Buyers of a corpus care enormously about this and will ask.\n5. **Compensation.** A price, a pointer to a price, or \"contact us\". The first two are machine-actionable; the third is where machine buyers stop.\n6. **Attribution requirements,** if any, in a form a generated answer can satisfy.\n\nKeep the document free to fetch, always. A licence behind a paywall cannot be evaluated, which means it cannot be accepted.\n\n## Human terms and machine terms must match\n\nPublish two representations of one policy: the machine-readable licence and a prose page a person can read and quote. Generate them from the same source if you can, and reference each in the other. When they disagree — because someone updated the prose and forgot the XML — the disagreement itself becomes the story.\n\nPractical structure that works:\n\n- `/license.xml` — the RSL document, referenced from `robots.txt`.\n- `/terms` and `/terms.md` — the same terms as prose, with a Markdown twin so agents can read them cheaply.\n- `/api/pricing.json` — the machine-readable offer catalogue, if you sell access.\n- Every `402` response body linking to all three.\n\nThe worked example this site publishes — free tier, paid tiers, what each licence grant actually permits, and the promise that index files and terms are never gated — is in [access and pricing for crawlers](/resources/access-and-pricing).\n\n## Provenance: proving origin, not permission\n\nA licence says what may be done with your content. Provenance says *this really is your content, and here is its history*. The two are complementary and increasingly requested together, particularly for images, documents and anything that could be fabricated.\n\nC2PA Content Credentials attach cryptographically signed assertions about origin and edit history to an asset, verifiable independently of the site serving it — see [C2PA content credentials](/resources/c2pa-content-credentials). The broader question of how provenance travels through data supply chains, and where the guarantees break, is covered in [AI supply chain provenance](/resources/ai-supply-chain-provenance).\n\nFor text-heavy publishers the practical version is more mundane and still valuable: dated revisions, a real changelog, stable canonical URLs, and a corpus export with a version number. Those are the things that let a buyer prove which version of your content they licensed.\n\n## What licensing gets you, honestly\n\nThree realistic outcomes, in descending order of likelihood:\n\n1. **A documented position.** Cheap, immediate, and useful the first time anyone asks. It also removes the \"we assumed it was fine\" defence.\n2. **A usable answer to inbound interest.** When a buyer with a legal department appears, the difference between a licence file plus a price and a contact form is weeks of process.\n3. **Revenue.** Real, but concentrated among sites with scarce content — proprietary data, verified freshness, structure nobody else provides. The arithmetic is in [what to charge AI crawlers](/articles/what-to-charge-ai-crawlers).\n\nWhat it does not get you is enforcement. Enforcement is a WAF rule or a 402 gate, and the mechanisms for the latter are compared in [agentic payment protocols](/resources/agentic-payment-protocols) with the implementation in [implementing an HTTP 402 paywall](/articles/http-402-paywall-implementation).\n\n## A minimum viable rights stack\n\n1. Decide your position on training, grounding and redistribution — three separate answers.\n2. Express access in `robots.txt` per user-agent token ([should you block AI crawlers?](/articles/should-you-block-ai-crawlers)).\n3. Express usage preference with Content Signals in the same file.\n4. Publish an RSL document and point at it with `License:`.\n5. Publish prose terms saying the same thing, with a `.md` twin.\n6. If you sell anything, publish a machine-readable offer catalogue and link it from every 402.\n7. Version all of it, and keep old versions resolvable — a buyer needs to prove what the terms said on the day they agreed.\n\nNone of that requires a lawyer to start, and all of it makes the eventual lawyer conversation shorter.", "cluster": { "id": "agent-ready-web", "title": "The agent-ready web", "description": "How to make a website readable, citable, controllable and payable for AI agents and AI crawlers — the operator side of the machine-first web.", "status": "complete", "pillar": { "slug": "agent-ready-website", "title": "The Agent-Ready Website: A Complete Guide to AI Visibility, Access Control and Monetization", "description": "The full operator playbook for making a website work for AI agents and AI crawlers: be fetchable, be readable, be controllable, be payable — with a 30-day implementation plan.", "kind": "pillar", "order": 0, "html": "https://changegamer.ai/articles/agent-ready-website", "markdown": "https://changegamer.ai/articles/agent-ready-website.md", "json": "https://changegamer.ai/api/articles/agent-ready-website.json" }, "articles": [ { "slug": "llms-txt-vs-robots-txt-vs-sitemap", "title": "llms.txt vs robots.txt vs sitemap.xml: Which File Does What", "description": "The three root-level files every agent-ready site publishes, what each one is actually for, and why publishing one does not substitute for the others.", "kind": "sub", "order": 1, "html": "https://changegamer.ai/articles/llms-txt-vs-robots-txt-vs-sitemap", "markdown": "https://changegamer.ai/articles/llms-txt-vs-robots-txt-vs-sitemap.md", "json": "https://changegamer.ai/api/articles/llms-txt-vs-robots-txt-vs-sitemap.json" }, { "slug": "how-to-write-an-llms-txt-file", "title": "How to Write an llms.txt File (Format, Template, and Maintenance)", "description": "A step-by-step guide to writing a useful llms.txt: the exact format, a copy-paste template, what to put under ## Optional, how to validate it, and how to keep it from rotting.", "kind": "sub", "order": 2, "html": "https://changegamer.ai/articles/how-to-write-an-llms-txt-file", "markdown": "https://changegamer.ai/articles/how-to-write-an-llms-txt-file.md", "json": "https://changegamer.ai/api/articles/how-to-write-an-llms-txt-file.json" }, { "slug": "serving-markdown-variants-to-ai-agents", "title": "Serving Markdown Variants to AI Agents: The Cheapest Win in AI Visibility", "description": "How to publish a .md twin of every page — URL patterns, content negotiation, discovery headers, generation pitfalls — and why it cuts what an agent pays to read you.", "kind": "sub", "order": 3, "html": "https://changegamer.ai/articles/serving-markdown-variants-to-ai-agents", "markdown": "https://changegamer.ai/articles/serving-markdown-variants-to-ai-agents.md", "json": "https://changegamer.ai/api/articles/serving-markdown-variants-to-ai-agents.json" }, { "slug": "how-ai-search-engines-choose-sources", "title": "How AI Search Engines Choose Sources (And What You Can Actually Influence)", "description": "What is known, what is claimed and what is speculation about how ChatGPT, Perplexity and AI Overviews pick the pages they cite — and the short list of things a site owner can actually control.", "kind": "sub", "order": 4, "html": "https://changegamer.ai/articles/how-ai-search-engines-choose-sources", "markdown": "https://changegamer.ai/articles/how-ai-search-engines-choose-sources.md", "json": "https://changegamer.ai/api/articles/how-ai-search-engines-choose-sources.json" }, { "slug": "should-you-block-ai-crawlers", "title": "Should You Block AI Crawlers? A Decision Framework by Business Model", "description": "Blocking AI crawlers is four separate decisions, not one. A framework that maps each crawler class to what it costs and earns you, by business model, with the exact robots.txt for each answer.", "kind": "sub", "order": 5, "html": "https://changegamer.ai/articles/should-you-block-ai-crawlers", "markdown": "https://changegamer.ai/articles/should-you-block-ai-crawlers.md", "json": "https://changegamer.ai/api/articles/should-you-block-ai-crawlers.json" }, { "slug": "what-to-charge-ai-crawlers", "title": "What to Charge AI Crawlers: Pricing Models for Machine Buyers", "description": "Per-crawl, per-resource, corpus licence or subscription key — the four ways to price AI access, the arithmetic behind each, and why pricing before you have demand data is the standard mistake.", "kind": "sub", "order": 6, "html": "https://changegamer.ai/articles/what-to-charge-ai-crawlers", "markdown": "https://changegamer.ai/articles/what-to-charge-ai-crawlers.md", "json": "https://changegamer.ai/api/articles/what-to-charge-ai-crawlers.json" }, { "slug": "http-402-paywall-implementation", "title": "Implementing an HTTP 402 Paywall an Agent Can Actually Pay", "description": "A working implementation guide for machine-payable content: the 402 response body, Link headers, key issuance and validation, caching rules, and the mistakes that make a 402 gate unpayable.", "kind": "sub", "order": 7, "html": "https://changegamer.ai/articles/http-402-paywall-implementation", "markdown": "https://changegamer.ai/articles/http-402-paywall-implementation.md", "json": "https://changegamer.ai/api/articles/http-402-paywall-implementation.json" }, { "slug": "structured-data-for-ai-agents", "title": "Structured Data for AI Agents: Which Schema.org Types Earn Their Keep", "description": "Most schema.org markup is invisible to machine readers. The types that are worth the effort for AI agents, how to emit them without drift, and what to build instead of more markup.", "kind": "sub", "order": 8, "html": "https://changegamer.ai/articles/structured-data-for-ai-agents", "markdown": "https://changegamer.ai/articles/structured-data-for-ai-agents.md", "json": "https://changegamer.ai/api/articles/structured-data-for-ai-agents.json" }, { "slug": "json-api-design-for-agents", "title": "JSON API Design for AI Agents: Endpoints They Prefer Over Scraping", "description": "How to publish read-only JSON endpoints that agents choose over scraping your HTML: discovery index, stable shapes, freshness signals, bulk exports, and errors a machine can act on.", "kind": "sub", "order": 9, "html": "https://changegamer.ai/articles/json-api-design-for-agents", "markdown": "https://changegamer.ai/articles/json-api-design-for-agents.md", "json": "https://changegamer.ai/api/articles/json-api-design-for-agents.json" }, { "slug": "measuring-ai-agent-traffic", "title": "Measuring AI Agent Traffic: Server-Side Telemetry That Answers Real Questions", "description": "Why client-side analytics miss AI agents entirely, the minimum row schema to log, the five queries worth running, and how to tell a real crawler from a spoofed user agent.", "kind": "sub", "order": 10, "html": "https://changegamer.ai/articles/measuring-ai-agent-traffic", "markdown": "https://changegamer.ai/articles/measuring-ai-agent-traffic.md", "json": "https://changegamer.ai/api/articles/measuring-ai-agent-traffic.json" }, { "slug": "licensing-content-for-ai-training", "title": "Licensing Content for AI Training: RSL, Terms, and Provenance", "description": "How to publish machine-readable licence terms for AI use — what RSL is, what it does and does not do, how it differs from robots.txt and Content Signals, and where provenance standards fit.", "kind": "sub", "order": 11, "html": "https://changegamer.ai/articles/licensing-content-for-ai-training", "markdown": "https://changegamer.ai/articles/licensing-content-for-ai-training.md", "json": "https://changegamer.ai/api/articles/licensing-content-for-ai-training.json" }, { "slug": "mcp-server-as-distribution-channel", "title": "Running an MCP Server as a Distribution Channel for Your Content", "description": "Why a content site should expose an MCP server, which tools to ship, how discovery and authentication work, how to gate paid tools, and the honest limits of the channel.", "kind": "sub", "order": 12, "html": "https://changegamer.ai/articles/mcp-server-as-distribution-channel", "markdown": "https://changegamer.ai/articles/mcp-server-as-distribution-channel.md", "json": "https://changegamer.ai/api/articles/mcp-server-as-distribution-channel.json" }, { "slug": "why-ai-agents-cant-read-your-site", "title": "Why AI Agents Can't Read Your Site: Twelve Failure Modes and How to Find Them", "description": "A diagnostic catalogue of the twelve reasons AI agents and crawlers fail on real sites — from silent WAF blocks to JS-only rendering — each with the command that detects it and the fix.", "kind": "sub", "order": 13, "html": "https://changegamer.ai/articles/why-ai-agents-cant-read-your-site", "markdown": "https://changegamer.ai/articles/why-ai-agents-cant-read-your-site.md", "json": "https://changegamer.ai/api/articles/why-ai-agents-cant-read-your-site.json" } ] }, "navigation": { "pillar": { "slug": "agent-ready-website", "title": "The Agent-Ready Website: A Complete Guide to AI Visibility, Access Control and Monetization", "description": "The full operator playbook for making a website work for AI agents and AI crawlers: be fetchable, be readable, be controllable, be payable — with a 30-day implementation plan.", "kind": "pillar", "order": 0, "html": "https://changegamer.ai/articles/agent-ready-website", "markdown": "https://changegamer.ai/articles/agent-ready-website.md", "json": "https://changegamer.ai/api/articles/agent-ready-website.json" }, "previous": { "slug": "measuring-ai-agent-traffic", "title": "Measuring AI Agent Traffic: Server-Side Telemetry That Answers Real Questions", "description": "Why client-side analytics miss AI agents entirely, the minimum row schema to log, the five queries worth running, and how to tell a real crawler from a spoofed user agent.", "kind": "sub", "order": 10, "html": "https://changegamer.ai/articles/measuring-ai-agent-traffic", "markdown": "https://changegamer.ai/articles/measuring-ai-agent-traffic.md", "json": "https://changegamer.ai/api/articles/measuring-ai-agent-traffic.json" }, "next": { "slug": "mcp-server-as-distribution-channel", "title": "Running an MCP Server as a Distribution Channel for Your Content", "description": "Why a content site should expose an MCP server, which tools to ship, how discovery and authentication work, how to gate paid tools, and the honest limits of the channel.", "kind": "sub", "order": 12, "html": "https://changegamer.ai/articles/mcp-server-as-distribution-channel", "markdown": "https://changegamer.ai/articles/mcp-server-as-distribution-channel.md", "json": "https://changegamer.ai/api/articles/mcp-server-as-distribution-channel.json" } }, "resources": [ { "slug": "ai-crawler-policy", "html": "https://changegamer.ai/resources/ai-crawler-policy", "markdown": "https://changegamer.ai/resources/ai-crawler-policy.md", "json": "https://changegamer.ai/api/resources/ai-crawler-policy.json" }, { "slug": "content-signals-explained", "html": "https://changegamer.ai/resources/content-signals-explained", "markdown": "https://changegamer.ai/resources/content-signals-explained.md", "json": "https://changegamer.ai/api/resources/content-signals-explained.json" }, { "slug": "agentic-payment-protocols", "html": "https://changegamer.ai/resources/agentic-payment-protocols", "markdown": "https://changegamer.ai/resources/agentic-payment-protocols.md", "json": "https://changegamer.ai/api/resources/agentic-payment-protocols.json" }, { "slug": "c2pa-content-credentials", "html": "https://changegamer.ai/resources/c2pa-content-credentials", "markdown": "https://changegamer.ai/resources/c2pa-content-credentials.md", "json": "https://changegamer.ai/api/resources/c2pa-content-credentials.json" }, { "slug": "ai-supply-chain-provenance", "html": "https://changegamer.ai/resources/ai-supply-chain-provenance", "markdown": "https://changegamer.ai/resources/ai-supply-chain-provenance.md", "json": "https://changegamer.ai/api/resources/ai-supply-chain-provenance.json" }, { "slug": "access-and-pricing", "html": "https://changegamer.ai/resources/access-and-pricing", "markdown": "https://changegamer.ai/resources/access-and-pricing.md", "json": "https://changegamer.ai/api/resources/access-and-pricing.json" } ] }