Skip to content

Commit 95faf8f

Browse files
Update llms.txt documentation with analytics and technical details
Co-Authored-By: Devin Logan <[email protected]>
1 parent 6fee06f commit 95faf8f

File tree

1 file changed

+14
-2
lines changed

1 file changed

+14
-2
lines changed

fern/products/docs/pages/seo/llms-txt.mdx

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,11 +19,23 @@ See an example: [docs.cohere.com/llms.txt](https://docs.cohere.com/llms.txt)
1919

2020
### llms-full.txt
2121
- **Comprehensive**: Includes the full content of your documentation.
22-
- **API-Ready**: Automatically incorporates your full API reference and SDK snippets (if generated by Fern).
22+
- **API-Ready**: Automatically incorporates your full API reference with OpenAPI specifications and SDK code examples (if generated by Fern).
2323
- **Token efficient**: Removes unnecessary formatting to be as token-efficient as possible.
2424

2525
See an example: [docs.cohere.com/llms-full.txt](https://docs.cohere.com/llms-full.txt)
2626

27+
## Analytics and Monitoring
28+
29+
Fern tracks comprehensive analytics for llms.txt usage to help you understand how AI tools are consuming your documentation. The system monitors performance metrics including load times, processing times, and content length. User agent detection automatically identifies bot traffic versus browser requests, and detailed logging captures request headers for deeper insights.
30+
31+
These analytics are available in the Fern dashboard, where you can view dedicated tables for llms.txt and markdown file access, along with channel attribution and device type information. This visibility helps you understand LLM traffic patterns and optimize your documentation for AI consumption.
32+
33+
## Technical Details
34+
35+
The llms.txt generation system handles complex schema types including self-referencing schemas, preventing infinite recursion during content generation. For large documentation sites, the system uses optimized timeouts to ensure reliable content delivery without timing out.
36+
37+
For REST API endpoints, the markdown generation includes OpenAPI specifications in YAML format, making it easy for LLMs to understand your API structure. The same markdown generation logic is used for both serving llms.txt files and indexing content for search, ensuring consistency across your documentation platform.
38+
2739
## View in Action
2840

2941
Check out the llms.txt files for this site:
@@ -36,4 +48,4 @@ Check out the llms.txt files for this site:
3648
alt="Example of using llms.txt"
3749
className="rounded-lg border border-gray-200 dark:border-gray-700"
3850
/>
39-
</Frame>
51+
</Frame>

0 commit comments

Comments
 (0)