Google says it ignores llms.txt. Is it worth your 30 minutes?

Google Says It Ignores llms.txt. Is It Worth Your 30 Minutes?

Skip llms.txt if your goal is Google visibility. Google’s June 15, 2026 clarification says the file neither helps nor hurts visibility or rankings in Google Search, including its generative AI features; spend those 30 minutes improving a public page that answers a buyer’s question. (developers.google.com)

What Google clarified on June 15, 2026

Google Search Central added a note to its AI optimization guide: Google Search does not use llms.txt, and keeping one won’t improve or reduce your visibility or rankings. The guide also says you don’t need special AI text files, Markdown, or markup to appear in Search or its generative AI features. Google may crawl and index different kinds of files, but that does not give them special treatment. (developers.google.com)

That includes Google’s AI features. Google says AI Overviews and AI Mode rely on the same basic Search foundations: a page needs to be indexed and eligible to appear with a snippet. There are no extra technical requirements or special files to create for those features. (developers.google.com)

Don’t confuse llms.txt with robots.txt. Google says robots.txt directives for Googlebot control how your site is crawled for Search. Google’s AI optimization guide instead says to focus on clear, useful content and sound technical SEO. (developers.google.com)

Rank your options for the next 30 minutes

Improve a public page that answers a buyer’s question. This is the best use of the time. Google says helpful, original content matters for generative AI visibility, and its AI features use pages from Google’s Search index. (developers.google.com)
Make an important page easier to find and index. Link to it from a relevant page on your site. Check that it is public, crawlable, and not blocked from indexing. Google recommends internal links to help people and Google find important pages. (developers.google.com)
Create llms.txt only if another service you use specifically needs it. Google says it’s fine to keep one for other services or systems that use the file. That’s a separate reason from improving Google visibility. (developers.google.com)

Who should not bother? A founder with a small site and limited content time who wants better Google Search or AI visibility. Google has already answered that question for you.

A worked example: 30 pages and two hours a month

Suppose you run a three-person SaaS with 30 pages and two hours a month for content. One 30-minute llms.txt task would use 25% of that monthly budget. If you value founder time at $100 an hour, that block costs $50 in opportunity cost—even if there’s no cash charge.

Instead, pick one page that matches a real buyer question. For example, suppose your SaaS helps small agencies approve invoices, and one page says little more than “automate invoice approvals.” A buyer might be asking: “How can a 10-person agency approve invoices without chasing people in Slack?”

Use the page to answer that question in plain terms. Explain the steps, who can approve an invoice, what your product supports, and where its limits are. Add a screenshot if it helps. Make the next step clear: see pricing, start a trial, or book a demo.

For the traffic part of the example, use your own data: record that page’s clicks from the last 28 days in Search Console before you edit it. That gives you a real starting point to compare later; it does not promise a traffic increase. Google’s guidance is clear that pages need to be indexed and eligible for a snippet to appear in AI features, but meeting those conditions does not guarantee that Google will show a page. (developers.google.com)

Use the half-hour to improve the page

Minutes 0–5: Pick the question. Check Search Console for a query related to the page. Add a question you hear in sales calls or support tickets if it better matches what a buyer needs to know.
Minutes 5–18: Write a direct answer. Put the answer near the top. Then explain how the product works, who it fits, and what it does not do. Use details only your team can provide; Google recommends useful content with a distinct point of view, not a rewording of common advice. (developers.google.com)
Minutes 18–23: Link to the page. Add a link from your homepage or a related page, using words that tell a reader what they’ll find. Google’s link guidance says every page you care about should have a link from another page on your site. (developers.google.com)
Minutes 23–30: Check the page in Search Console. Use URL Inspection to see whether Google has indexed it. If it is not indexed, check the report for crawl or indexing problems. Google’s tool can show whether the page is on Google and help diagnose why it is not. (support.google.com)

This is a better trade than making a file that Google says it ignores. The page can help a buyer understand your product, and it gives Google a public, crawlable page to consider.

If publishing useful content every week is the larger bottleneck, AutoPod can turn research into SEO articles and podcast episodes and publish them on your own domain. Start with the buyer question; automation can help keep the work moving.

When llms.txt still makes sense

Keep the file if a specific non-Google service or system you use asks for it, and maintaining it fits your workflow. Just don’t treat it as a Google SEO task. Google’s June clarification gives you a better priority: make your important pages public, easy to find, and genuinely useful to the people deciding whether to buy.

**This week, open Search Console, choose one product page tied to a buyer question, and spend 30 minutes making the answer clear and easy to find.