feat: value-aware Content Signals Policy evaluation in robots.txt#57
Merged
Conversation
Cloudflare's Content Signals Policy adds a robots.txt `Content-Signal:` directive (search / ai-input / ai-train = yes|no). The ai-crawler-access factor previously awarded a flat +8 for merely declaring one, so a site setting `ai-input=no` — which tells answer engines not to use its content for AI answers (RAG/grounding) — was rewarded for opting out of AEO. Parse the per-User-agent directive and score by value: ai-input=yes +6 / =no -12 (flagged + fix rec), search=yes +2 / =no -6 (flagged + rec), ai-train neutral (blocks training not answers; Cloudflare's own default). The ideal `search=yes, ai-input=yes` still nets +8, so AEO-friendly sites and sites with no directive are unaffected; only restrictive/partial policies shift. Adds 5 finding codes; updates docs, SKILL, CHANGELOG. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cloudflare's Content Signals Policy adds a
robots.txtContent-Signal:directive (search/ai-input/ai-train=yes|no), but theai-crawler-accessfactor previously awarded a flat +8 for merely declaring one — so a site settingai-input=no, which tells answer engines not to use its content for AI answers (RAG/grounding), was rewarded for opting out of AEO. This PR parses the per-User-agentdirective and scores by value:ai-input=yes+6 /=no−12 andsearch=yes+2 /=no−6 (both flagged with fix recommendations), whileai-trainis neutral (it blocks training, not answers, and is Cloudflare's own default). The idealsearch=yes, ai-input=yesstill nets +8, so AEO-friendly sites and sites with no directive are unchanged — only restrictive or partial policies shift. Adds 5 finding codes and 7 tests, updatesdocs/finding-codes.md/SKILL.md/CHANGELOG.md, and bumps to4.2.0(a scoring change; no CLI or output-format change).🤖 Generated with Claude Code