Podcast SEO guidance is near-unanimous on one thing: the text layer is what search engines actually read. The episode page, the title, the description, the transcript, the show notes — these are the parts that get crawled and indexed, not the audio waveform. Google's structured data documentation is explicit that markup helps it understand page content and qualify for richer search features, but provides no guarantee of ranking gains by itself. The audio needs a well-built text wrapper to be discoverable at all.
Given that, the conventional workflow makes sense on paper: record the episode, generate a transcript, then optimize the show notes, title, and description for the terms you want to rank for. The problem is that this approach treats the transcript as a raw material to be retrofit with search intent after the fact. And the transcript reflects what the host knew and said when they sat down. If the keyword research happens only after recording, the terms you want to rank for exist in your metadata — but not necessarily in the most semantically dense part of your content: what the host actually said.
If you only do post-recording SEO, you often end up writing around a conversation that never targeted a real query in the first place.
What the research says about text versus audio
Current evidence supports that transcripts and detailed episode pages are the primary discoverability layer for podcasts in web search, because they expose the words, entities, and long-tail phrases inside an episode to search engines. Audio content indexed by platforms like Spotify uses their own internal search systems, which are separate from open web search. For open web visibility — the kind that puts an episode in front of someone searching on Google — the text wrapper is what matters. Industry guides on podcast SEO are consistent on this: one episode page per episode, a clear title, a detailed description, a full transcript, relevant show notes.
A useful honest caveat here: direct comparison studies between pre-recording SEO and post-recording SEO in podcast contexts don't appear to exist in the academic literature, as of the research conducted for this article. The evidence for the pre-recording approach is a strong inference from adjacent findings, not a proven head-to-head result. What is well-supported is that keyword density is not a direct ranking factor — Semrush is explicit about this — and that topical completeness and natural language use matter more than mechanical repetition of terms.
We have not found controlled studies showing that episodes planned for SEO before recording outrank episodes optimized only after publication. The pre-recording argument is supported by mechanism evidence from speech cognition research and SEO fundamentals — not a podcast-specific ranking comparison. We are stating what the evidence supports, not more than that.
The speech and cognition angle
This is where the argument gets more interesting. Cognitive research on language production is consistent that internalized concepts are easier to articulate naturally than terms you're trying to insert deliberately. Speaking reinforces recall — the act of producing language strengthens the memory trace of the material being spoken. Applied to podcasting: if a host has genuinely internalized a set of target terms during preparation, those terms are more likely to surface organically throughout the recording. If those terms only exist in the show notes added afterward, the semantic density of the actual transcript is lower.
This is not a trivial distinction. The strongest SEO signal in a transcript is natural, high-frequency use of target language across the full running length of the content — not a cluster of terms in the show notes section that the host never spoke. For a 45-minute episode with a full transcript, the body of indexable text is large. If the episode was prepared with clear search intent in mind, that transcript will contain the relevant terms, entities, and semantic variations naturally. If it wasn't, the terms live in a thin layer of copy that wraps a conversation that went a different direction.
How we do it in practice
Before an episode goes into production, we identify the primary query and two to three secondary semantic targets the episode should serve. These inform the episode brief alongside the research findings. The host gets a document that contains the verified claims, the argument architecture, and — embedded in that architecture — the language we want to appear naturally in the recording. Not as a list of terms to insert, but as part of how the argument is framed.
After recording, the transcript gets cleaned as editorial content, not raw machine output: readable speaker labels, section breaks, and a usable summary. The episode page is built with the primary target in the title, a descriptive lead in the show notes, timestamps, and structured data markup. The two phases solve different problems: pre-recording plants the seeds; post-recording builds the page that Google actually reads.
What this means for the transcript quality
The practical test is simple. Read the transcript of an episode that was prepared with a clear search target versus an episode that wasn't. In the first, the target topic and its related terminology appear naturally throughout — because the host knew what they were talking about before they opened their mouth. In the second, the topic may be in the title and the show notes, but the transcript wanders, hedges, and circles back because the argument architecture wasn't set. Post-production can clean the audio, but it can't tighten reasoning that wasn't there.
The best-supported workflow in the current evidence is: plan the topic and the search intent before recording, speak naturally to that intent, then publish a strong text wrapper afterward. Pre-recording and post-recording SEO are not competing approaches — they solve different parts of the same problem. The mistake is assuming the post-recording pass can compensate for not having done the pre-recording work.