NovaDB supports RSL 1.0 – How publishers can specifically control the use of their content by AI

RSL (Really Simple Licensing) 1.0 is a new open standard that enables publishers to control the AI use of their content in a transparent and machine-readable manner. NovaDB, as a headless CMS and PIM system, supports RSL and enables structured maintenance and API-supported playback of differentiated license information.

Würzburg, December 15, 2024 – On December 10, 2025, RSL 1.0 was released as an official industry standard. The new, open web standard enables media companies and content providers to define machine-readable terms of use and licensing conditions for their content, particularly with regard to AI training, AI search functions, and automated content processing.

What is RSL 1.0 and what is the standard used for?

RSL is an XML-based specification that allows publishers to precisely define how their content may be used by AI systems and automated crawlers.

Unlike the previous robots.txt file, which only allows yes/no rules, RSL offers a differentiated system for defining usage rights, compensation models, and legal frameworks. The standard was developed by the RSL Technical Steering Committee and is supported by leading technology and infrastructure organizations such as Cloudflare, Akamai, Creative Commons, and IAB Tech Lab.

Over 1,500 media companies worldwide have already endorsed RSL, including The Associated Press, Vox Media, USA Today, Boston Globe Media, Stack Overflow, and The Guardian.

What new opportunities does RSL offer publishers and content providers?

RSL 1.0 introduces differentiated usage categories that enable publishers to control content rights in a granular manner:

• ai-all: Covers all AI usage (training, inference, indexing, generation)
• ai-train: Allows or prohibits the training of AI models
• ai-input: Regulates use in AI-generated responses (e.g., retrieval-augmented generation)
• ai-index: Controls inclusion in AI indexes or retrieval databases
• search: Classic search engine indexing (without AI summaries)

In addition, RSL supports various remuneration models such as commercial licenses, attribution requirements, contribution-based approaches, and more for non-commercial content.

How NovaDB enables the integration of RSL licenses into CMS and PIM

For media companies, the practical implementation of RSL is crucial: license signals must be maintained in a structured manner, linked to content, and played out across various channels. As a headless CMS and PIM system, NovaDB offers the ideal basis for this:

• Structured metadata: RSL-relevant attributes (usage rights, license types, remuneration models) can be stored as configurable fields in the content model
• API-supported playout: The NovaDB Delivery API enables the machine-readable provision of license data for automated systems
• Workflow integration: Approval processes and rights management can be centrally controlled via workflows and roles
• Omnichannel publishing: Content and associated licenses are delivered consistently across all channels (web, app, syndication).

Why is RSL relevant for publishers when dealing with AI?

RSL 1.0 offers a practical alternative to the previous uncertainty in dealing with AI crawlers. Whereas individual license agreements between publishers and AI providers previously had to be negotiated on a case-by-case basis, RSL creates an open, machine-readable standard.

The RSL standard does not technically block crawlers itself. This task is performed by supporting infrastructure providers such as Cloudflare and Akamai. Publishers can thus specify that content should appear in traditional search engines but not be used for AI summaries or model training.

What next steps publishers should take now

Publishers and content providers should develop their RSL strategy as soon as possible:

1. Content categorization: Which content may be used for which AI applications?
2. Define licensing model: Commercial license, attribution, contribution, or release?
3. Technical integration: Store RSL metadata in the CMS/PIM and make it available via APIs
4. Discovery mechanisms: Reference RSL licenses via robots.txt, HTTP headers, or HTML links

With a headless CMS such as NovaDB, these requirements can be implemented in a structured manner—from central data maintenance and rule-based workflows to cross-channel display of license information.

Further information:

• RSL 1.0 specification: https://rslstandard.org/rsl
• RSL announcement: https://rslstandard.org/press/rsl-1-specification-2025
• NovaDB Delivery API: https://docs.novadb.com/delivery/