No. Google's documentation on AI features states there are no additional requirements to appear in AI Overviews or AI Mode, and no special optimizations are necessary. The same foundational SEO best practices apply. An llms.txt file is not a Google requirement, is not mentioned in that documentation, and should not be treated as a substitute for crawlable, useful pages.
What does Google's AI features documentation actually say?
Google's guide, AI features and your website, covers AI Overviews and AI Mode from a site owner's perspective. It says the best practices for SEO remain relevant, that there are no additional requirements to appear in those experiences, and that no special optimizations are necessary. It also recommends reviewing fundamental SEO best practices.
The same page explains the mechanism: AI Overviews summarize complex topics and act as a jumping-off point to links, while AI Mode supports exploration, reasoning and comparisons. Both may use a "query fan-out" technique, issuing multiple related searches across subtopics and data sources to build a response. That is a description of how responses are assembled, not a list of files a site must publish.
Where does llms.txt come from, and what is it for?
Llms.txt is a proposed convention, not a Google product. It is a proposed plain text file placed at a site root, typically listing key pages with short descriptions, intended to help language models find useful material. It emerged from parts of the AI and developer community rather than from Google Search documentation.
That distinction matters. A convention can be useful for teams that want a curated machine-readable map of their best content. It does not become a ranking or inclusion requirement just because it is widely discussed. Google's AI features documentation does not mention llms.txt, and it does not describe any file-based gate for AI Overviews or AI Mode.
Is llms.txt useless then?
Not necessarily, but its value is not what many summaries claim. It is a voluntary signal. If a platform chooses to read it, it may help that platform find preferred pages, though no official source confirms this effect. If a platform ignores it, nothing in Google's documented requirements is broken.
Treat it as an optional publishing and clarity exercise, not a switch. The practical test is whether the file duplicates information that is already discoverable through normal crawling and internal linking. If it does, it adds little. If it resolves genuine ambiguity about which pages represent a topic, it may help some consumers of the file, though this is not documented by Google.
What actually governs inclusion in AI features?
Google's documentation points back to foundational SEO. In practice that means the page must be technically eligible for Google Search: crawlable, indexable, and not blocked by rules that prevent it from being seen. Google's documentation states that content quality, relevance and helpfulness remain relevant, though selection for any given query is not guaranteed.
A useful diagnostic sequence:
- Confirm the page returns a normal HTML response and is not blocked by robots.txt or a noindex directive.
- Check that the page is indexed and can appear for relevant queries in ordinary Search.
- Review whether the content answers a real question clearly, with the main point near the top.
- Check internal links so the page is reachable through normal navigation.
- Only then consider optional files such as llms.txt.
This order matters because a file cannot compensate for a page that is not crawlable or not indexed. If a page fails step one or two, no AI-specific file changes the outcome.
Example: a hypothetical publisher
Consider a hypothetical UK-based publisher with 4,000 articles. It adds an llms.txt listing 200 "best" pages. Nothing else changes. If those 200 pages were already crawlable and internally linked, the file is unlikely to alter their eligibility, though this is a hypothetical illustration and not a documented outcome. If some were blocked by a misconfigured robots.txt rule, the file does not unblock them, as this is a hypothetical illustration. The fix is the robots.txt rule, not the file. These figures are illustrative only.
How should teams decide?
| Situation | Reasonable action |
|---|---|
| Core pages crawlable and indexed | Prioritise content quality and internal linking; treat llms.txt as optional |
| Pages blocked or not indexed | Fix technical access first |
| Multiple similar pages on one topic | Improve consolidation and internal links before adding a file |
| Team wants a curated AI-facing map | Publish llms.txt as a low-cost experiment, with no expectation of guaranteed effect |
What about AI crawler controls?
Separate from llms.txt, sites can manage AI-related crawlers through robots.txt user-agent rules and, where offered, publisher controls. Those are access decisions, not inclusion requirements. Blocking a crawler may reduce how content is used elsewhere; it does not create a documented path into AI Overviews or AI Mode, and access decisions are separate from inclusion requirements. Keep access policy and content strategy as two distinct decisions.
What remains uncertain?
Google's documentation is clear about requirements, but it does not describe every internal signal used to select supporting links. The behaviour of non-Google AI systems toward llms.txt is also not settled, and adoption varies. Any claim that a specific file guarantees visibility in AI features goes beyond what the documentation supports, as Google states there are no additional requirements or special optimizations. Verify changes by observing your own indexed pages and search performance over time, not by assuming a file has a fixed effect.
How can you verify claims about llms.txt?
Ask three questions of any recommendation: Does an official source state it as a requirement? Is the claim about Google Search or about a different platform? Can the effect be measured on your own pages? If a source cannot answer the first two, treat the advice as a hypothesis. For Google specifically, the AI features documentation is the reference point, and it points back to standard SEO practice.
For related context on how Google documents features, see our coverage of the Google Search Profile Badge documentation and why market-specific testing matters when features differ by region.
Follow-up questions
Does adding llms.txt improve rankings in Google Search?
No documented mechanism supports that. Google's guidance for AI features points to foundational SEO, and llms.txt is not part of that documentation.
Should I remove llms.txt if I already published one?
There is no documented penalty for having one. If it duplicates existing crawl paths and adds maintenance cost, removing it is a reasonable housekeeping decision rather than a corrective action.