What is a Content-Signal line in robots.txt?
We search the robots.txt we already fetched for a Content-Signal directive.
What it is
A Content-Signal line extends robots.txt from access to purpose. It states your position on 3 uses separately: search indexing, ai-input for answering a question now, and ai-train for training a model.
The syntax is a comment-style directive alongside your existing groups, with `yes` or `no` per use. `Content-Signal: search=yes, ai-input=yes, ai-train=no` is a common position.
It is a declaration of preference, not an enforcement mechanism. We record whether the directive is present, and we do not judge the values you chose.
Why an agent needs it
Access and use are different questions. `Allow: /` says a crawler may fetch the page and says nothing about whether the content may be used to train a model.
Stating the distinction yourself is better than leaving each client to assume. It is also the position you would want on record if the assumption were ever disputed.
The Fix
Add a Content-Signal line to your robots.txt stating search, ai-input and ai-train separately. Decide each one deliberately rather than copying a default.
Most businesses want to be found and quoted, and are less comfortable being trained on. That position is `search=yes, ai-input=yes, ai-train=no`.
Keep it consistent with your named agent groups and your edge rules. 3 places stating 3 different positions is worse than one clear line.
This one is a change in your own markup or edge configuration, so the Fix Pack cannot write it for you. A Report names every page it affects, with the Evidence.