# Content Signals Policy vs AIPREF Vocabulary

The map lists them as complementary: sites and agents commonly implement both.

[3 Permit](/category/permit/) [Content Signals Policy](/protocols/cloudflare-content-signals-policy/) · [3 Permit](/category/permit/) [AIPREF Vocabulary](/protocols/aipref-vocabulary/)

|  | [Content Signals Policy](/protocols/cloudflare-content-signals-policy/) | [AIPREF Vocabulary](/protocols/aipref-vocabulary/) AIPREF |
| --- | --- | --- |
| Lifecycle step | 3 Permit: What may the agent do here? | 3 Permit: What may the agent do here? |
| Answers | May content fetched under a robots.txt allow rule also be used for search indexing, as live input to an AI answer, or for AI model training? | What controlled set of values expresses a publisher's AI-use preferences, independent of how they are attached to content? |
| Governed by | Cloudflare, developed with publisher/platform partners named in the announcement (e.g. Condé Nast, News/Media Alliance, Reddit, Pinterest, Quora, Yahoo) | IETF AI Preferences Working Group (ai-control@ietf.org mailing list) |
| Status (issuer's words) | Vendor-published policy convention layered on robots.txt; not submitted to a standards body as of this verification | Internet-Draft, work in progress; explicitly states its contents 'DO NOT REFLECT CONSENSUS of the Working Group' |
| Phase | living | working group |
| Version | Announced 2025-09-24 (2025-09-24) | draft-ietf-aipref-vocab-08 (2026-09-14) |
| Form / transport | well-known file | document format |
| Found at | /robots.txt | Not independently discoverable; values are carried by the Content-Usage attachment mechanism (robots.txt directive or HTTP header) |
| Adoption | unmeasured | unmeasured |
| Evidence | 5 verified | 2 verified, 1 reported |
| Primary use case | Control AI crawling and training use | Control AI crawling and training use |
| Last verified | 2026-10-19 (current) | 2026-10-18 (current) |
| Specification | [https://blog.cloudflare.com/content-signals-policy/](https://blog.cloudflare.com/content-signals-policy/) | [https://datatracker.ietf.org/doc/html/draft-ietf-aipref-vocab-08](https://datatracker.ietf.org/doc/html/draft-ietf-aipref-vocab-08) |

## When to use which

- Choose Content Signals Policy when your question is “May content fetched under a robots.txt allow rule also be used for search indexing, as live input to an AI answer, or for AI model training?” and you accept its maturity: phase living, adoption unmeasured.
- Choose AIPREF Vocabulary when your question is “What controlled set of values expresses a publisher's AI-use preferences, independent of how they are attached to content?” and you accept its maturity: phase working group, adoption unmeasured.

Guidance is derived from the two records (question, phase, adoption, prerequisites, pairings), not from opinion. Each record's page carries its numbered references.

## Read the full articles

- [Content Signals Policy](/protocols/cloudflare-content-signals-policy/): May content fetched under a robots.txt allow rule also be used for search indexing, as live input to an AI answer, or for AI model training?
- [AIPREF Vocabulary](/protocols/aipref-vocabulary/): What controlled set of values expresses a publisher's AI-use preferences, independent of how they are attached to content?

Ask the MCP server to compare any two: the compare-protocols prompt, or get on both ids. [Connect](/connect/).

[cloudflare-content-signals-policy.json](/data/protocols/cloudflare-content-signals-policy.json) · [aipref-vocabulary.json](/data/protocols/aipref-vocabulary.json) · [Markdown](/compare/cloudflare-content-signals-policy-vs-aipref-vocabulary/index.md)