Skip to content

Conversation

@roomote
Copy link
Contributor

@roomote roomote bot commented Feb 10, 2026

Related GitHub Issue

N/A -- This is part of an AEO (Answer Engine Optimization) initiative for the marketing site.

Roo Code Task Context (Optional)

Created with Roo Code.

Description

Adds two static files to the marketing site following the llms.txt standard to improve discoverability by AI answer engines (ChatGPT, Perplexity, Claude, Google AI Overviews, etc.):

  • llms.txt -- Concise, structured summary of Roo Code products, integrations, key differentiators, and resource links. This is the file AI crawlers look for first.
  • llms-full.txt -- Comprehensive product information (~4,000 words) covering all products, features, pricing, comparisons vs alternatives (Copilot, Cursor, Windsurf, Cline), and FAQ content.

Both files are placed in apps/web-roo-code/public/ and will be served at roocode.com/llms.txt and roocode.com/llms-full.txt automatically by Next.js.

Key content covered in llms-full.txt:

  • What is Roo Code (overview, key principles)
  • VS Code Extension (features, supported languages, MCP)
  • Roo Code Cloud (how it works, features, agent types)
  • Slack and Linear integrations
  • PR Reviewer and PR Fixer agents
  • Enterprise features
  • Roo Code Router
  • Pricing tiers (Free extension, Cloud Free, Cloud Team, Enterprise)
  • Comparison vs GitHub Copilot, Cursor, Windsurf, and Cline
  • 12 FAQ entries

Test Procedure

  • Verify files exist after build: roocode.com/llms.txt and roocode.com/llms-full.txt
  • Validate Markdown renders correctly in a Markdown viewer
  • Confirm all links point to valid pages
  • No code changes to the app itself -- these are static files in public/

Pre-Submission Checklist

  • Issue Linked: N/A (AEO initiative, no issue)
  • Scope: Changes are focused -- two new static files only
  • Self-Review: Content reviewed against all existing marketing site pages for accuracy
  • Testing: Static files, no functional tests needed
  • Documentation Impact: No documentation updates required
  • Contribution Guidelines: Read and agreed

Screenshots / Videos

N/A -- static text files, no UI changes.

Documentation Updates

  • No documentation updates are required.

Additional Notes

This is the first step in a broader AEO initiative. Future work includes adding FAQPage structured data, a dedicated "What is Roo Code" page, and per-page JSON-LD schemas. The full plan is documented in plans/aeo-optimization-plan.md.

Important

Added llms.txt and llms-full.txt static files to the marketing site for Answer Engine Optimization, providing concise and comprehensive Roo Code product information for AI crawlers.

Related GitHub Issue

N/A -- This is part of an AEO (Answer Engine Optimization) initiative for the marketing site.

Description

Adds two static files to the marketing site following the llms.txt standard to improve discoverability by AI answer engines (ChatGPT, Perplexity, Claude, Google AI Overviews, etc.):

  • llms.txt -- Concise, structured summary of Roo Code products, integrations, key differentiators, and resource links. This is the file AI crawlers look for first.
  • llms-full.txt -- Comprehensive product information (~4,000 words) covering all products, features, pricing, comparisons vs alternatives (Copilot, Cursor, Windsurf, Cline), and FAQ content.
    Both files are placed in apps/web-roo-code/public/ and will be served at roocode.com/llms.txt and roocode.com/llms-full.txt automatically by Next.js.
    Key content covered in llms-full.txt:
  • What is Roo Code (overview, key principles)
  • VS Code Extension (features, supported languages, MCP)
  • Roo Code Cloud (how it works, features, agent types)
  • Slack and Linear integrations
  • PR Reviewer and PR Fixer agents
  • Enterprise features
  • Roo Code Router
  • Pricing tiers (Free extension, Cloud Free, Cloud Team, Enterprise)
  • Comparison vs GitHub Copilot, Cursor, Windsurf, and Cline
  • 12 FAQ entries

Test Procedure

  • Verify files exist after build: roocode.com/llms.txt and roocode.com/llms-full.txt
  • Validate Markdown renders correctly in a Markdown viewer
  • Confirm all links point to valid pages
  • No code changes to the app itself -- these are static files in public/

Additional Notes

This is the first step in a broader AEO initiative. Future work includes adding FAQPage structured data, a dedicated "What is Roo Code" page, and per-page JSON-LD schemas. The full plan is documented in plans/aeo-optimization-plan.md.

This description was created by Ellipsis for 4da1dd8. You can customize this summary. It will automatically update as commits are pushed.

@dosubot dosubot bot added size:L This PR changes 100-499 lines, ignoring generated files. Enhancement New feature or request labels Feb 10, 2026
@roomote
Copy link
Contributor Author

roomote bot commented Feb 10, 2026

Rooviewer Clock   See task

Reviewed the latest changes. The previously flagged MCP description issue has been fixed. No new issues found.

  • Incorrect MCP (Model Context Protocol) description in llms-full.txt -- describes MCP as a way to connect to AI models/providers, but MCP is actually for connecting to external tools and data sources via MCP servers
Previous reviews

Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 10, 2026

🚀 Preview deployed!

Your changes have been deployed to Vercel:

Preview URL: https://roo-code-website-9en4q1cbp-roo-code.vercel.app

This preview will be updated automatically when you push new commits to this PR.

Co-authored-by: roomote[bot] <219738659+roomote[bot]@users.noreply.github.com>
@roomote
Copy link
Contributor Author

roomote bot commented Feb 10, 2026

Fixaroo Clock   See task

No changes needed -- the MCP description fix was already applied in commit 4da1dd8.

View commit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Enhancement New feature or request size:L This PR changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants