Analytics and integration

View as Markdown

llms.txt and llms-full.txt are generated automatically for your site, but how readers and AI tools discover them is up to you. Track usage in the Fern Dashboard and surface endpoints directly in your docs.

Track LLM traffic

The Fern Dashboard provides analytics for llms.txt usage including:

  • Traffic by LLM provider (Claude, ChatGPT, Cursor, etc.)
  • Page-level breakdowns of bot vs. human visitors for Markdown and llms.txt files

Surface endpoints to readers

To make endpoints discoverable to human readers, add buttons or navigation links:

Add a button to your SDK docs that links to the llms-full.txt for your API Reference. Use lang to filter code examples to one language, and excludeSpec=true to exclude the raw OpenAPI specification.

Markdown
1<Button href="/api-reference/llms-full.txt?lang=python&excludeSpec=true" target="_blank">
2 Open Python API Reference for LLMs
3</Button>

This gives users a clean, language-specific output they can feed to AI tools when writing code.

Add a dropdown in your navbar that links to different filtered versions of llms-full.txt, making it easy for users to access LLM-optimized documentation for their preferred language.

docs.yml
1navbar-links:
2 - type: dropdown
3 text: LLMs
4 icon: fa-solid fa-robot
5 links:
6 - text: Full docs
7 href: /llms-full.txt
8 - text: Python SDK
9 href: /api-reference/llms-full.txt?lang=python&excludeSpec=true
10 - text: TypeScript SDK
11 href: /api-reference/llms-full.txt?lang=typescript&excludeSpec=true
12 - text: Go SDK
13 href: /api-reference/llms-full.txt?lang=go&excludeSpec=true