Blog / Digital growth /

Podcast SEO: show notes and transcripts that get found

A podcaster records a brilliant forty-minute episode on pricing for freelancers. Two guests, real numbers, proper disagreement. Then the episode page on their website says: “Episode 37 is live! Listen below.” One sentence and an embedded player.

To a search engine, that page is almost empty. Google doesn’t sit through the audio and decide it’s the best answer to “how should freelancers price their work”. It reads the page. And the page says nearly nothing.

That’s podcast SEO in one picture. The episode is the product, but the text around it is what gets found. Show notes and transcripts turn audio into something search can understand, link to and rank. The rest of this post covers how to write both so they’re worth reading, not just worth indexing.

Where podcast discovery actually happens

Most people find shows inside podcast apps and on YouTube, not through Google. That’s fine. Your website isn’t trying to replace those. It does a different job:

  • catching searches about the topic of an episode, from people who’ve never heard of the show
  • giving each episode a permanent, linkable home you control
  • collecting email sign-ups, which no podcast app hands you

It’s also worth not betting the strategy on any single app. Google has already said Google Podcasts is closing this year, with listeners pointed towards YouTube Music. Apps come and go. Your own site, with your own episode pages, stays.

Show notes: what goes on the episode page

Good show notes are a short article about the episode, not a teaser. Here’s the structure I’d use.

A title that names the topic

“Episode 37” tells a searcher nothing. “Episode 37: pricing your freelance work when clients push back” tells them exactly what they’ll get. Put the topic first if your theme or podcast host lets you; the episode number can come after. The same thinking from writing YouTube titles that get found without clickbait applies here: describe, don’t tease.

A summary that answers something

Two or three paragraphs at the top that say what the episode covers and what the listener will come away with. Write it so someone who never presses play still learns something. That’s the part Google is most likely to use to understand the page.

Key points or timestamps

A list of the main sections with timestamps does two jobs. Listeners can jump to the bit they want, and the page gains a clear outline of the subjects covered. Keep each line descriptive: “12:40, why day rates beat hourly rates for small projects” is better than “12:40, rates”.

Everything mentioned in the episode: books, tools, earlier episodes, the guests’ sites. Linking to your own earlier episodes is internal linking, and it helps both listeners and search engines move through your archive.

Who’s speaking

Guest names, what they do and a link to their work. If a guest is a known expert, that’s real experience and expertise on the page, and it’s the kind of detail people search for too.

Transcripts: useful, but not raw

A full transcript puts every word of the episode on the page. That’s a lot of relevant text, and it helps accessibility (people who are deaf or hard of hearing, people who’d rather read, people in a noisy place).

But a raw, auto-generated transcript is a mess. Filler words, speaker labels missing, names misspelt, technical terms mangled. Pasting that onto the page doesn’t do much for readers and doesn’t make the page look careful.

What I’d do instead:

  1. Generate it automatically. Most podcast hosts and plenty of tools will do a first pass.
  2. Fix the things that matter. Names, brands, technical terms and numbers. These are also the words people search for.
  3. Add speaker labels and paragraph breaks. A wall of text is unreadable.
  4. Add subheadings every few minutes of conversation. They make the transcript skimmable and give the page structure.
  5. Trim the worst filler. You don’t need every “um”. You do need to keep the meaning.

If the transcript is very long, put it below the show notes, or behind a “read the full transcript” toggle that’s still in the page’s HTML. Keep the summary at the top where readers see it first.

When an episode deserves its own article

Some episodes are good enough to become a proper blog post: an article written from the conversation, structured around the main question, with the episode embedded inside it.

This works best when an episode answers one clear question in depth. “How to price freelance work” can become a solid article that quotes the guests, adds a short checklist and links back to the full episode. A rambling catch-up episode can’t, and that’s fine. Not every episode needs to be an article.

I wrote about the same process for video in how to turn YouTube videos into blog posts. The method carries over almost exactly: find the question the episode answers, write for that question, and use the recording as the evidence.

The technical bits worth checking

  • One page per episode, with its own URL. Not just a single “podcast” page with a player that lists everything.
  • The player shouldn’t slow the page down. Embedded players can be heavy. Load them lazily or use a lightweight embed where you can.
  • Mark it up. Article structured data for the episode page is a sensible start; schema for blog posts covers the basics.
  • Add episodes to your sitemap like any other post, and link new ones from the homepage or podcast archive so they don’t sit orphaned.

A simple routine per episode

  1. Publish the episode page the same day the episode goes live.
  2. Write the topic-first title and the summary before anything else.
  3. Add timestamps and the resources list.
  4. Clean up and add the transcript within the week.
  5. Pick the one or two strongest episodes each month and turn them into full articles.

FAQ

Do podcast transcripts help SEO?

They can, because they add relevant text that search engines can read. They help most when they’re cleaned up and structured. A raw automatic transcript adds words but not much quality.

Should show notes be long?

Long enough to answer what the episode is about and what someone will learn. A few hundred words plus timestamps and links is a reasonable start. Length for its own sake doesn’t help.

Will this replace getting listeners from podcast apps?

No. It adds a second way in: people searching for the topic who don’t know the show exists yet.

Pick your best episode from the last three months and rewrite its page tonight: a topic-first title, a real summary and timestamps. Does the page now explain the episode to someone who never presses play?