How to Write Podcast Show Notes (Templates + AI Workflow)

Show notes do three jobs at once: they convince a browsing listener to press play, they help an existing listener find that link or quote from minute 43, and they give search engines the text that audio can't provide. Most shows fail at all three with the same two-sentence summary — not because writing notes is hard, but because writing them from scratch after every episode is the kind of chore that dies by week six. The fix is structural: a fixed template, filled from the transcript, drafted by AI, reviewed by you.

What good show notes contain

The reliable template, top to bottom:

• Hook paragraph (2–3 sentences). Not a summary — a reason to listen. Name the payoff: what the listener will know or feel at the end.

• Guest intro, if there is one: who they are and why they're worth an hour.

• Timestamped chapters. 5–10 moments with times — the single most-used element for returning listeners, and players increasingly surface them as navigation.

• Key takeaways. 3–5 bullets of substance. This is what gets skimmed, quoted, and screenshotted.

• Links and resources mentioned in the episode — the thing listeners actually come back for.

• Pull quote — one strong sentence, quotable as-is.

• Calls to action: subscribe, review, the next episode to try.

The AI workflow: from audio to draft in minutes

1. Transcribe the episode. Upload the audio (or paste the episode link) into a transcription tool and get a speaker-labeled, timestamped transcript. Everything downstream depends on this file — the full episode workflow is in our podcast transcription guide.

2. Fix names once. Guest names, product names, jargon — correct them in the transcript and every artifact inherits the fix.

3. Generate against your template. A transcript summarizer drafts the hook, takeaways and chapter list from the transcript. Timestamps come from the transcript's timeline, so chapters land on real moments.

4. Review as an editor. Sharpen the hook (models write serviceable, you write specific), verify the timestamps hit the right beats, check every link, pick the pull quote a human would actually share.

5. Ship everywhere. Full notes to your site, a tightened version to the podcast apps (players truncate — front-load the hook and links), chapters wherever your host supports them.

Show notes vs transcript vs episode page

These are three different artifacts, and shows that conflate them lose value:

Publishing the transcript alongside the notes is the underused half: it makes every sentence of the episode searchable — the reason transcripts matter for discovery, which we dig into in our piece on podcast SEO.

What to skip

• The blow-by-blow summary. "First we discuss X, then we move on to Y…" serves nobody — takeaways beat chronology.

• Keyword stuffing. Notes written for robots read like notes written for robots. The transcript already gives search engines the vocabulary; let the notes be for humans.

• Unreviewed AI output. A generic AI summary is better than nothing and worse than five minutes of your judgment. The draft is the floor, not the ceiling.

A worked example

Here's the template filled for a fictional interview episode, written the way the notes would actually ship to the apps:

Episode 47 — Anna on starting a studio with three clients and one room

Anna opened her recording studio in 2019 with three clients, a rented room in Kreuzberg and no business plan. Five years later it's a team of six. This episode is about the unglamorous middle: the year she almost quit, the pricing mistake that cost her a client, and the one habit she credits for surviving it.

Chapters
02:14 — Why she left a safe job
09:40 — The first three clients (and how she found them)
18:05 — The pricing mistake
27:30 — The year she almost quit
38:50 — Hiring the first person
46:10 — What she'd tell episode-one Anna

Key takeaways
• Charge for the outcome, not the hours — her margins doubled after one pricing change.
• The first clients came from one referral, not from marketing.
• "Buy the cheap mic. Publish anyway."

Links: Anna's studio · the pricing template she mentions · our episode with her first client

If this one helped, leave a review — it's how new listeners find the show. Next week: the editor who cut this episode.

Notice what's absent: no chronology, no "in this episode we discuss". Every line either sells the listen or serves navigation.

Where the notes go, and what each destination wants

• Podcast apps (Apple, Spotify and the rest). They read the episode description from your RSS feed. Apple's guidelines for creators live at Apple Podcasts for Creators; the practical constraint is truncation — the first two lines do the selling, links belong near the top, and heavy formatting gets flattened.

• Your episode page. The full template plus the transcript. If your host supports the open podcast namespace, the transcript can also ride along in the feed as a podcast:transcript tag, which lets apps show it natively.

• YouTube (video or audiogram episodes). Paste the chapter timestamps into the description and YouTube turns them into navigable chapters — the rules are in its chapters help page: the first timestamp must be 00:00, at least three chapters, each ten seconds or longer.

• Newsletter and social. The hook paragraph and the pull quote are already written — reuse, don't rewrite.

Frequently asked questions

How long should show notes be?

App-facing notes: a tight 100–200 words before the fold, links early. Episode page: as long as usefulness sustains — template sections plus transcript. Length is a byproduct, not a target.

Should I publish the full transcript in the show notes field?

No — apps truncate and it buries your links. Notes in the apps, transcript on the episode page, each doing its job.

Can AI write show notes directly from audio?

That's exactly the transcribe-then-generate workflow — the transcript is the intermediate that makes the output checkable. Correct the transcript, and the notes, chapters and quotes all inherit the accuracy.

Do timestamps/chapters matter for SEO?

They matter most for listeners, which is the metric that compounds. Structured chapters also feed player features and keep people on the episode longer — indirect but real.

The bottom line

Fix the template once, let the transcript do the drafting, and spend your ten minutes as editor-in-chief instead of stenographer. Shows that ship real notes every week aren't more disciplined than you — they've just stopped writing them by hand.