Skip to content

fix: withhold AI training consent in robots.txt - #1406

Closed
cblanc wants to merge 1 commit into
mainfrom
aeo-signals-no-train
Closed

cblanc wants to merge 1 commit into
mainfrom
aeo-signals-no-train

Conversation

@cblanc

@cblanc cblanc commented Sep 29, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Switch the robots.txt signal to Content-Signal: search=yes, ai-input=yes, ai-train=no: search indexing and AI grounding stay allowed, AI training is refused.
  • Add Cloudflare's standard content-signals notice above the group. It defines the signals and states that a no is an express reservation of rights under Article 4 of EU Directive 2019/790.
  • static/robots.txt and the committed build/robots.txt stay byte-identical.

Test plan

  • pnpm build && PORT=8881 node dist/server.js
  • curl -si localhost:8881/robots.txt: 200 text/plain, ai-train=no under User-agent: *

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@cblanc

cblanc commented Sep 29, 2026

Copy link
Copy Markdown
Member Author

Not needed: postcodes.io keeps ai-train=yes (open data), as shipped in #1405.

@cblanc cblanc closed this Sep 29, 2026
@cblanc
cblanc deleted the aeo-signals-no-train branch September 29, 2026 08:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant