Some 167 million Americans listened to a podcast last month, an all-time high, and roughly 175 million episodes now sit in public feeds. You'd expect a medium that size to turn up somewhere in the research on where AI answers get their sources. Yet four large-scale studies of how AI engines cite, covering more than 680 million citations between them, name exactly zero podcast platforms as a source.
The reason podcasts and AI citations barely intersect is mechanical. Engines cite text, and podcasting's text layer is thin and scattered to begin with, and on one major platform it's actively fenced off.
The corpus nobody cites
The audience side of this is enormous. Edison Research's Infinite Dial 2026 puts monthly podcast listening at 58% of Americans aged 12 and up, with 130 million people listening every week. That's a mainstream habit by any measure, and advertisers pay for it like one. Per IAB and PwC, US podcast ad revenue grew 17.6% to $2.9 billion in 2025, and about 26 million new episodes shipped last year alone.
The citation research tells a very different story. The 5WPR Citation Source Index synthesized 680 million citations from ChatGPT, Claude and Perplexity, plus Gemini and Google AI Overviews, and published the 50 domains that dominate AI answers. Reddit made that list, and so did Wikipedia, YouTube and Forbes. No podcast platform did.
A second dataset points the same way. Foundation and AirOps tracked 57.2 million citations across 5.1 million responses. In their breakdown Reddit leads at 20.8% of sources, YouTube (13%) and LinkedIn (11%) come next, and help docs and review sites show up too. No podcast surface registered at all. Yext's 155 million citations and Qwairy's 669,000-citation analysis tell the same story by leaving podcasts out.
Absence of evidence does cut two ways here. Podcast content may well earn citations through individual show websites that are too small and scattered to register in domain-level studies. That's the charitable reading, though, and even under it no podcaster can point to a published benchmark showing that episodes earn AI citations. As far as any measurable citation data shows, the most-consumed content medium in America is nearly invisible to the answer engines.
The Foundation dataset has two more numbers that sharpen the picture. In over two-thirds of AI responses that discussed a brand, the brand's own content was completely absent from the citations, and on unbranded, category-level discovery queries, brand-owned domains earned just 2.2% of citations.
Apply that to podcasting and you get a conclusion that's uncomfortable but useful. Even a perfect episode page on your own domain is playing against a stacked deck, because engines prefer third-party corroboration. You still need the episode page. What actually gets pulled into answers, though, is the recap on someone else's site, the roundup that quotes your guest spot and the community thread where people discuss the episode.
Why audio is invisible: crawler mechanics
The explanation is sitting in the crawler documentation. OpenAI's bot docs describe OAI-SearchBot and GPTBot as web crawlers that read pages, and nothing in the spec mentions MP3, WAV or any kind of audio parsing. PerplexityBot and ClaudeBot are built the same way, as text-based HTML readers. So when an AI engine seems to "know" what a podcast said, it read a page that quoted the episode and never heard a second of the audio.
Google is the partial exception, and the details matter. In March, Search VP Liz Reid said LLMs can now understand audio and video "at a level we couldn't years ago", going past transcription toward style and context. She also said Google has taken "small steps so far." That capability lives in Google's own AI layer. History also shows what happens when the text bridge goes away: Google Podcasts used to transcribe episodes and surface them in a search carousel, and when it shut down in 2024 the carousel died with it. Today even Google mostly reaches podcast content through the episode's crawlable webpage.
Everything downstream follows from one rule, which is that a podcast episode's AI visibility equals the quality of its best crawlable text surface. If there's no text page, there's no citation, however good the conversation was.
200+ SaaS teams already track their AI citations.
They know exactly when ChatGPT mentions their brand, and when it stops. Do you?
The platform trap: Spotify fences, Apple opens
This part surprised us, and we only caught it because we pulled the robots.txt files ourselves instead of trusting anyone's summary. Almost nobody seems to have noticed the split.
Spotify's robots.txt runs a two-tier policy. Training crawlers are blocked from the entire site, which covers GPTBot, Google-Extended and ClaudeBot as well as CCBot and Bytespider. The citation-fetching bots (OAI-SearchBot, PerplexityBot and Claude-SearchBot) get onto exactly two paths, /embed/ and /oembed. That leaves the full episode pages, show notes and descriptions included, off-limits to every AI bot that could ever cite you.
Comments in the file spell out the intent, which is protecting Spotify's "catalogue graph and entity relationships." Its October 2025 ChatGPT integration doesn't change the math either. That deal pipes recommendations and playback into ChatGPT while explicitly withholding content from training, so Spotify ends up as a distribution surface and never a citation surface.
Apple Podcasts' robots.txt is the mirror image. Episode pages are fully crawlable with no AI-specific restrictions, and Apple actively publishes episode-level sitemaps that hand crawlers a map of every show page. Apple Podcasts is quietly the only major platform whose episode pages an AI citation bot can actually read.
If you rank the surfaces by how accessible they are to citation bots, the hierarchy looks like this:
| Surface | Crawlable by AI citation bots? | Notes |
|---|---|---|
| Your own episode page with transcript | Yes, fully | You control schema, structure, and internal links |
| Apple Podcasts episode page | Yes | Sitemapped by Apple; metadata only, no transcript |
| Third-party recap and transcript sites | Yes | Someone else's domain earns the citation |
| Spotify episode page | No (embeds only) | Show notes living only here are invisible |
| The audio file itself | No, nowhere | Invisible to every engine |
If your podcast strategy is "publish to Spotify, paste the notes there, done," then as far as answer engines are concerned your show doesn't exist.
What the text layer actually earns
Before the tactics, the evidence base needs an honest label. The only rigorously measured transcript effect on record is still 3Play Media's study of This American Life. After the show published full transcripts, its search traffic rose 6.68% and its inbound links rose 3.89% over 27 months of data, and that was traditional Google search, measured in 2014. The mechanism is real enough, but every "transcripts got us 4-7x more AI citations" claim floating around the AEO content mill is marketing, an unverified assertion with no named brands and no methodology.
Where practitioners do agree is that you rework the transcript instead of posting it as is. Raw transcript dumps underwhelm, because nobody reads a verbatim hour and engines get a wall of filler words. The working pattern treats the transcript as raw material for a 2,000-word structured article per episode, with the question-shaped headings and clean claims that engines extract, plus episode schema. Several podcasters have automated the whole pipeline, so a transcript goes in and a structured post with JSON-LD comes out. The thread where people compare these workflows is worth the read:
What do y'all do with your episode transcripts in order to help SEO?
Back in the day, people here used to talk about using transcripts to help with Search engine optimization. That sounded wonderful, but I wasn't about to type the entirety of an episode out. Now that AI just kind of does it automatically for...
One growth operator made the same point from the SEO side, years before the AI angle made it fashionable. The advice was to pull the transcript, mine it for the long-tail questions the guest answered and publish each answer as its own indexable page. That advice dates to 2024, which is exactly the point, since the transcript-to-text-asset play predates answer engines. What answer engines did was raise its payout. Every derived page is now a candidate for extraction into an AI answer, on top of its old job as a blue link.
How often does ChatGPT mention your brand?
Most founders have no idea. The answer might surprise you.
The video pivot is quietly an indexability pivot
For the last two years the industry argued about video podcasts as an audience play, and the indexability angle got missed entirely.
Edison's 2026 data shows that 57% of Americans have now both listened to and watched podcasts, and YouTube's 32% share of daily podcast time puts it ahead of Spotify (25%) and Apple (20%). Listeners went multi-format, and each format leaves a very different data trail behind it. A YouTube version generates captions on a heavily crawled domain that citation studies consistently rank near the top, and Gemini reads that transcript layer directly. By default, the audio-only version of the same conversation generates nothing at all.
Spotify and Apple both auto-transcribe episodes now, which sounds like it solves the text problem until you look at where those transcripts render: inside the apps, behind the same walls we mapped above. They help with in-app accessibility, but they add zero crawlable text to the open web, and an AI bot can't cite a transcript it has no way to fetch.
Meanwhile discovery is drifting toward exactly the surfaces bots can read. Buzzsprout's tracking across 120,000+ shows found that browser-based listening, where someone finds and plays an episode from a web search, grew from 5.4% to 7.3% of listens by early 2025. That's a small share on a steady climb, and every one of those plays starts on an indexable page. The episode webpage is turning into the front door for humans and machines at the same time, so neglecting it costs you twice.
Guesting: weak links, strong entity
For SaaS founders the sharper question is usually about appearing on other people's shows, and the r/SEO consensus on that is worth taking seriously:
Is podcast guesting actually worth it for SEO?
For a long time, I’ve been thinking about trying to get myself booked on other people’s podcasts as a way to support my website but I’m not sure whether it’s actually a wise use of my time. I’ve seen services that help connect you with podc...
The thread's verdict is that guesting makes a mediocre backlink play, since show-notes links are mostly nofollow and sit on low-authority pages. Yet the practitioners who dismiss it on link math keep tripping over their own counter-examples. One agency founder in that thread spent 18 months unable to land clients, then appeared on one niche trade podcast and watched the business take off.
In the AI era, the mechanism behind stories like that is entity accumulation. Engines decide whether to recommend a brand by cross-checking how consistently independent sources describe it. Every crawlable transcript or episode page that names you, describes what you do and links your site is one more corroborating document. It's the same math we laid out for unlinked mentions in digital PR, where the mention does the work whether the link is followed or not.
Guesting also feeds the surfaces engines demonstrably do cite. A video version puts your words into YouTube's transcript layer, which Gemini reads directly (that pipeline deserves its own article), and guest appearances compound with the platforms at the top of every citation study. One content marketer documented that chain in real time. A strong newsletter earned her podcast invitations, and the combined footprint turned into 15+ tracked AI citations.
Podcasts feed those surfaces rather than replacing them. Her list of "the most human places on the internet" (Reddit, YouTube, LinkedIn) matches the Foundation citation data almost exactly, and we've written up why Reddit sits at the top of that list.
What the engines say when you ask about podcasts
One experiment shows where authority actually lives. Podglomerate asked seven AI tools which podcasters get cited most and got back the same eight names from nearly every model: Rogan, Fridman, Ferriss, Huberman and the rest of the household tier. The models were reciting fame instead of retrieving anything about podcasts. Two of the tools volunteered that no database actually tracks podcaster mention frequency, and several confidently hallucinated show titles and affiliations.
I take two lessons from that. The first is that the citation rarely rides on episode-level content, because the entity carries it. AI tools name famous podcasters since thousands of text pages discuss them, and whether the engines indexed their shows doesn't come into it.
Measurement claims in this niche also need scrutiny. LLM answers are generated fresh on every run, so any "we tripled podcast citations" claim built on single spot-checks is noise. The only defensible measure is your appearance rate across repeated prompt runs, the same distribution logic we apply to AI search volume claims.
On markup, set your expectations carefully. PodcastEpisode and PodcastSeries are stable schema.org types and worth shipping for machine comprehension. Google dropped its podcast structured-data support along with Google Podcasts, though, so the markup feeds entity understanding and won't earn you rich results. Practitioners increasingly add Clip markup with time offsets as well, so engines can reference specific moments.
The playbook: make the audio leave a paper trail
Everything above compresses into six moves, and I'd take them in order of payoff. Start by owning the episode page. Every episode gets a page on your domain with a summary, the key claims with their numbers and a guest bio with links. Lower down go the embedded player and the full transcript (below the fold), and the page carries PodcastEpisode schema. From there, transform the episode instead of dumping it: one structured article per episode, with question-shaped H2s and the guest's best stats made quotable. That article, and not the transcript, is your citation candidate.
Next, treat Apple as an SEO surface and Spotify as a player. Complete the Apple metadata, because those pages are crawlable and sitemapped, and never let show notes live only on Spotify. Use a filter when you guest, too. Before booking, check whether the show publishes transcripts or episode pages on a real, crawlable website, and ask for the transcript page as part of the booking. A great conversation on a Spotify-only show leaves no trail.
The last two moves happen after the episode ships. Clip and repurpose every episode into YouTube, LinkedIn and the community threads engines actually quote. Then track presence instead of downloads by running your buyer prompts across ChatGPT, Perplexity and Gemini on a schedule and logging whether the episodes, the guests or your brand surface in answers.
Where a new episode page shows up first
The engines don't all offer the same odds, so it helps to watch them in the right order. Qwairy's analysis of 669,000 citations found that Perplexity attaches an average of 21.87 citations per response, nearly triple ChatGPT's 7.92 and four times Claude's 5.67. More citation slots per answer means more room for a new page to grab one, and Perplexity also indexes fresh third-party content fastest.
In practice, your new episode article will almost always turn up in Perplexity answers weeks before ChatGPT acknowledges it exists. If it still hasn't appeared in Perplexity after a month of prompt checks, the page has a content or crawlability problem, and that's worth fixing before you blame the strategy.
Keep one boundary straight while you measure: none of this touches in-app podcast search. The internal search engines at Apple and Spotify index little beyond show titles, episode titles and author tags, and the practitioners who've tested it report that transcripts do nothing for in-app rankings. In-app discovery and AI-answer visibility are separate games played with separate signals, and this article is about the second one.
That's also where the skeptics have a point worth remembering, because nobody searches for podcasts the way they search for articles. Your episode won't be the answer to "best podcast about X." Its ideas, on a crawlable page, can be the answer to the hundred questions the episode covered.
The workload is real. A disciplined version of this takes three to five hours per episode, plus the recurring prompt-panel time, forever, and that last part is what we automate. RankControl checks your buyer questions across six AI engines every week and shows where your brand gets named, so you can see whether mentions rise after an appearance instead of guessing from download charts. Run the pipeline by hand or let our agents watch it, but don't record another 50 episodes without a text layer.
15 hours a week manually. Or 15 minutes with RankControl.
Track citations, monitor competitors, and fix content gaps across every AI search engine. Automatically.
The conversation was always podcasting's core asset. For answer engines it only starts to count once it leaves a paper trail, because the mic captures the insight but the transcript page is what a machine can quote. Most of your competitors haven't figured that out yet, which leaves the medium AI engines currently ignore wide open for anyone who ships episodes with text behind them.
