AgentReady.me

Free practical tool

llms.txt checker and generator

Inspect the file your site actually serves, catch common deployment mistakes, and generate a concise starting point with links you can maintain.

Important boundary: Google says it does not use llms.txt for Google Search, including generative AI features. A good file may orient other tools that choose to read it; it does not improve Google rankings, grant permission, or prove an agent can complete a task. Read Google's current guidance

Checker

Inspect the live root file

We fetch only the submitted site's public /llms.txt, follow validated public redirects, and inspect up to 256 KB.

Generator

Create a maintainable starting file

Choose an example, replace the facts, then preview, copy, or download the exact text.

# Acme Analytics

> Privacy-conscious product analytics for software teams that need clear funnels and reliable event data.

Canonical site: https://example.com/

## Important pages

- [Product overview](https://example.com/product)
- [Pricing and plan limits](https://example.com/pricing)
- [Developer documentation](https://example.com/docs)
- [Security and privacy](https://example.com/security)

## Notes

Public documentation is authoritative. Account, billing, and data-export actions require user authentication.

What this checks

Verify the artifact, not a marketing claim

  • Delivery: root URL, final status, redirect destination, and text media type.
  • Shape: a useful title and concise summary instead of an empty file.
  • References: descriptive Markdown links and absolute public URLs.
  • Routing: detection of a branded HTML shell accidentally served at /llms.txt.

What it cannot prove

This checker does not test whether every linked fact is current, whether a third-party model consumes the file, whether pages rank or receive citations, or whether an agent can safely complete signup, booking, purchase, or product use.

Compare discovery files Visibility audit vs. readiness audit

A maintainable llms.txt checklist

  1. 1

    Name the product

    Use the public product or organization name—not an internal project codename.

  2. 2

    State the job

    Explain what the site helps someone do and who it serves in one factual sentence.

  3. 3

    Link source-of-truth pages

    Prefer canonical product, pricing, policy, docs, and contact pages over duplicated prose.

  4. 4

    Keep authority explicit

    A public file may describe capabilities; it cannot authorize an account, payment, or write action.

  5. 5

    Own the updates

    Regenerate or review the file whenever routes, plans, policies, or product scope change.

  6. 6

    Test the actual journey

    Pair discovery files with semantic browser and API checks for the outcome customers delegate.

Frequently asked questions

Does llms.txt improve Google rankings or AI Overview visibility?

No. Google says it does not use llms.txt for Google Search, including its generative AI features. Maintain one only for tools or readers that choose to consume it.

Where should llms.txt live?

The emerging convention places it at the origin root, such as https://example.com/llms.txt. It should return actual text rather than an HTML application fallback.

What should an llms.txt contain?

Use a truthful title, a concise product description, descriptive absolute links to maintained public pages, and only the operational notes a reader needs. Never include secrets or imply authorization.

Check the journey beyond the file

Run a free public scan for discovery, semantics, forms, browser compatibility, safety signals, and evidence-backed fixes.

Scan the full agent journey