# Content Signals

Category: Agent readiness
Version: 1.0.0

## Goal
Declare AI-usage preferences via Content-Signal directives in robots.txt (ai-train, search, ai-input).

## Issue
The audited site did not satisfy the Content Signals readiness check.

## Fix
Add Content-Signal directives to your robots.txt declaring preferences for ai-train, search, and ai-input. Example: `Content-Signal: ai-train=no, search=yes, ai-input=no`. Pair with explicit User-agent blocks so each signal targets specific bots, and review quarterly as the spec evolves.

## Validation
- Confirm content types, payload shape, and discoverability from the public web surface.
- Verify against fresh public evidence, not only local source changes.
- Re-run the relevant isitready.dev scan before claiming the issue is closed.

## Copyable Fix Prompt
```text
Outcome: make this single public-readiness issue pass for the audited site.

Goal: Content Signals for https://example.com

Issue: The audited site did not satisfy the Content Signals readiness check.

Fix: Add Content-Signal directives to your robots.txt declaring preferences for ai-train, search, and ai-input. Example: `Content-Signal: ai-train=no, search=yes, ai-input=no`. Pair with explicit User-agent blocks so each signal targets specific bots, and review quarterly as the spec evolves.

Skill: /.well-known/agent-skills/content-signals/SKILL.md

Docs: https://blog.cloudflare.com/content-signals-policy/

Validation: Confirm content types, payload shape, and discoverability from the public web surface.

Requirements: preserve existing product behavior, add or update relevant tests, and validate public response shape/content type where applicable.

When done, tell the user to re-run the public scan at https://isitready.dev so they can verify this issue now passes. Do not claim it is fixed until a fresh report confirms.
```