If someone told you your website needs llms.txt to rank on Google, you can put that task on hold. Google Search explicitly ignores the file. It is not a missing SEO requirement.
That does not make every use of it pointless. It is a proposed way to give systems that choose to use it a short guide to a website's content. Documentation can be useful when it has an actual reader and is kept accurate.
The decision is not “does everyone have this file?” It is “who will use ours, and what will it help them do?”
Know what is being proposed
The llms.txt proposal describes a Markdown document that introduces a site or project and points to useful resources. It is commonly published at /llms.txt.
The current proposal requires a top-level heading naming the site or project. A short summary, explanatory text and grouped resource links are useful optional parts. It does not require every site to have an identical set of section names.
Support is not universal. Publishing a file does not prove an AI provider reads it, trusts its claims or will cite your pages.
Google's AI optimization guidance states that Search ignores llms.txt: it does not help or hurt Search rankings or visibility, including Google's AI experiences. Do not buy or prioritize the file on the promise of a Google ranking improvement.
Decide whether maintaining one is worth the work
It may be reasonable if you have a concrete use: a documentation consumer that supports the proposal, or a workflow that benefits from a small, curated list of public resources.
Ask what information that consumer needs and where the authoritative answer already lives. A product with extensive documentation might provide a brief introduction and links to installation, supported features and limitations. A small service business with no such consumer may have no need to create the file.
If your public pricing page is outdated, your articles are unreachable, or your contact form fails, fix those things first. An optional document does not compensate for a website that is hard for people to use.
A missing file can be the correct outcome. Do not confuse “not present” with “something is broken.”
Check an existing document without Google connections
If you already maintain one, open SEO Dispatcher's llms.txt checker and enter your website address. The tool requests the origin's /llms.txt; it does not need Google Analytics or Search Console.
The checklist reviews whether the document is reachable, has a site title and summary, and contains usable Markdown links with absolute web addresses. These are focused format and quality checks, not a certification that all AI systems accept the document.
Read Found and Result separately. A summary being present does not make it accurate. A missing recommended summary does not mean the current proposal's required heading is invalid. An unavailable response does not prove the file never existed.
The report observes a bounded list of links, up to twenty, and checks a small sample of up to four same-origin destinations. External destinations and unsampled links need separate review. An observed 404 or 410 can identify a missing sampled resource; a fetch failure is uncertainty, not proof that a destination works.
Review the wording against the real website
The more important check is manual: does the document describe what is true today?
For a hypothetical appointment app, a summary might explain who it is for and link to current setup and booking documentation. It should not promise SMS reminders, a free plan or an integration unless those features actually exist under the stated conditions.
Use a small review checklist:
- Does the name clearly identify the site or product?
- Does the summary describe the real offer without inflated claims?
- Do the links point to current, public, authoritative pages?
- Are limitations and eligibility conditions easy to find where relevant?
- Is there a person or process responsible for updates?
The checker does not fact-check your business claims or compare the document with every page. A clean format can still describe a product badly. Someone who knows the product needs to review the words.
Fix links at their source
For each flagged link, open the destination and establish what happened. Was the page moved, removed, made private or temporarily unavailable?
If it moved, update the resource link to the current preferred address. If it no longer exists, remove the reference or choose a genuinely relevant replacement. Do not point every missing guide to the homepage: that keeps the link alive while removing the promised answer.
Use absolute public URLs in this document so destinations are unambiguous. Keep credentials, private dashboard links and personal information out of a publicly served file.
If your repository or website builder generates the document, update that source. Editing a downloaded copy on your laptop will not change the live response. Check the published file afterwards.
SEO Dispatcher's free tool reports observations. It does not generate, rewrite or deploy the file for you.
Do not use it as a permission or indexing control
llms.txt does not secure content, replace robots.txt, or remove a page from search. A resource being listed does not establish permission for every use of that resource.
If you want to examine crawl permissions, use the robots.txt guide and consult the relevant provider's current crawler documentation. If you need private content protected, use real access controls. If you want to diagnose a public page's indexing eligibility, inspect the page and its instructions instead.
Keeping those jobs separate prevents a misleading “AI-ready” badge from becoming a substitute for actual configuration.
Finish with a maintenance decision
The best outcome may be “we do not need this file.” If you do keep it, record the consumer, the source of truth and who updates it when pages or product features change.
The free allowance is three accepted runs total per user and domain across all tools, with no reset. Signing in shows more of the same report, not extra attempts. Accepted fetch failures still count; saved reports can be reopened within their 24-hour availability without another run. Anonymous users on a shared network may share an allowance.
Do not spend a limited check trying to make an optional file mandatory. Use it to review documentation you actually maintain.
For a different job—choosing useful articles from your own search evidence and preparing reviewed content changes—SEO Dispatcher's paid workspace provides a connected workflow. Better content and clearer documentation each have a purpose; neither needs a promise of guaranteed rankings or AI citations.