Agent diagnostics 3 min read  ·  Updated October 2026

Decide whether to publish llms-full.txt

The optional full-text companion was not detected. It earns no points.

maintains Let The Bots In, a technical AI-readiness scanner and reference site.

What does this finding mean?

The report identifies this check as no-llms-full in Agent diagnostics. This diagnostic is outside the six scored categories. This is a category weight, not an automatic deduction for this finding. Read the scan detail for the measured state, overlapping signals and any score cap.

If useful to your documentation readers, publish an accurate full-text rendition with links to canonical sources.

Why does this matter for AI retrieval?

These observations describe optional formats and declared content-use preferences. They earn no score points. Support varies by operator; do not assume every engine reads an optional file or honors an unofficial directive.

How do I check and resolve it?

  1. Decide whether a compact Markdown index would help tools using your documentation. llms.txt is optional and earns no points.
  2. Serve /llms.txt as UTF-8 plain text or Markdown. Start with one H1, a concise blockquote summary and Markdown links grouped under H2 headings.
  3. Use canonical public URLs and check each link. Keep secrets, authentication tokens and private document titles out of the public file.

Adapt the example to the reported issue and the actual route. Placeholder names, URLs and dates must be replaced with facts from your site.

# Actual site name

> A short description of the site and who it helps.

## Documentation

- [Crawler access](https://example.com/guide/): Configure and test public crawler rules.
- [About](https://example.com/about/): Who maintains this site.

Verify the result

Fetch /llms.txt directly. Confirm HTTP 200 and a text body rather than an HTML fallback. Run the validator for format diagnostics; it does not establish adoption by an AI search engine.

Open the related tool or technical guide, then run a new scan of the affected URL. Keep unknown checks marked unknown until you have a complete response.

Copy a prompt for your coding agent

Paste this into Codex, Claude Code or Cursor from your own repository. Include the scan's exact URL and detail so the agent can verify the observation.

Investigate the scanner finding "Decide whether to publish llms-full.txt" (no-llms-full) in this repository.
Observation: The optional full-text companion was not detected. It earns no points.
Required change: If useful to your documentation readers, publish an accurate full-text rendition with links to canonical sources.
Inspect the existing route, shared layouts and configuration first. Confirm the finding against the actual response before editing. Preserve intentional access restrictions, existing content and unrelated changes. Use only factual identity and date values. Make the smallest appropriate fix, verify the deployed HTML or resource response and run the relevant project checks. Explain any measurement that remains unknown. Do not promise search rankings or AI citations.
Reference: https://letthebots.in/fixes/no-llms-full/

Check your site's technical readiness

Scan a public URL for crawler rules, delivered HTML and page metadata. The report distinguishes measured issues from checks it could not complete.

Check my site →