LLMs.txt Checker

Check llms.txt in 30 seconds

AI content discovery file check — enter your domain or paste llms.txt content, get pass/warn/fail rules and a fix checklist.

View sample report

What you get from an llms.txt check for AI content optimization

Domain presence check

Fetch /llms.txt from any public domain — a common AI content discovery signal — and see whether the file exists with readable content

Structure validation

Pass, warn, and fail rules for H1 title, sections, Markdown links, Last-Updated, and auth boundaries

Content preview

Review the first lines of the fetched or pasted file alongside each finding

Continue in Site Audit

llms.txt is one technical signal — sign in for pillar scores across technical, schema, content, and more. Part of the gptmelo AI content toolset — pair with Site Audit for full AI crawler readiness scoring.

How it works

Our free llms.txt checker fetches or accepts pasted content and returns a structure score in under a minute.

01
Enter a domain or paste llms.txt
Fetch /llms.txt from any public domain — or paste file content directly. No signup required to preview.
02
We validate structure
Check H1 title, blockquote lede, public page links, Last-Updated, and auth-boundary rules for AI discovery.
03
View your preview report
See your score, pass and warn checklist rows, and a content snippet in this browser session. Use View sample report on the form to see an example first.
04
Fix what matters
Follow the checklist to strengthen llms.txt — then sign in for a full GEO Site Audit across six pillars.

llms.txt best practices

Start with H1 and a blockquote. Open with `# ProductName` and a `> one-sentence positioning` line so models grasp your category quickly.

List public pages with one-line descriptions. Use `[Title](url): description` under a Public pages section — include Privacy, Terms, and support email.

Separate signed-in modules from crawlable URLs. Document authenticated areas in prose without deep links crawlers cannot read without a session.

Bump Last-Updated when you revise. Add `Last-Updated: YYYY-MM-DD` at the bottom and update it whenever routes or product scope changes.

Pair with a GEO site audit. llms.txt helps AI discovery context; Site Audit checks whether your homepage is technically and structurally AI-ready.

LLMs.txt Checker FAQ

Everything you need to know about gptmelo.com.

What is llms.txt?

llms.txt is a plain-text file at your site root (yoursite.com/llms.txt) that summarizes your product and links to key public pages — a curated map for AI crawlers and models, similar in spirit to robots.txt but focused on discovery context.

Where should I put llms.txt?

Publish it at https://yourdomain.com/llms.txt — the domain root, not a subdirectory. On Next.js, place the file in public/ so it deploys to /llms.txt automatically.

How is this different from robots.txt or sitemap.xml?

robots.txt controls crawl allow/deny rules. sitemap.xml lists URLs for search engines. llms.txt adds human-curated context — product summary, public vs signed-in boundaries, and which pages are authoritative for compliance questions.

Does this checker verify every linked URL?

No — it validates structure and GEO best practices (sections, links, Last-Updated, auth boundaries). For full on-page readiness, run a GEO Site Audit on your homepage.

Do I need an account to see results?

No. Domain checks and content validation preview in this browser session without a signup wall. Sign in when you want saved site audits and workspace tools.