Skip to content

llms.txt チェッカー

A free llms.txt validator. Check a live URL or paste a draft, and the checker parses the file against the llmstxt.org specification: H1 title, blockquote summary, detail blocks and H2 link lists. You get a score out of 100, a grade, and the exact lines to fix.

Free · no sign-up · URL or pasted content

A bare domain works — we add https:// and look for /llms.txt and /llms-full.txt at the site root.

What is an llms.txt checker?

An llms.txt checker is a tool that tests whether an llms.txt file follows the llmstxt.org specification. This free validator fetches the file from your site, or reads a draft you paste, and checks five rules: Markdown format, one H1 title, a blockquote summary, heading-free detail blocks and H2 link lists. It returns a score out of 100, a grade and line-by-line fixes, with no sign-up.

The five rules the validator checks

Each rule maps to a requirement in the llmstxt.org specification. Every finding is marked as an error, a warning or a note.

Markdown format

The file is plain markdown that parses cleanly, with nothing the spec doesn't allow.

H1 title

Exactly one H1 with the site or project name, at the top. It is the only required section.

Blockquote summary

A short > summary directly under the H1, so the links that follow have context.

Detail blocks

Optional paragraphs or lists after the summary, with no headings before the first H2.

H2 file lists

Each H2 section holds - [name](url): note items, and a section named Optional comes last.

Score, grade and preview

Generate a file

A 0 to 100 score with an A to F grade, findings grouped by severity, and a rendered preview of the file.

How to validate an llms.txt file

Check, fix, publish, and check again.

  1. Pick an input mode

    Choose Check by URL to validate a file that is already live, or Paste content to validate a draft before you publish it.

  2. Enter your URL or file

    Type a bare domain, a site root, or a direct /llms.txt URL — the protocol is added for you. In paste mode, drop the full markdown into the text box.

  3. Run the check

    Press Check or Validate. The file is fetched, split into specification blocks, and scored against the five structural rules.

  4. Read the score and grade

    The score ring shows weighted compliance out of 100 with a letter grade, plus how many rules passed, warned, or failed.

  5. Work through the findings

    Each finding names the rule, the line number, and the exact change to make. Expand a rule card to see every detail behind its status.

  6. Fix, publish, and re-check

    Apply the fixes, upload the file to your site root so it is served at yourdomain.com/llms.txt, then run the URL back through the checker to confirm it passes.

How to read the llms.txt report

Start with the errors, then the warnings. Notes are suggestions, not failures.

Score and grade

A weighted score from 0 to 100 with a letter grade from A to F. Each of the five rules carries part of the weight.

Passed, warned, failed

How many of the five rules the file passes outright, passes with warnings, or fails.

Errors

Breaks the specification, such as a missing H1 or link lines that aren't list items. Fix these first.

Warnings

Allowed but likely to confuse a parser, such as a missing summary or an Optional section that isn't last.

Line numbers

Each finding points at the line to change, so you can fix the file in any text editor.

Preview

A rendered view of the title, summary and link sections, the way a program would read them.

llms.txtとは何ですか?

llms.txt is a markdown file published at the root of a website — yourdomain.com/llms.txt — that gives large language models a short, curated map of the site. Instead of asking a model to crawl navigation, scripts and boilerplate, the file hands it a title, a summary and a list of the pages that actually matter.

The format is defined by the specification at llmstxt.org. It is deliberately small: only H1 and H2 headings exist, and the body of each section is a list of links. That constraint is what makes the file both human-readable and trivially parseable by a program.

The spec also describes a companion convention, /llms-full.txt, which contains the expanded content itself rather than an index of links.

仕様に基づく必須の順序

  1. An optional byte-order mark at the very start of the file.
  2. An H1 with the name of the project or site — the only required section.
  3. A blockquote with a short summary containing the key information needed to understand the rest of the file.
  4. Zero or more markdown blocks — paragraphs, lists, tables — of any type except headings.
  5. Zero or more sections delimited by H2 headers, each containing a file list of `- [name](url)` items with optional `: notes`.
  6. A section named exactly “Optional” has special meaning: its URLs may be skipped when a shorter context is needed.

確認する5つの検証ルール

すべてのチェックはllmstxt.orgの仕様書の条項に直接対応しています。各ルールにスコアが付けられ、重み付けされた 合計がコンプライアンススコアおよびアルファベット評価になります。

マークダウン形式 markdown-format

ファイルはマークダウン形式である必要があり、フォーマット内にはH1およびH2見出しのみが存在します。

/llms.txtではプレーンなマークダウンを提供します。HTML、YAMLフロントマター、H3〜H6見出しは使用しないでください。H2より下位の見出しは仕様外となります。

H1 プロジェクトタイトル h1-title

プロジェクト名またはサイト名を設定したH1。これは必須の唯一のセクションです。

ファイルの先頭に単一の `# サイト名` 行を配置します。これは仕様の中で必須となる部分であり、ファイル内に正確に1つだけ存在する必要があります。

引用の要約 blockquote-summary

プロジェクトの短い要約を含む引用ブロック。残りのファイルを理解するために必要な重要な情報が含まれています。

H1の直下に `> 1段落の要約` を配置します。モデルがその下にあるすべてのリンクを解釈できるように、サイトの概要と対象ユーザーを記述してください。

見出しのない詳細ブロック project-details

見出しを除く、より詳細な情報を含む任意のタイプの0個以上のマークダウンセクション(段落、リスト、テーブルなど)。

要約の後に、段落、リスト、テーブルとして任意のコンテキストを追加します。ここでは見出しを使用しないでください。ファイル内の次の見出しは、最初のH2セクションにする必要があります。

ファイルリスト付きのH2セクション file-lists

H2ヘッダーで区切られた0個以上のマークダウンセクション。詳細情報が記載されているURLのファイルリストが含まれています。

`## セクション名`の見出しの下にリンクをグループ化し、1行につき1つのリンクを `- [名前](https://absolute-url): 任意のメモ` の形式で記載します。正確に `Optional` という名前のセクションは、より短いコンテキストが必要な場合にスキップできるため、常に最後に配置してください。

準拠したllms.txtの書き方

実装ガイド

仕様に準拠し続けるための6つの重要な判断

  1. H1見出しは1つだけにする. サイト名またはプロジェクト名を使用します。その上にはオプションのBOM(バイト順マーク)以外何も置かないでください。これは仕様で必須とされる唯一のセクションです。
  2. 引用による概要を追加する. H1の直下に、サイトの内容を説明する`>`段落を1つ配置し、下部のリンクに文脈を持たせます。
  3. 詳細ブロックには見出しを使わない. 概要の後に、追加の段落、リスト、表を配置することは許可されていますが、最初のH2までは見出しを使用しないでください。
  4. H2セクションの下にリンクをグループ化する. AIモデルが探すもの(ドキュメント、ガイド、API、ブログなど)に合わせてセクションに名前を付けます。このフォーマットで使用できるのはH1とH2のみです。
  5. ファイルリスト項目を正確に記述する. `- [ページ名](https://example.com/page): 簡単な説明`。AIモデルがベースURLなしで解決できるように、絶対URLを使用してください。
  6. 「任意(Optional)」は最後に配置する. 「Optional」という正確なタイトルのセクションは、より短いコンテキストが必要な場合に省略できます。二次的なページ用にとっておき、末尾に配置してください。

仕様テンプレート

llmstxt.orgで公開されている標準的なサンプル — コピーしてご自身の値を入力してください。

# Title

> Optional description goes here

Optional details go here

## Section name

- [Link title](https://link_url): Optional link details

## Optional

- [Link title](https://link_url)

· Save it as llms.txt and upload it to your site root so it is served at yourdomain.com/llms.txt, then run it back through this checker.

The specification this checker follows is published and maintained at llmstxt.org.

What this llms.txt validator doesn't do

  • It checks structure against the specification, not whether the pages you list are your best ones or still load.
  • It doesn't fix the file for you; each finding says what to change.
  • A perfect score doesn't mean AI engines will read the file or cite you. llms.txt is a voluntary convention.
  • In URL mode it reads what your server returns at /llms.txt. If a firewall or bot protection blocks the request, paste the file instead.

Questions about llms.txt

Something else? Ask the team

What is llms.txt?

llms.txt is a markdown file published at the root of a website that gives large language models a short, curated map of the site. The specification at llmstxt.org defines its structure: an H1 with the project or site name, a blockquote summary, optional heading-free detail blocks, and H2 sections containing file lists of the form - [name](url): optional notes.

Where does the llms.txt file have to be located?

At the root of your domain, served at yourdomain.com/llms.txt. The specification also describes a companion file, /llms-full.txt, which holds the expanded content itself instead of an index of links. This checker looks for both when you validate by URL.

What does this llms.txt checker validate?

Five structural rules drawn from the specification: that the file is markdown using only H1 and H2 headings, that it opens with a single H1 project title, that a blockquote summary follows it, that any further detail blocks contain no headings, and that each H2 section contains a file list of link items. Each rule is weighted, and the total becomes a score out of 100 with a letter grade.

Is the blockquote summary required in llms.txt?

The H1 with the project name is the only section the specification marks as required. The blockquote summary is described as part of the expected structure and carries the key information needed to understand the rest of the file, so this checker treats a missing summary as a problem worth fixing rather than a hard failure of the format.

What does the Optional section mean in llms.txt?

A section named exactly Optional has special meaning in the specification: the URLs listed under it may be skipped when a shorter context is needed. Use it for secondary pages such as contact, legal and policy pages, and keep it as the last section in the file.

What is the difference between llms.txt and llms-full.txt?

llms.txt is a compact index — a title, a summary, and lists of links to the pages that matter. llms-full.txt is the companion convention that contains the full content itself in one file, for cases where a model should read the material rather than follow links to it.

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

No. robots.txt tells crawlers what they are allowed to fetch and a sitemap lists every indexable URL. llms.txt does neither — it is a curated summary that tells a language model which content is worth reading and how the site fits together. They serve different purposes and can all coexist at the site root.

Do I need an account to use this llms.txt checker?

No. The checker is free and requires no sign-up. You can validate a live URL or paste the contents of a draft file, and the results are returned to you without being published anywhere.

How do I validate an llms.txt file?

Enter your site address (the checker fetches /llms.txt) or paste the file's contents, then run the check. Fix each error and warning it lists, publish the file at your site root, and run the check again until the score is where you want it.

Is this llms.txt validator free?

Yes. The checker is free and needs no account. It works on a live URL or on pasted content, so you can test a draft before you publish it.

See whether AI engines use your pages

A valid llms.txt is a map. AI Rank Lab shows whether ChatGPT, Claude, Gemini, Perplexity and Google's AI answers actually mention and cite you.

Brand Visibility

Run the prompts your buyers ask on six AI engines and record whether your brand is mentioned, where, in what tone, and which URLs are cited. Every run is stored so you can compare over time.

  • ChatGPT, Claude, Gemini, Perplexity, AI Overviews and AI Mode
  • Mentions, position, sentiment and cited URLs
  • Runs when you choose, stored for comparison
See brand visibility
fieldnote.app4,571 credits

Brand Visibility

12 prompts · last run

Illustrative data
Mentioned in answersshare of prompts
  • ChatGPT42%
  • Claude35%
  • Gemini28%
  • Perplexity51%
  • AI Overviews22%
  • AI Mode19%

Runs when you choose to run it. Every run is stored so you can compare over time.

See where you stand in search and AI

Paste your site. The free audit scores it for SEO, answer engines and generative engines, with the fixes.