Add explicit AI crawler rules to robots.txt#1335
Draft
IEvangelist wants to merge 1 commit into
Draft
Conversation
Add per-agent User-agent groups for major AI/LLM crawlers (OpenAI, Anthropic, Google, Perplexity, Apple, Amazon, Meta, Mistral, DuckDuckGo, Cohere, Common Crawl) that explicitly Allow: / and carry the existing Content-Signal (ai-train=yes, search=yes, ai-input=yes), while preserving the wildcard default group and the sitemap reference. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
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
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 explicit AI / LLM crawler rules to
src/frontend/public/robots.txtsohttps://aspire.dev/robots.txtstates our stance per user-agent instead of relying only on the wildcard group.Why
The recommended "AI crawler rules" practice is to declare explicit
User-agentgroups for AI crawlers (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, …) so allow/disallow decisions are on our terms rather than left implicit. Aspire already opts into AI use viaContent-Signal: ai-train=yes, search=yes, ai-input=yes, ships anllms.txt, agent skills, and an MCP server — so this change makes that intent explicit and machine-readable for each major AI agent.What changed
Content-Signalthe site already declares:GPTBot,OAI-SearchBot,ChatGPT-UserClaudeBot,Claude-User,Claude-SearchBot,anthropic-aiGoogle-ExtendedPerplexityBot,Perplexity-UserApplebot-ExtendedAmazonbot; Meta:Meta-ExternalAgent; Mistral:MistralAI-User; DuckDuckGo:DuckAssistBot; Cohere:cohere-ai; Common Crawl:CCBotUser-agent: *) default group, itsContent-Signal, and theSitemap:reference.Allowing (rather than blocking) these agents is intentional and consistent with the site's existing
ai-train=yes/search=yes/ai-input=yessignals — Aspire wants to be discoverable by AI assistants. Flip any group toDisallow: /later if the policy changes.Verification
robots.txtlives in Astro'spublic/dir, so it's copied verbatim to the site root (/robots.txt) with no transform. Validated the file with Python'surllib.robotparser:GPTBot,ClaudeBot,CCBot, and an arbitrary UA all resolve tocan_fetch = TrueSitemapis parsed:https://aspire.dev/sitemap-index.xml