Free llms.txt diagnostic

Inspect a deployed llms.txt file and its linked resources

Enter a public hostname to inspect its root-level llms.txt response, title, introduction, sections, links, malformed Markdown, duplicate destinations, and insecure URLs.

The checker treats llms.txt as an emerging optional convention. A present or well-formed file does not prove that any answer engine reads it, prefers it, indexes it, or cites the site.

Public website check Inspectable evidence Clear limitations

Methodology reviewed 2026-08-05

More free checks

Try the other free AI discovery checks

Each check looks at a different layer of AI discovery readiness. Run them together for a fuller picture, or open the complete audit for all of it at once.

Check robots.txt rules for documented AI crawlers

Enter a public hostname to test whether its deployed robots.txt policy allows, blocks, or has no matching restriction for documented AI crawler tokens at the root path.

Check AI crawler rules

Check how clearly your website identifies the business and its entities

Enter a public hostname to compare the visible business name and opening copy with the Organization, WebSite, Person, or SoftwareApplication entities declared in the homepage JSON-LD.

Check structure and identity

Check Recipe structured data on a food publisher page

Enter a public hostname to inspect Recipe entities declared in its homepage JSON-LD and see which of Google’s documented required and recommended Recipe properties were observed.

Check Recipe schema

Build a starting llms.txt file

Fill in a title, short context, and the resource links you want to list, and this page builds a valid llms.txt file for you to review, edit, and publish.

Build llms.txt

Build a starting robots.txt from a declared policy goal

Choose a declared policy goal and this page builds robots.txt groups for the documented AI crawler tokens that goal has an explicit preference for, which you can review, edit, and publish.

Build robots.txt

Build a starting Organization JSON-LD block

Fill in your business name, canonical URL, logo, and official profile links, and this page builds a valid Organization JSON-LD block for you to review, edit, and publish.

Build JSON-LD

AI citation forensics

Paste a prompt and the source an AI answer cited. See which public evidence differs from your site, what is worth testing, and what no external audit can prove.

Compare the evidence

What this check looks for

See the public evidence behind the result

OpenForBots examines the relevant public page or resource, shows what it found, and explains what to review next.

1
Checks the public /llms.txt file at the root of the website.
2
Reports response availability, redirects, content type, and bytes read.
3
Extracts the document title, introductory context, H2 sections, and Markdown links.
4
Identifies malformed link-like lines, duplicate destinations, and insecure HTTP URLs.
5
Separates file quality observations from unsupported ranking or citation claims.

Example evidence result

The file is available but has limited introductory context

The live result uses the deployed page or resource and exact check time. This example shows the evidence structure, not a claim about a real domain.

Observed evidence

Observed source: https://example.com/llms.txt
Document title: found
Resource links: 12
Opportunity: add a concise factual introduction before the resource sections

Recommended next action

Add only accurate, maintained context; keep the file concise; and re-run the check after the deployed response changes.

Understand the result

What the check confirms—and what it cannot tell you

What it can confirm

Whether OpenForBots could retrieve a text response at the convention location.
What supported Markdown structure and links were observed in that response.
Which file-quality issues and improvement opportunities were identified.

What remains unknown

llms.txt is not part of the Robots Exclusion Protocol and does not grant crawler permission.
A missing file is not proof that a website is inaccessible or unready for AI discovery.
A valid file does not guarantee provider support, indexing, ranking, citation, or model use.
The checker reviews file structure and links; it does not certify the factual accuracy of every linked page.

Learn and take action

Related guides and methodology

Don't have an llms.txt yet? Build one

Generate a starting llms.txt from a title, system context, and resource links.

Review the proposal, practical uses, adoption limits, and non-guarantees.

Place llms.txt in the wider access, content, structure, identity, and verification workflow.

Questions about this check

Is llms.txt required for ChatGPT, Claude, Perplexity, or Google AI features?

OpenForBots does not treat it as a universal requirement. Provider support varies and can change, so the checker reports the deployed file without converting the convention into a ranking guarantee.

Does llms.txt replace robots.txt or a sitemap?

No. robots.txt expresses crawler policy, while a sitemap supports URL discovery for systems that consume it. llms.txt is intended as a concise contextual resource index for tools that choose to use it.

Is a missing llms.txt file a critical failure?

No. Missing llms.txt is reported as an optional opportunity, not proof that the site is blocked, uncrawlable, unindexable, or unable to receive citations.