The launch-readiness audit

llms.txt: making your app visible to AI search

AI answers from ChatGPT, Claude, and Perplexity are where discovery is moving. An llms.txt file is how they read your site accurately. Learn what Actuant checks and how to write one.

Last updated 2026-07-19

Discovery is shifting from ten blue links to AI answers. This weight-8 check verifies you've published an /llms.txt — a plain-text brief that lets AI crawlers read your site accurately instead of scraping a JavaScript shell.

What Actuant checks

  • /llms.txt responds with real content (more than ~40 characters, not an HTML error page).
  • Present and plausible → pass. Missing → fail ("AI crawlers have no quick brief of your site").
  • Unreachable due to a slow host → partial (retry), never counted as missing.

Two sibling checks complete the AI-visibility category: AI crawlers allowed (weight 4) confirms your robots.txt doesn't block GPTBot and friends, and Readable without JS (weight 5) confirms there is real text in the HTML before JavaScript runs.

Why it matters

Many AI crawlers don't execute JavaScript, so an AI-built SPA looks empty to them. An llms.txt gives them a clean, authoritative summary of what you do, who it's for, pricing, and key pages — the difference between being cited in an answer and being invisible.

How to fix it

Publish a Markdown-flavoured /llms.txt at your site root. Keep it plain and factual.

public/llms.txtmd
# YourApp

> One sentence on what YourApp does and who it's for.

## What it does
- Core capability one
- Core capability two

## Pricing
- Free tier, then $X/mo

## Key pages
- Pricing: https://yourapp.com/pricing
- Docs: https://yourapp.com/docs

On the Launch plan, Actuant drafts your llms.txt from your live site and opens it as a pull request you review and merge.