Maintain declared content-use preferences

What does this finding mean?

The report identifies this check as content-signal-present in Agent diagnostics. This diagnostic is outside the six scored categories. This is a category weight, not an automatic deduction for this finding. Read the scan detail for the measured state, overlapping signals and any score cap.

Keep the declaration consistent with your licensing choices and verify crawl policy separately.

Why does this matter for AI retrieval?

These observations describe optional formats and declared content-use preferences. They earn no score points. Support varies by operator; do not assume every engine reads an optional file or honors an unofficial directive.

How do I check and resolve it?

1. Read the deployed robots.txt and identify whether the directive came from your repository or a CDN-managed section.
2. Choose the actual content-use policy you intend. A stated preference differs from a crawl rule and from an enforceable server block.
3. Change the owning setting or file. Check the live response again because a managed section can be prepended to the file you deploy.

Adapt the example to the reported issue and the actual route. Placeholder names, URLs and dates must be replaced with facts from your site.

Copy code

User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=no
# Non-standard content-use preferences, not an access control.
# Preserve the robots.txt groups that express your crawl policy.

Verify the result

Fetch the live file and compare it with your intended policy. Check the operator documentation before assuming it honors a non-standard preference.

Open the related tool or technical guide, then run a new scan of the affected URL. Keep unknown checks marked unknown until you have a complete response.

Copy a prompt for your coding agent

Paste this into Codex, Claude Code or Cursor from your own repository. Include the scan's exact URL and detail so the agent can verify the observation.

Copy prompt for coding agent

Investigate the scanner finding "Maintain declared content-use preferences" (content-signal-present) in this repository.
Observation: The scanner found Content-Signal declarations. Operator support varies.
Required change: Keep the declaration consistent with your licensing choices and verify crawl policy separately.
Inspect the existing route, shared layouts and configuration first. Confirm the finding against the actual response before editing. Preserve intentional access restrictions, existing content and unrelated changes. Use only factual identity and date values. Make the smallest appropriate fix, verify the deployed HTML or resource response and run the relevant project checks. Explain any measurement that remains unknown. Do not promise search rankings or AI citations.
Reference: https://letthebots.in/fixes/content-signal-present/