Top Citation Signal

Getting cited

Does llms.txt actually help AI visibility?

Short answer
Barely, on current evidence. Around 9–10% of major sites publish an llms.txt, but monitoring of AI crawler traffic shows the file is almost never requested — GPTBot, ClaudeBot, PerplexityBot and Google-Extended overwhelmingly crawl HTML directly. No major AI company has committed to reading it, and Google has said it does not support it.

Why publish one anyway

The cost is close to zero and the downside is nil. If a standard for agent-readable site summaries does consolidate, having one already in place costs nothing extra.

It is also genuinely useful as a forcing function. Writing a clean, one-page description of what your site is and which pages matter most tends to expose that your actual pages do not say it that clearly.

What to do instead

Everything llms.txt promises — clear structure, extractable answers, an obvious hierarchy — is better delivered in the HTML the crawlers actually fetch. Spend the effort there first.

Treat llms.txt as a cheap hedge, not a strategy. Any advice that positions it as a primary lever for AI visibility is running ahead of the evidence.

See where you actually stand

We ask AI engines the questions your buyers ask and show you whether you were named, who was named instead, and which sources they cited. Free.

Run my free AI Visibility Snapshot

Related questions

Should I block AI crawlers in robots.txt?

Not if you want to appear in AI answers. Blocking GPTBot, ClaudeBot, PerplexityBot, or Google-Extended removes your pages from the retrieval pool those engines draw on, which removes you from the answers. Blocking is a defensible choice for publishers protecting licensable archives, and a self-inflicted wound for almost everyone else.

Does schema markup help with AI search visibility?

Indirectly, yes. No major AI engine has confirmed that structured data is a ranking input, but schema makes a page's facts unambiguous — what it is, who published it, what it is about, and which entities it refers to. That resolves the reconciliation problem engines face, and unambiguous pages get misread less often.

Do AI engines read JavaScript-rendered content?

Mostly no. Google renders JavaScript for its own index, but the crawlers used by ChatGPT, Perplexity, and Claude generally fetch raw HTML and do not execute JavaScript. Content that only exists after client-side rendering is invisible to them, even when it is perfectly visible to a human in a browser.

More on getting cited

All answersGlossaryHow we measure

Last reviewed 2026-07-30.