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
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.
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.
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.
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.
Run the check
Press Check or Validate. The file is fetched, split into specification blocks, and scored against the five structural rules.
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.
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.
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.
규격에 명시된 필수 순서
An optional byte-order mark at the very start of the file.
An H1 with the name of the project or site — the only required section.
A blockquote with a short summary containing the key information needed to understand the rest of the file.
Zero or more markdown blocks — paragraphs, lists, tables — of any type except headings.
Zero or more sections delimited by H2 headers, each containing a file list of `- [name](url)` items with optional `: notes`.
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입니다. 필수 항목인 유일한 섹션입니다.
파일의 시작은 단 하나의 `# Your Site Name` 줄로 시작해야 합니다. 이는 사양 중 유일한 필수 항목이며, 정확히 하나만 존재해야 합니다.
인용구 요약 blockquote-summary
나머지 파일 내용을 이해하는 데 필요한 핵심 정보를 담은, 프로젝트의 짧은 요약이 포함된 인용구입니다.
H1 바로 아래에 `> 한 단락 요약`을 배치하세요. 모델이 아래의 모든 링크를 해석할 수 있도록 사이트의 정체성과 주요 타겟층을 명시하세요.
제목 없는 상세 블록 project-details
제목을 제외하고 더 상세한 정보를 담은, 모든 유형(단락, 목록, 표 등)의 0개 이상의 마크다운 섹션입니다.
요약 뒤에 단락, 목록, 표 형식으로 선택적 맥락을 추가하세요. 여기에는 제목을 사용하지 마세요. 파일 내 다음 제목은 첫 번째 H2 섹션이어야 합니다.
파일 목록이 포함된 H2 섹션 file-lists
H2 헤더로 구분되며, 추가 세부 정보를 확인할 수 있는 URL 파일 목록을 포함하는 0개 이상의 마크다운 섹션입니다.
링크는 `## 섹션 이름` 제목 아래에 한 줄당 하나씩 `- [이름](https://absolute-url): 선택적 메모` 형식으로 그룹화하세요. 정확히 `Optional`로 명명된 섹션은 더 짧은 맥락이 필요할 때 생략할 수 있으므로 맨 마지막에 배치하세요.
규정을 준수하는 llms.txt 작성 방법
구현 가이드
파일을 사양 내에 유지하는 6가지 결정
하나의 H1으로 시작하기. 사이트 또는 프로젝트 이름을 사용하세요. (선택 사항인 바이트 순서 마크(BOM) 외에는 그 위에 아무것도 넣지 마세요.) 이는 사양에서 요구하는 유일한 섹션입니다.
인용구 요약 추가하기. H1 바로 아래에 사이트가 무엇을 하는지 설명하는 하나의 `>` 단락을 배치하여, 아래 링크들이 문맥을 가질 수 있도록 하세요.
상세 블록에 제목 넣지 않기. 요약문 뒤에는 추가 단락, 목록 또는 표를 사용할 수 있지만, 첫 번째 H2가 나올 때까지는 제목을 사용하지 마세요.
H2 섹션 아래로 링크 그룹화하기. 모델이 찾을 만한 주제(문서, 가이드, API, 블로그 등)로 섹션 이름을 지정하세요. 이 형식에는 H1과 H2만 존재합니다.
파일 목록 항목을 정확하게 작성하기. `- [페이지 이름](https://example.com/page): 짧은 설명`. 모델이 기본 URL 없이도 해결할 수 있도록 절대 URL을 사용하세요.
'선택 사항(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.
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.
More tools for AI crawlers
Build the file, set crawl rules, and see what AI agents receive from 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
ChatGPT
Claude
Gemini
Perplexity