Ask podcast hosts why they skip show notes, and you get three answers. First: "I don't have time after the edit is done." Second: "Nobody reads them anyway." Third: "My hosting platform has a description field and I just put a few sentences there."
All three are understandable and all three are worth questioning.
Why show notes actually matter
Podcast audio is not indexed by search engines. The text content associated with an episode -- the title, the episode description, the full show notes -- is what gets indexed. If you are trying to be discoverable by anyone who is not already a subscriber, the text content is your primary surface.
A two-sentence description does not give search engines much to work with. A proper set of show notes with guest name, key topics, timestamps, and resource links gives search engines a rich text document to index. That is what shows up in results when someone searches for the topic your episode covered.
Show notes also serve the listener who is already subscribed. Most podcast apps surface the episode description before play. A listener scrolling through their feed deciding what to listen to during a commute is making a decision based on that text. The title gets them interested; the description converts or does not.
Finally, show notes are the permanent web page for an episode. When someone links to your episode from a blog post, shares it in a forum, or references it in a newsletter, they are linking to a URL that may or may not have useful content on it. An episode with a well-written show notes page gives link-followers something to read even before they decide to listen.
The real reason hosts skip them
The workflow problem is real. Show notes feel like an addendum. The recording is done, the edit is done, you exported the file, you are done with this episode -- and now there is one more task. It is a cold start. You have to open a blank document, remember what the episode covered, and write something from scratch while your brain is already moving on to the next thing.
That cold start cost is the actual problem. The content of the show notes is not hard to write. You covered the topic. You know what was said. The problem is that by the time you get to writing them, the episode is stale in your memory and the activation energy to start is high.
The workflow that makes it twelve minutes
The fix is to collect the material for show notes during the recording, not after.
Keep a notes document open while you record. As you move through the conversation, jot down the topic transitions and rough timestamps. Do not write full sentences -- just capture the signposts. "14 min -- guest background, how they got into the field." "28 min -- discussion of the problem with X, their contrarian take." "45 min -- specific recommendation they make."
For interview episodes, write three bullet points about what you expect to cover in the first five minutes before the recording starts. You will deviate from them; that is fine. The act of writing pre-interview notes means you already have a skeleton for the show notes intro before you have recorded anything.
After the edit is done, you have a timestamp skeleton and three intro bullet points. The work remaining is: write a two-paragraph intro that covers why this episode and why this guest, expand the timestamp notes into one-sentence descriptions, and add any resource links the guest mentioned. This process takes 12 to 15 minutes, not an hour.
The one-hour version happens when the notes are started after the edit on an episode the host has already mentally filed away. The 12-minute version happens when the raw material was captured during the process.
What good show notes contain
For interview episodes: a two-to-three sentence intro identifying the guest and the central topic, a timestamp breakdown of the conversation (one line per major topic, time included), any resources, books, tools, or links the guest mentioned, and a CTA to subscribe or leave a review.
For solo episodes: the central argument or thesis of the episode in two sentences, three to five bullet points covering the main points made, and any resources referenced.
Neither format requires extensive writing. The timestamps are the most useful single element -- they are what listeners use to navigate longer episodes and what search engines use to understand the structure of the content.
The "nobody reads them" argument
Show notes readership is hard to measure directly, because most podcast hosting analytics do not report on show notes page views separately from episode plays. The claim "nobody reads them" comes from the absence of evidence rather than evidence of absence.
What is measurable: podcasts with detailed show notes rank in search results. Podcasts with minimal show notes generally do not, for topics where search volume exists. If discoverability matters to your show, the text content you associate with each episode is one of the few levers available. Audio alone will not get you there.
On the hosting platform description field
Most hosting platforms surface the episode description field in two places: in the app listing (usually 2-3 sentences truncated) and as part of the RSS feed. Some platforms have a separate full-content field. If your platform supports longer show notes, use them. If it only has a description field, put more than a sentence or two in it.
A practical middle ground: a short description (2-3 sentences, designed for the truncated view in apps) plus a longer section with timestamps below a "read more" or "full notes" break. Both audiences are served: the app-listing skimmer and the listener who is already engaged enough to look for more.
