chore(seo): disallow /mcp in production robots#27
Merged
Conversation
/mcp is the separate mcp-catalog stack (agentage.io/mcp). Keep it out of the index until the catalog has real content. Dev stays blanket-noindex.
|
✅ CI - Verify PASSED Commit:
|
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.
Add
/mcpto the productiondisallowlist inpackages/landing/src/app/robots.ts.Why
agentage.io/mcpis served by the new mcp-catalog stack (a separate repo/Swarm stack, routed by TraefikPathPrefix(/mcp)), currently a placeholder scaffold. landing ownsagentage.io/robots.txt, so the disallow has to live here. This keeps/mcpout of the search index until the catalog has real content.Change
const disallow = ['/api/', '/dashboard/']->[..., '/mcp'](prod/indexable branch only). The dev branch already returns a blanketDisallow: /, so dev is unaffected.Verify
agentage.io/robots.txt) gainsDisallow: /mcpfor*and the AI bots.seo.spec.tsonly asserts the non-prod blanket-disallow, so no test change needed.