docs: Content Signals in robots.txt for AI content-usage preferences#179
Merged
Conversation
…ots.txt Add docs/robots.txt with a Content-Signal directive (search=yes, ai-input=yes, ai-train=yes) per contentsignals.org / draft-romm-aipref-contentsignals, declaring that this public protocol documentation may be indexed, used to ground AI answers, and used for training. Values mirror the site's existing stance of explicitly allowing all AI crawlers (GPTBot, ClaudeBot, Google-Extended, etc.). Also includes the basic allow rules, AI-crawler allowlist, and sitemap reference so robots.txt is complete on its own (main had none).
juan-malbeclabs
force-pushed
the
content-signals-robots
branch
from
41f5705 to
bea37d7
Compare
Re-apply the Content Signals declaration (search=yes, ai-input=yes, ai-train=yes) per contentsignals.org / draft-romm-aipref-contentsignals. It was dropped when main (which already added robots.txt via #176) was merged into this branch. Values mirror the existing AI-crawler allowlist.
…lls) Add hooks/emit_well_known.py to copy well-known/ into the built site's .well-known/ dir, publishing an MCP Server Card (SEP-1649) and an Agent Skills discovery index (v0.2.0) whose digests are computed at build time. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
armcconnell
approved these changes
Jun 10, 2026
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
2 participants
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.
What
Adds
docs/robots.txtwith a Content Signals directive declaring AI content-usage preferences:Per contentsignals.org / draft-romm-aipref-contentsignals. Addresses the isitagentready.com check "No Content Signals found in robots.txt".
Why these values
The signal values mirror the site's existing demonstrated stance: the AI-crawler allowlist already explicitly permits every training-capable crawler (GPTBot, ClaudeBot, Google-Extended, …). For public protocol documentation we want it indexed (
search), used to ground AI answers (ai-input), and available for training (ai-train). Flip any value tonoto opt out.Notes
mainhad nodocs/robots.txt, so this file is complete on its own (basic allow rules + AI-crawler allowlist + sitemap + Content-Signal).docs/robots.txtverbatim to/robots.txt. Verified locally:mkdocs buildsucceeds andGET /robots.txtreturns200 text/plainwith the directive present.main).ai-agent-ux: that branch also addsdocs/robots.txt. This version is a strict superset of it (same allowlist + sitemap, plus the header comment and Content-Signal block), so any merge conflict resolves by keeping this version.