Knowledge base/ExtractabilityAUTO

llms.txt lists key pages with descriptions

An llms.txt that exists is good. An llms.txt with clear page descriptions is much better.

What separates a good llms.txt from a bad one

A bad llms.txt is a bare list of URLs, or worse, a dump of your entire site. It does not help the model prioritize. A good llms.txt is a curated selection of your most important pages, grouped by topic, each with a short description explaining what the model will find there.

Think of it as a human-edited sitemap. The value is in the editing.

Structure that works

# Acme CRM

> Lightweight CRM for small sales teams. Built for teams of 2 to 20 people.

## Getting started
- [Quickstart](https://docs.acmecrm.com/start): Sign up and import your contacts in 5 minutes.
- [Video walkthrough](https://acmecrm.com/demo): Five-minute tour of the product.

## Core features
- [Pipeline](https://acmecrm.com/features/pipeline): Visual drag-and-drop pipeline for deals.
- [Email sync](https://acmecrm.com/features/email): Gmail and Outlook integration.
- [Reports](https://acmecrm.com/features/reports): Revenue and activity reporting.

## Pricing and plans
- [Pricing](https://acmecrm.com/pricing): Free, Pro ($12/user), and Enterprise tiers.

Rules

  • Start with a one-line summary as a blockquote.
  • Group pages under topical H2 headings.
  • Each entry is a link followed by a colon and a one-sentence description.
  • Include at most 30 or 40 links. Fewer is better.
  • Keep it current — out-of-date entries hurt more than missing ones.