add better examples, update title, small restructures

Author: devalog

fern/products/docs/docs.yml

@@ -194,6 +194,7 @@ navigation:
         path: ./pages/seo/redirects.mdx
       - page: llms.txt
         path: ./pages/seo/llms-txt.mdx
+        slug: llms-txt
   - section: Authentication
     collapsed: true
     contents:

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

@@ -1,19 +1,9 @@
 ---
-title: llms.txt
+title: llms.txt and llms-full.txt
 description: Enable tools like Cursor, GitHub Copilot, ChatGPT, and Claude to understand your documentation.
 ---
 
-[llms.txt](https://llmstxt.org/) is a standard for exposing website content to AI developer tools. Fern automatically generates and maintains `llms.txt` and `llms-full.txt` files for your documentation site.
-
-## `llms.txt`
-
-Contains a lightweight summary of your documentation site with each page distilled into a one-sentence description and URL. The format is structured to help AI tools parse and understand your documentation's hierarchy and organization.
-
-`llms.txt` is available at any level of your documentation hierarchy (e.g., `/llms.txt`, `/docs/llms.txt`, `/v1/api-reference/llms.txt`).
-
-When Fern detects an LLM bot accessing your documentation, it automatically serves Markdown instead of HTML, reducing token consumption by 90%+.
-
-See an example: [docs.cohere.com/llms.txt](https://docs.cohere.com/llms.txt)
+[llms.txt](https://llmstxt.org/) is a standard for exposing website content to AI developer tools. Fern automatically generates and maintains `llms.txt` and `llms-full.txt` files for your documentation site. When Fern detects an LLM bot accessing your documentation, it automatically serves Markdown instead of HTML, reducing token consumption by 90%+.
 
 <Frame>
   <img
@@ -23,25 +13,28 @@ See an example: [docs.cohere.com/llms.txt](https://docs.cohere.com/llms.txt)
   />
 </Frame>
 
-## `llms-full.txt`
+## `llms.txt`
 
-Contains complete documentation content including the full text of all pages. For API documentation, this includes your complete API Reference with resolved OpenAPI specifications and SDK code examples for enabled languages. Each API endpoint page includes its full OpenAPI spec.
+Contains a lightweight summary of your documentation site with each page distilled into a one-sentence description and URL. The format is structured to help AI tools parse and understand your documentation's hierarchy and organization.
 
-`llms-full.txt` is available only at the root of your documentation site.
+`llms.txt` is available at any level of your documentation hierarchy (e.g., `/llms.txt`, `/docs/llms.txt`, `/v1/api-reference/llms.txt`).
 
-See an example: [elevenlabs.io/docs/llms-full.txt](https://elevenlabs.io/docs/llms-full.txt)
+Examples from Eleven Labs: 
+- Developer documentation: [elevenlabs.io/docs/llms.txt](https://elevenlabs.io/docs/llms.txt)
+- API Reference (Create speech endpoint): [elevenlabs.io/docs/api-reference/text-to-speech/convert/llms.txt](https://elevenlabs.io/docs/api-reference/text-to-speech/convert/llms.txt)
 
-### Examples
+## `llms-full.txt`
+
+Contains complete documentation content including the full text of all pages. For API documentation, this includes your complete API Reference with resolved OpenAPI specifications and SDK code examples for enabled languages. Each API endpoint page includes its full OpenAPI spec.
 
-View the `llms.txt` files for this site:
+`llms-full.txt` is available only at the root of your documentation site.
 
-- [https://buildwithfern.com/learn/llms.txt](https://buildwithfern.com/learn/llms.txt)
-- [https://buildwithfern.com/learn/llms-full.txt](https://buildwithfern.com/learn/llms-full.txt)
+Example from Cash App: [developers.cash.app/llms-full.txt](https://developers.cash.app/llms-full.txt)
 
 ## Analytics and monitoring
 
 The [Fern Dashboard](https://dashboard.buildwithfern.com/) provides comprehensive analytics for `llms.txt` usage including:
 - Traffic by LLM provider (Claude, ChatGPT, Cursor, etc.)
-- Page-level breakdowns of bot vs. human visitors for `.md` and `llms.txt` files
+- Page-level breakdowns of bot vs. human visitors for Markdown and `llms.txt` files
 
 This visibility helps you understand LLM traffic patterns and optimize your documentation for AI consumption.