How to Write Great Podcast Show Notes (The Template I Use)

The short version: great show notes aren't a summary for people who already listened, they're a sales page for people who haven't pressed play yet, written for humans and search engines at the same time. Aim for 300 to 500 words, three to five timestamps, one pull quote, and links that go somewhere useful. Do that consistently and your back catalogue keeps working for you long after the recording light goes off.

Who really reads your show notes

Here's the bit most guides skip. Your listeners don't read your show notes. They listened, they know what happened, why would they go and read a text version of a thing they already heard? The people reading your show notes are almost entirely people who haven't listened yet: someone scrolling a podcast app deciding between your episode and three others, someone who found you through a Google search for a phrase your guest said, or an AI tool trying to work out what your episode is about so it can recommend it.

Once you accept that, everything changes. You stop writing show notes like meeting minutes ("in this episode we discuss...") and start writing them like a trailer. You're persuading a stranger to spend 40 minutes of their day on you. That's a bigger ask than most podcasters treat it as.

My own show notes disaster

I learned this the slow way. Years ago I recorded a weekly episode where the guest, a brilliant operations consultant, spent 35 minutes on a single idea: how most small businesses lose money through "invisible admin", the tasks nobody schedules or bills for. I wrote the show notes in about four minutes flat, something like "In this episode I talk to [name] about business efficiency and admin". It went out. It got the usual 40 or so downloads on launch day from people who already follow me.

Two years later I rewrote the notes, gave them a real title mentioning "invisible admin costs", pulled a direct quote from the guest, and added three timestamped sections. That single page has brought in around 1,200 downloads since, and the vast majority of that traffic never followed me on anything. They found the page through search, read the notes, decided the episode was worth their time, and pressed play. The audio didn't change. The notes did. That's the whole lesson in one story.

The step-by-step template I use now

This is the exact process, in order, that I run for every episode now, whether I'm the host or I've just done a guest slot worth writing up (like when I sat down for episode 78 of the Expert In Demand Podcast, where the honest headline was that I hate social media, and the notes had to earn that click on their own).

• Step 1: Write the title as a promise, not a description. "Episode 42 with Sarah Jones" tells nobody anything. "How Sarah Jones Cut Client Churn by 30% Without Hiring Anyone" tells them exactly what they get.
• Step 2: Open with two sentences that could stand alone. If someone reads nothing else on the page, these two sentences need to sell the episode. State the problem the episode solves and the one thing the listener walks away with.
• Step 3: Write a 300 to 500 word summary. Not a transcript, not a full recap. Three or four short paragraphs covering the shape of the conversation: what was discussed, what was disagreed on, what surprised you as the host.
• Step 4: Add three to five timestamps. Real ones, tied to specific moments, not vague sections. "12:40 Why most founders underprice their first product" beats "Middle of episode: pricing".
• Step 5: Pull one direct quote. Something the guest said, word for word, in quotation marks. This is the single most shared, most clicked element on any show notes page I've written.
• Step 6: Add a two to three sentence guest bio with one credible detail. Not their whole LinkedIn history. One thing that proves they know what they're talking about.
• Step 7: Link out with intent. Link to anything the guest mentioned by name, link to related episodes on your own site, link to your guest's own work if it's relevant.
• Step 8: Add a call to action that isn't "subscribe". Ask them to reply with a question, download something, or listen to a specific related episode next.

Do that eight step process and you're looking at 20 to 30 minutes of work per episode once you've done it a few times. I've timed myself. It's rarely faster than 15 minutes and rarely slower than 35, and the return on that time compounds for years, unlike the episode itself which gets most of its downloads in the first 72 hours.

What goes wrong most often

The most common mistake I see, on shows with good production and good guests, is pasting the auto-generated transcript in as the show notes and calling it done. A transcript is not show notes. Nobody reads 6,000 words of "um, so, yeah, I think what's interesting there is..." to decide whether to listen. It also does nothing for search, because Google and AI answer engines are looking for structure and clarity, not raw speech-to-text.

The second mistake is writing show notes that give away the ending. If your two opening sentences and your summary tell someone the full answer to the problem, why would they need the audio? Good show notes create a gap. They tell you what's discussed and why it matters, they don't hand you the punchline.

The third mistake, and this one's uncomfortable to admit, is that most podcasters write show notes for their own ego, not their listener's decision making. They list every topic touched on, every tangent, every joke, because it feels thorough. Thorough isn't the goal. Persuasive is.

Timestamps, quotes and links that make people click

Timestamps work best when they read like a contents page for a useful article, not a diary. Compare "05:00 intro, 10:00 background, 20:00 main discussion" with "05:12 The one hiring mistake that cost her £40,000, 18:30 Why she fired her biggest client on purpose". The second version sells three separate reasons to click play, even if someone skips everything else on the page.

Quotes need to be exact. I keep a rough transcript running while I record (most podcast hosting tools, including Spreaker, will generate one automatically) purely so I can scan it afterwards and lift the two or three lines that sound sharpest out loud. A quote that sounds punchy spoken doesn't always read well written down, so I'll tidy the grammar slightly but never change what was said.

Links should never be decorative. If your guest mentioned a book, link the book. If they mentioned a stat, link the source of the stat if you can find it (a proper study, a government report, something with real authority, not another blog). If you've covered a related theme before, for instance if the episode touches on how you go about choosing guests in the first place, link that too. Every link is either helping the reader or wasting their trust, there's no neutral link.

SEO for show notes without sounding like a robot wrote them

Show notes are, quietly, one of the best SEO assets a small podcast has, because they're written text about spoken content that would otherwise be invisible to search engines entirely. The trick is writing the phrase your listener would search, not the phrase your guest used. If your guest talked for ten minutes about "operational drag" but nobody searches that phrase, and everybody searches "how to reduce business overheads", use the second phrase in your heading and your opening sentence, then let "operational drag" show up naturally further down as the guest's own words.

I've had single episode show notes pages outrank entire competitor blog posts on the exact same topic, purely because the show notes had a real quote, a real name, and a specific number in the first 100 words, while the competing article was generic advice with no source behind it. Specificity beats polish here almost every time.

How long should show notes be

Under 150 words and you've written a caption, not show notes, it won't rank and it won't sell the episode. Over 800 words and you're writing an article that happens to reference a podcast, which is fine as a separate long-form piece but isn't show notes anymore. The sweet spot, from testing this across dozens of episodes, sits between 300 and 500 words for the core notes, with timestamps, quote, and bio sitting outside that word count as their own distinct blocks.

If you're just getting your show running and haven't settled on a format yet, it's worth reading through a proper step-by-step guide to starting a podcast before you lock in a show notes template, because your format (solo show, interview show, co-hosted) changes what your notes need to do. A solo hosted show needs notes that sell your own argument, an interview show needs notes that sell the guest.

Writing this well, every single week, for months on end, is tedious, and it's exactly the kind of repetitive, template-driven writing task I get asked about most when I work directly with founders as an AI consultant for small businesses, because a good process plus a well-trained AI drafting tool can take that 30 minute job down to 10 without losing the specificity that made it work in the first place.

The last thing worth saying

Nobody's show notes are going to save a boring episode. If the conversation itself was flat, no amount of clever timestamps fixes that. But a good episode with lazy show notes is the more common problem, and it's the cheaper one to fix. You already did the hard part when you recorded it. Spend the extra 25 minutes making sure someone who's never heard of you has a reason to click play.

Frequently asked questions

How long should podcast show notes be?

Aim for 300 to 500 words for the main summary, with timestamps, a pull quote, and a short guest bio sitting outside that count as separate elements on the page.

Should I just publish the automatic transcript as my show notes?

No, a transcript is not show notes, it's raw material; nobody reads 6,000 words of unedited speech to decide whether to listen, and it does very little for search compared with a written summary that has real structure.

Do show notes help with SEO?

Yes, they're often the only written text search engines can index for an episode, and specific details like real quotes, guest names, and numbers tend to outrank generic advice articles on the same topic.

What's the most common mistake in podcast show notes?

Writing them as a list of every topic covered rather than a short, persuasive summary aimed at someone who hasn't listened yet; thoroughness isn't the goal, getting someone to press play is.