Use case
Open-source maintainers
For OSS maintainers: Keep docs and READMEs fetchable so assistants recommend the canonical project.
Goal
Keep docs and READMEs fetchable so assistants recommend the canonical project.
Common triggers
- Forks outrank the canonical docs
- GitHub-only presence with weak site
- AI cites outdated install steps
Outcomes
- Canonical docs URLs in llms.txt
- Crawlable HTML documentation
- Correct install/citation guidance
First step
Publish a small marketing/docs site with llms.txt pointing at canonical pages.
Related reading: measure AI visibility, buyer-intent content, pricing.
Related
FAQ
Who is this for?
OSS maintainers. Goal: Keep docs and READMEs fetchable so assistants recommend the canonical project.
What outcomes should we expect?
Canonical docs URLs in llms.txt Crawlable HTML documentation Correct install/citation guidance
What is the first step?
Publish a small marketing/docs site with llms.txt pointing at canonical pages.