A good podcast episode is full of ideas and quotable lines, all locked inside audio. Search engines can’t read it, skimmers won’t sit through it, and it slips down your feed a week after it airs. If you want to turn a podcast into a blog post, the work is mostly in two steps: get the words out as text, then shape one part of the conversation into something written to be read.

This guide walks through that process from start to finish, then shows how to stretch one episode into a week of content without it feeling recycled.

The short version

To turn a podcast episode into a blog post:

  1. Get a transcript of the episode from its Spotify or Apple Podcasts link, or from the audio file.
  2. Pick one angle. Choose the single idea from the episode that would make the best article.
  3. Draft it. Write from the transcript, or use the Blog Post option on the transcript page for a first draft.
  4. Edit it properly. Add headings, a few direct quotes with timestamps, links, and your own voice.
  5. Publish and link the post and the episode to each other.

Why turn a podcast into a blog post

  • Search. People search for answers in text. A written post can rank for the questions your episode answers, while the audio itself can’t be read.
  • Reach. Plenty of people won’t press play on a 60-minute episode but will read a 5-minute article, and some of them become listeners.
  • Shelf life. Episodes fade from feeds quickly. A useful article keeps getting found long after.
  • Accessibility. Text helps deaf and hard-of-hearing readers, people reading in a second language, and anyone who can’t listen right now. (For accessibility, publish the full transcript too. A blog post is a summary, not a substitute.)

Step 1: Get the transcript

Everything starts from an accurate transcript. Retyping an hour of conversation takes hours; AI transcription takes minutes.

  • If the episode is public on Spotify, paste the episode link into the Spotify transcript generator.
  • If it’s on Apple Podcasts, use the Apple Podcasts transcript generator. The link should contain ?i=, which points to one episode.
  • If you have the raw recording (an unpublished episode, a file from your editor, or a show that isn’t public), use the file upload option. It takes MP3, M4A, WAV and other common audio and video formats, up to 6 hours and 500 MB.

You’ll get a full, timestamped transcript you can copy or download as TXT or PDF. For more on the options, see how to convert a podcast to text.

Step 2: Pick one angle per post

This is the step most people skip, and it matters most. A good conversation wanders; a good blog post doesn’t.

Read through the transcript, or skim the AI summary on the result page, and look for:

  • A question your listeners actually ask. “How do I price my first freelance project?” makes a better post than “Episode 47 recap”.
  • A story with a clear lesson, or a surprising opinion.
  • A how-to the guest explained step by step.

Pick one. If the episode has three strong ideas, that’s three posts, not one long one.

Step 3: Draft it

You can write the draft yourself from the transcript, or get a head start. On the transcript page, the Blog Post repurpose option turns the transcript into a long-form first draft with a title, headings and a structure to work from. It costs 1 credit.

If the episode covers several topics, use the AI chat on the same page to ask for a blog post about just your angle.

Treat it as a first draft. It gets you past the blank page, but it doesn’t know your audience or your opinions.

Step 4: Edit it into a real post

  • Lead with the answer. Readers and search engines both reward posts that say the useful thing early.
  • Add structure. Clear ## headings, short paragraphs, and lists where the content is a list.
  • Use real quotes. Pull two or three of the best lines straight from the transcript. Use the Search transcript box to find them and check each one against the audio before you publish. See how to find a quote in a podcast for more.
  • Add timestamps. “Listen to this part at 23:14” gives readers a reason to press play.
  • Credit your guests. Name them, describe who they are, and link to their site or work.
  • Add links to the episode, related posts, and anything the episode mentions.
  • Add your voice. Context, a disagreement, an example from your own work. This is what makes it worth reading.
  • Cut the filler. Spoken language is full of repetition and tangents. Written language shouldn’t be.

Step 5: Publish and connect it

Embed the episode player in the post, and link from the episode’s show notes back to the post. If you’re writing show notes too, how to write podcast show notes from a transcript covers that separately.

One episode, a week of content

The same transcript can feed every channel you use. The transcript page has repurpose options for an X thread, LinkedIn post, email newsletter, FAQ, YouTube description, Reddit post and Instagram caption, each 1 credit. A simple plan:

  • Monday: blog post. The strongest single idea from the episode, fully written up.
  • Tuesday: LinkedIn post. One lesson or story, told in the first person.
  • Wednesday: X thread. Five to eight takeaways, one per post.
  • Thursday: email newsletter. A short take on the episode, linking to the blog post and the episode.
  • Friday: FAQ. The questions the episode answered, added to the blog post or the episode page.

If the episode is also on YouTube, generate its description from the same transcript. Edit each piece like you edited the blog post.

Mistakes to avoid

  • Publishing the raw transcript as a “blog post.” A transcript is useful on the episode page, but it isn’t an article. It has no headline answer, no structure and lots of filler.
  • Publishing the AI draft unedited. Readers can tell.
  • Cramming the whole episode into one post. One angle per post reads better and is easier to find in search.
  • Missing attribution. If a guest said it, credit them by name. Never present a guest’s idea as your own.
  • Misquoting. Speech-to-text can mis-hear names and numbers. Check quotes against the audio.

Common questions

Is a podcast transcript a blog post?

No. A transcript is a record of what was said, and it’s worth publishing on the episode page for accessibility and search. A blog post is written to be read: it picks an angle, leads with the answer and cuts the tangents. The best approach is to publish both and link them.

Will publishing the transcript and a blog post count as duplicate content?

Not if the post is a real rewrite. A post built around one angle, in your own words with a few quotes, is different text from the full transcript. Avoid publishing the same text on several pages. If you do post the transcript, keep it on the episode page and link to the post from there.

How long should a podcast blog post be?

As long as it takes to cover one angle well. For most single-topic posts that’s somewhere around 800 to 2,000 words. A focused 900-word post is better than a padded 3,000-word one.

Is it OK to use AI to turn a podcast into a blog post?

Yes, as long as the result is useful. Google has said it judges content on whether it helps readers, not on how it was produced. Use the AI draft for structure and speed, then add what only you can: your opinion, your examples, accurate quotes and edits for your audience.

Is it free?

Podcast transcription and file uploads are part of the Plus and Pro plans, because they process full-length audio. They cost 10 credits per hour of audio, so an hour-long episode is 10 credits. Each AI action, like a blog post draft or a LinkedIn post, is 1 credit. See the credits page for plan details.

Start with the transcript

Every format in this guide starts from the same place: the words from your episode, as text. Paste a public episode link into the Spotify transcript generator, pick your angle, and you’ll have a first draft to edit in minutes.