A clear answer on your llms.txt.
Check the file agents find, see what holds up, and fix what does not. Required errors stay separate from optional guidance.
Methodology
Strict where the proposal is strict.
The checker follows the current version 2 proposal. It verifies the opening project name, then treats summaries, sections, notes, and link conventions as recommendations.
Read the proposal- 01
Fetch
Confirm the file resolves, returns text, and stays within safe limits.
- 02
Read
Check the required opening structure without inventing extra rules.
- 03
Verify
Test up to 20 listed destinations and surface broken pages.
Common questions
The useful context, without the folklore.
What does an llms.txt file require?
In the current version 2 proposal, the only required element is one H1 project or site name at the start. A summary, sections, links, and notes are useful but optional.
Does llms.txt improve Google rankings?
Google says special AI text files are not required for its Search AI features. Treat llms.txt as an emerging discovery aid for agents, not a ranking shortcut.
What happens to a draft I paste?
The draft is checked in request memory and returned to your browser. AgentReady does not save it. Pasted drafts receive structure checks only because there is no live HTTP response to inspect.
Why are recommendations separate from errors?
The proposal is intentionally small. Separating required errors from optional guidance keeps the result accurate while still showing how to make the file more useful.
Need a file before you can check it?
Generate an llms.txt draft