Show Notes vs Transcripts: What to Publish and Where


Publish both, but in different places. Show notes are a short, curated description, title, hook, timestamps, links, that goes in your RSS feed and shows up in every app. A transcript is the full word-for-word text of the episode, and it belongs on your own website page, below the notes, not in the feed. They do different jobs: notes sell the tap, transcripts serve accessibility and long-tail search.
The mistake almost every new show makes is treating these as the same field. They paste a raw transcript into the description box (which buries the hook and breaks app layouts), or they write a tidy paragraph and skip the transcript entirely (which forfeits accessibility and a lot of searchable text). The two formats, plus a third, the summary, are three layers, and each has one right home.
Here is how to tell them apart, decide which to make for a given episode, and put each one where it actually earns its keep.
What's the difference between show notes and a transcript?
Show notes are a short, edited description of an episode, usually a title, a two-to-three-sentence hook, timestamps, links, and a guest line, totalling 150 to 300 words. A transcript is the complete spoken text of the episode, often several thousand words, with no editing for brevity. Notes are written to be skimmed; transcripts are written to be searched and read accessibly.
There is a third thing people conflate with both: the summary, a one-to-three-sentence abstract of what the episode covers. The summary is the shortest layer, the show notes are the middle layer, and the transcript is the full layer. Most shows need all three, and they are cheap to produce together because each is a subset of the same source material.
Which one helps SEO, show notes or transcripts?
Both, on different queries. Show notes carry your main keyword in the title and hook, so they help you rank for the episode's core topic, the words a person would type to find that show. A transcript adds thousands of natural-language phrases, so it helps you catch long-tail and question searches you never thought to target. Notes win the headline term; transcripts win the long tail.
This matters because the audio file itself is invisible to a search engine. Apple, Spotify, Google, and your own website index text, not speech. The title and show notes are the small, curated text surface; the transcript is the large, uncurated one. If you only publish one, publish the notes, they cover the query that actually describes your episode. If you can publish both, the transcript is found money for searches you'd never write a post about.
Two honest caveats. First, a transcript helps SEO only when it lives on a crawlable web page, pasting it into your app description does nothing for search and breaks the listening experience. Second, a wall of raw, auto-generated text with no structure is weak content. Google's spam policies target low-effort, scaled text with no added value, so a transcript should sit under a real summary and notes, not stand alone as the whole page.
Which one matters more for accessibility?
The transcript, clearly. A full transcript is the only one of the three that lets a deaf or hard-of-hearing person access the entire episode, and it's the layer screen-reader users rely on. Show notes give a sighted, hearing reader the gist; a transcript gives everyone the actual content. If accessibility is a requirement for you, the transcript is non-negotiable.
There's a discovery angle too, not just a compliance one. A transcript is searchable on your own page, translatable, and quotable, a listener can Ctrl-F for the exact thing they remember, copy a line into a post, or read instead of listen on a quiet train. Captions on your clips do the same job in short form: most social video is watched on mute, so the text on screen is the content for a large share of viewers. The transcript is the long-form version of that same idea.
Where does each one belong?
Each layer has one right home. The summary and full show notes, hook, timestamps, links, go in the RSS feed, because that text is what every podcast app pulls and displays. The transcript goes on your website episode page only, below the notes, where a browser can render it and a crawler can read it. It does not belong in the feed.
The reason transcripts stay out of the feed is mechanical. Apps truncate the description after a sentence or two on mobile, and a 6,000-word transcript pasted into that field buries your hook, bloats your feed file, and can break layouts in older players. Keep the feed lean: summary plus notes. Put the heavy text where a browser can render it and a crawler can read it.
A practical note on the feed itself: if you edit notes on your website but not in the feed source, apps keep showing the old text. The fix is to update the feed, not just the page, see managing your RSS feed without breaking it for how the two stay in sync.
How to make all three without tripling your work
You don't write three documents. You generate the transcript first, then carve the other two layers out of it. Auto-transcription gets you the full text in minutes; from there, the summary and notes are an editing job, not a writing-from-scratch job.
- Auto-generate the transcript. Most editing and hosting tools transcribe automatically. Treat the output as a draft, accuracy on names, jargon, and crosstalk needs a human pass, especially for the parts you'll quote.
- Pull the summary from the transcript. Read it back, find the single throughline, and write one to three sentences. This is your app-facing description.
- Build the show notes around the best moment. Use the summary as the opening, add timestamps and links, and lead with the line that made you sit up. The block-by-block method is in how to write show notes with a reusable template.
- Add timestamps once, reuse everywhere. The chapter markers in your notes can become clickable chapters in players, getting the formats right is its own small job, covered in adding chapters to your podcast.
- Publish the full transcript on the website page, below the notes. Format it with speaker labels and headings so it's readable, not a wall. Then make sure the episode reaches every directory it should, the distribution checklist covers where the feed needs to go.
Common mistakes (and the fix)
- Pasting the transcript into the description field. It buries the hook and breaks app layouts. Fix: feed gets summary + notes; transcript lives on the website page.
- Skipping the transcript to save time. You forfeit accessibility and a lot of long-tail search. Fix: auto-transcribe, do a quick review pass, publish it under the notes.
- Publishing a raw, unstructured transcript as the whole page. A wall of unedited text reads as low-value to both humans and crawlers. Fix: put a real summary and notes on top; add speaker labels and headings.
- Writing the summary before listening back. You can't name the best moment until you've heard it. Fix: transcribe first, then summarize.
- Letting the feed and website drift apart. Editing one and not the other means apps show stale text. Fix: update the feed source, then the page.
FAQ
Should I publish podcast transcripts? Yes, if you can, but on your website page, not in the feed. A transcript is the strongest accessibility layer you have and it catches long-tail searches your show notes never will. The cost is low: auto-generate it, do one human review pass for names and jargon, and publish it below your notes.
Do transcripts hurt SEO if they're auto-generated? Only if you dump raw, unstructured text as the entire page. A reviewed transcript sitting under a real summary and show notes adds value. A wall of unedited auto-text standing alone is the kind of low-effort, scaled content Google's spam policies are built to catch.
What's the difference between a summary and show notes? A summary is one to three sentences, the gist. Show notes are 150 to 300 words with a title, hook, timestamps, and links. The summary is your app-facing description; the show notes are the fuller version that lives in the feed and on your website.
Can I just use show notes and skip both summary and transcript? You can, and many shows do, but you give up two things. Without a tight summary, your app description may not survive truncation. Without a transcript, you lose accessibility and long-tail search. Show notes alone are the minimum; all three is the complete setup.
Where do timestamps go, notes or transcript? Notes. Timestamps are a curated set of five to eight chapter markers that help people jump to a topic and can become clickable chapters in players. A transcript is continuous text; you don't timestamp every line. Keep the chapter markers in the notes and let the transcript run.