Skip to content

Commit 58fca48

Browse files
committed
add info on llms.txt improvements
1 parent 95faf8f commit 58fca48

File tree

1 file changed

+8
-11
lines changed

1 file changed

+8
-11
lines changed

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

Lines changed: 8 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -19,24 +19,21 @@ 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 with OpenAPI specifications and SDK code examples (if generated by Fern).
23-
- **Token efficient**: Removes unnecessary formatting to be as token-efficient as possible.
22+
- **API-ready**: Automatically incorporates your complete API reference with resolved OpenAPI specifications and SDK code examples for all enabled languages. Each API endpoint page includes its full OpenAPI spec.
23+
- **Token efficient**: When Fern detects an LLM bot, it automatically serves markdown content from the llms.txt file, reducing token consumption by 90%+.
2424

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

27-
## Analytics and Monitoring
27+
## Analytics and monitoring
2828

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.
29+
Fern tracks comprehensive analytics for llms.txt usage in the Fern Dashboard, including:
30+
- LLM traffic by provider (Claude, ChatGPT, Cursor, etc.)
31+
- Traffic breakdown for .md and llms.txt files by agents and humans
3032

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.
33+
This visibility helps you understand LLM traffic patterns and optimize your documentation for AI consumption.
3234

33-
## Technical Details
3435

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-
39-
## View in Action
36+
## View in action
4037

4138
Check out the llms.txt files for this site:
4239
- `https://buildwithfern.com/learn/llms.txt`

0 commit comments

Comments
 (0)