No, you do not need an llms.txt file to show up in Google's AI answers. Google published its own guide to generative AI features in Search, last updated 10 July 2026, and put that file in a section titled "Mythbusting generative AI search: what you don't need to do."
The exact line: "You don't need to create new machine readable files, AI text files, markup, or Markdown to appear in Google Search (including its generative AI capabilities), as Google Search itself doesn't use them."
If you have spent the last few months being told the opposite by SEO threads, that sentence is worth reading twice. Google also tells you to ignore chunking your content into tiny pieces and rewriting your pages in a special voice for machines. Structured data is called useful for rich results, and explicitly not required for AI search.
So what does work? Mostly one thing you can control on a single page: your show page.
Why creators keep hearing the opposite advice
Because the advice is easier to sell than the work. A file you can upload in an afternoon sounds like a lever. A show page that reads like someone with 80 episodes behind them wrote it does not scale into a service package. Google shipped the counterargument in its own documentation, on the record, with a date on it.
What is query fan-out, and why does it change your show page?
Google defines query fan-out as "a set of concurrent, related queries generated by the model to request more information and fetch additional relevant search results to address the user's query." Its example is a lawn: ask "how to fix a lawn that's full of weeds" and the model also goes looking for "best herbicides for lawns", "remove weeds without chemicals", and "how to prevent weeds in lawn".
Now put your show in that machine. Someone asks an assistant for "a good interview podcast about small business finance." Behind that one sentence, the model is very likely off fetching results for how long the episodes are, who the host is, whether the guests are practitioners or authors, how often it publishes, and where to listen.
Your show page either answers those or something else gets quoted instead, usually a directory listing written by nobody in particular.
Which questions should one show page answer?
Write out the five to eight things a stranger needs before they press play, then check that your page states each one plainly instead of implying it.
| What the model is looking for | What your page needs to say, plainly |
|---|---|
| What the show is about | One sentence naming the topic and who it is for, in the first paragraph |
| Who the host is | Your name and the experience that makes you credible on this topic |
| Format and length | Interview or solo, and the real average runtime |
| Publishing schedule | Weekly, fortnightly, seasonal, with the day |
| Who the guests are | Names and roles from recent episodes, not "industry leaders" |
| Where to listen | Named platforms with working links |
| What a specific episode covers | Titles plus transcripts, so the words exist as text |
One page. Not eight. This is the part people get wrong, and Google says so directly: creating separate content for every possible variation of how people might search, including fan-out queries, primarily to manipulate rankings or AI responses "violates Google's scaled content abuse spam policy." Google adds that it does not work anyway, because a high quantity of pages does not make a site more relevant.
Transcripts are the cheapest win in that table. They turn 40 minutes of speech into text a model can actually retrieve, and they are the same asset that makes your show accessible to deaf and hard of hearing listeners. If you are already producing episode audio in a studio like Vois, exporting the script or transcript alongside it costs you nothing extra.
Why episode-summary boilerplate does not get cited
Google draws the line with two page titles, in its own words:
Commodity content (for example, something like "7 Tips for First-Time Homebuyers") is often based on common knowledge, which could originate from anyone, and typically adds little unique insight for readers. In contrast, non-commodity content (such as "Why We Waived the Inspection & Saved Money: A Look Inside the Sewer Line") provides unique expert or experienced takes that go beyond common knowledge and the ordinary.
Read those two titles again and then read your last five episode descriptions. Most show pages are the homebuyer tips: a synopsis anyone with the audio file could have written, in the flat register of a press release.
Google is blunt about the same failure in the section on unique viewpoints. A first-hand review provides a perspective based on personal experience, "whereas a summary of existing content simply restates information already available elsewhere." Then the sentence that should be pinned above every content calendar: don't publish what "could easily be produced by a generative AI model."
What a non-commodity show page actually contains
The production story. Nobody else has it.
Write the paragraph about why you moved from two remote mics to one room and what it did to your guests' answers. Write what you learned publishing weekly for a year and then dropping to fortnightly, including the download numbers moving the wrong way for six weeks before they recovered. Write which intro you tested and abandoned.
None of that is keyword work. It is the only material on your page a model cannot generate from thin air, which is exactly why it is the material worth grounding an answer in. If you want a starting structure for that kind of writing, our podcast voice kit includes the show page prompts and the intro scripts we use, and our notes on building a consistent voice brand cover the tone side of it.
How do you check whether AI search is citing you?
In Search Console, using the Generative AI performance report. Google's guide names it as the way to see how your content performs in generative AI features on Google Search and Discover, and it reports on your own property rather than on a sample of prompts.
One prerequisite from the same guide, easy to miss: to be eligible to appear in generative AI features, a page must be indexed and eligible to be shown in Search with a snippet, and a site "must be included in Search generative AI features in Search Console." Check that before you conclude your content is being ignored.
Do AI agents change how you build the page?
They are starting to. Google's guide has a section on agentic experiences: autonomous systems that perform tasks for people, where browser agents visit your site and gather what they need by "analyzing visual renderings (like screenshots), inspecting the DOM structure, and interpreting the accessibility tree."
Notice what an agent reads. The accessibility tree is the same structure a screen reader uses. Google's advice on semantic HTML is careful here: perfect code is not required, but semantic HTML is a good idea because it helps other kinds of users, including screen readers, parse and navigate your page. It is framed as accessibility, and agents come along for the ride. Google points to web.dev's agent-friendly website guide for the details.
Practical version for a show page: real heading levels instead of styled divs, a labelled audio player, alt text on your cover art, and a subscribe link that is a link.
The show page rewrite checklist
Give yourself an afternoon and go in this order.
- Answer the question in the first two sentences. If the page is about your show, say what the show is and who it is for before anything else loads.
- State the facts plainly. Host, format, average runtime, schedule, recent guests by name, platforms. No inference required.
- Cover the fan-out set on one page, with real headings for each part instead of a wall of prose.
- Add transcripts. Every episode, even rough ones, cleaned up where it matters.
- Replace one synopsis with one production story. Then do that again next month.
- Fix the markup. Headings, labels, alt text, working links.
- Open the Generative AI performance report and write down today's numbers so next month means something.
Skip the file uploads. Skip the ten thin variation pages. The thing that makes your show page quotable is that a person with a microphone and a year of scars wrote it, and Google's own documentation now says as much in writing.
If you want the dated policy changes as they land rather than three months later, we send them out in the Vois newsletter. And if you are rewriting your intro while you are in there anyway, these intro techniques and our guide to turning written posts into narration pair well with the rewrite.
Write the page only you could write, then go check the report in thirty days.
The Vois Team