Skip to content
Leadee
Not translated yet.This page is not available in Español yet, so you are reading the English version.Open the English page
Technical readiness

llms.txt: The Correct Format, Common Errors, and How Much It Actually Matters

By the Leadee team at Netbase JSC · Updated

llms.txt is a plain-text file at your site root, in Markdown, that lists your key pages in one place for an AI agent to read instead of crawling your whole site. The format needs an H1 title, a one-line blockquote summary, and one or more "## Section" headings each holding a list of `[title](url): description` links. It is easy to get right and, by independent measurement, has no proven effect on whether AI engines cite you.

Key facts

  • In a study of nearly 300,000 domains, only 10.13% had an llms.txt file, and researchers found no correlation between having one and how often AI engines cited the domain — removing the llms.txt variable from their prediction model made it more accurate, not less. (SE Ranking, 2026)
  • Google's own AI optimization guide says plainly that "Google Search itself doesn't use" llms.txt files, and that creating one will "neither harm nor help your site's visibility or rankings in Google Search, as Google Search ignores them." (Google Search Central, 2026)
  • OpenAI's, Anthropic's and Perplexity's own crawler documentation describes robots.txt and sitemaps as the ways to control and guide their bots; none of the major AI vendors has published a commitment to read or weight llms.txt in how they decide what to cite. (OpenAI, 2026)
  • Leadee's own check validates llms.txt against the documented llmstxt.org format (H1, summary blockquote, link sections) and reports the exact line that is malformed, not just a pass/fail — see the AI crawlability check.

What does a valid llms.txt file look like?

The llmstxt.org format has one required element — an H1 heading naming your site or company as the very first line — and a conventional shape around it: a one-line blockquote summary right after the H1, optional free-text paragraphs, then one or more `## Section Name` headings, each followed by a bullet list of links in the exact form `- Link title: optional description`.

A section literally named `## Optional` is a convention from the spec itself: it marks links an AI agent working with a short context window is free to skip, as opposed to the core sections above it.

  • `# Acme Manufacturing` — the required H1, your company or site name, nothing else on that line.
  • `> Acme makes precision-machined aluminium brackets for the aerospace and automotive industries.` — the one-line summary.
  • `## Products` followed by `- Aerospace brackets: CNC-machined to AS9100 spec` — a section with one correctly formatted link.
  • `## Optional` followed by `- Careers` — secondary links an agent can skip under context pressure.

What are the most common llms.txt errors?

Leadee's checker parses the file the same way an AI agent's parser would, and reports a specific problem string for each thing it finds wrong — these are the exact messages you will see in a scan result, not a paraphrase.

  • "missing H1 title — the file must start with '# Site Name'" — the very first non-blank line was not a single `#` heading; a blank line or a `##` section before the H1 triggers this.
  • "missing summary blockquote ('> one-line description') after the H1" — no `>` blockquote line directly follows the title.
  • "no '## Section' with a link list found" — the file has an H1 and maybe prose, but never a `##` heading at all.
  • "malformed link under '<section name>' — expected '- title: description'" — a line under a section starts with `-` but is not a real Markdown link, often a plain bullet of plain text or a link missing its closing `)`.
  • "section(s) found but no valid links in any of them" — every `##` section is empty or every line under it failed to parse as a link.

What is llms-full.txt, and do I need it?

llms-full.txt is the same idea at a larger scale: instead of a short index of links, it is the full text an agent would need — summaries, key facts, sometimes entire page bodies — all in one file, so an agent with a large context window can read your whole site's substance without a single additional fetch.

Leadee's check gives a small score bump for having both files rather than just llms.txt, on the reasoning that a richer file costs nothing extra to maintain once the short one exists and some agents do prefer reading one consolidated document over following many links.

Does llms.txt actually affect whether AI engines cite you?

Honestly, the best independent measurement available says no, not meaningfully. SE Ranking's study of close to 300,000 domains found adoption sitting around 10% regardless of how much traffic a site gets, and no statistical link between having the file and how often a domain gets cited in AI answers — removing llms.txt from their citation-prediction model made the model more accurate, which is the opposite of what you would expect from a lever that matters.

That does not make llms.txt harmful or pointless to add — it costs almost nothing to create and keep current, and no major AI vendor has published a commitment either way about future weight. Leadee scores it as a low-severity check for exactly this reason: fix it, but fix crawler access, schema markup and real citability first — see AI crawlers and robots.txt and schema markup for B2B.

Does Google use llms.txt for ranking or AI Overviews?

No, and Google has said so directly rather than leaving it ambiguous. Google's own AI optimization guide states that "Google Search itself doesn't use" llms.txt, and that adding one will "neither harm nor help your site's visibility or rankings in Google Search, as Google Search ignores them." That covers both classic Search and Google's AI features — neither reads the file as a ranking or citation input.

Ordinary, well-understood fundamentals — crawlable HTML, structured data, a current sitemap — are what Google points site owners back toward instead. That lines up with the rest of this page: llms.txt is a low-cost, low-risk file to maintain, but it is not where a site's AI-visibility budget belongs.

Questions

Is llms.txt the same thing as robots.txt?

No. robots.txt tells crawlers which paths they may or may not fetch; llms.txt is a curated, human-and-agent-readable index of your key pages. A site needs both for different jobs — see [AI crawlers and robots.txt](/learn/ai-crawlers-robots-txt) for the crawler-access side.

Has any major AI vendor confirmed it reads llms.txt?

Not that Leadee has found documented anywhere. Google has stated the opposite outright for Search and its AI features; OpenAI, Anthropic and Perplexity document robots.txt and sitemaps as their crawler-control mechanisms and are silent on llms.txt specifically.

What's the single most common mistake in an llms.txt file?

A missing or malformed H1 on the very first line — a blank line, a byte-order mark, or starting straight with a `##` section before the title all trip the "missing H1 title" error.

Should I generate llms.txt automatically from my sitemap?

You can, but curate it rather than dumping every URL — the format's whole point is a short, prioritised list an agent reads quickly, closer to a table of contents than a full site index.

If llms.txt barely matters, why does Leadee check for it at all?

Because some agents do read it, it costs almost nothing to get right, and a malformed file is a quick, free fix — it just should not be where you spend your first hour of effort.

Do I need to update llms.txt every time I publish a new page?

Only for pages important enough to belong in a short curated index — new blog posts rarely qualify, new product or service lines usually do.

Can GEO guarantee results?

No. AI answer engines change their output frequently, and no vendor — including Leadee — can guarantee a ranking or a mention. Leadee publishes confidence intervals on every metric so you can see how much a result can vary run to run.

How does Leadee measure AI visibility?

Leadee runs your prompt set against each AI engine on a weekly to daily schedule, depending on plan, through official vendor APIs (OpenAI, Gemini, Perplexity, Anthropic, DataForSEO) — never by scraping consumer chat interfaces — and reports mention rate, citation rate, average position, share of voice and sentiment with a 95% confidence interval.

Who do I talk to?

Email [email protected] or use Talk to an expert at https://leadee.ai/contact-sales — the Netbase JSC team behind Leadee replies by email or WhatsApp — or WhatsApp the CEO directly at https://wa.me/84937869689.

Check your llms.txt for real format errors

Run the free check to see the exact line your llms.txt breaks on, then get it fixed alongside the checks that matter more.