The short answer: don't publish the transcript and call it a blog post. Pick the one argument the episode makes, title the post around the question someone would search for, turn the sub-points into headings, and use the best lines from the episode as evidence, with the context a reader needs added in. Embed the episode and link the transcript separately. From a 45-minute conversation, that is usually an article of 1,000 to 1,500 words that stands on its own.
A podcast episode is a long, spoken argument with a few detours. A blog post is a short, written one without them. That difference is why so many "podcast blog posts" are unreadable: they are transcripts with headings, and neither readers nor search engines have much use for them.
Done properly, the article is one of the most valuable pieces an episode can become. It reaches people who will never press play, it can rank in search for years, and it gives every episode a page worth linking to. This guide is the workflow, with an example outline from a real episode.
Why a transcript is not a blog post
A transcript has its uses. It is good for accessibility, and for the few people who want to find an exact line. But it reads badly as an article, for reasons that have nothing to do with how good the conversation was:
| Transcript | Blog post | |
|---|---|---|
| Structure | The order things were said | The order a reader needs |
| Length | Roughly 7,000 to 10,000 words for a 45 to 60 minute episode | Usually 1,000 to 1,500 |
| Focus | Every topic the conversation touched | One argument, with the detours cut |
| Language | Spoken: false starts, "you know", half-sentences | Written: complete, direct sentences |
| Context | Assumes you heard the previous ten minutes | Explains anything a new reader needs |
| Search | No clear topic for a page to rank for | Built around a question people search |
The job is not to tidy the transcript. It is to write a new piece, using the transcript as your research notes.
Step 1: choose the one idea
Most episodes contain one idea worth an article, sometimes two. Read the transcript, or your notes from recording, and ask: what is the single most useful thing a stranger could learn from this?
Good candidates are:
- A question the episode answers. "Why do big agency clients hurt margins?" is an article. "Agency growth" is a topic.
- A process someone walked through. Steps become headings almost by themselves.
- A position someone argued. A clear claim, with the reasons behind it, makes a strong article.
Then check the idea against how people search. Type the question into Google and look at the autocomplete suggestions and the "People also ask" box. You are looking for the words real people use. If your guest says "productised retainers" but everyone searches "how to package agency services", title the article in their words and use the guest's term inside it.
If an episode has two strong ideas, write two articles. Two focused posts beat one that tries to cover everything.
Step 2: outline from the transcript
With the idea chosen, go back through the transcript and pull out only what serves it. Note the timestamp of each moment you use, so you can check the exact wording later.
- Write the question as your working title.
- List the three to six sub-points that answer it. These become your H2 headings.
- Under each heading, note the evidence: a quote, a number, a story or an example from the episode.
- Mark the gaps. Anywhere the episode assumed knowledge, or skipped a step, the article needs a sentence of context.
- Cut everything else. The intro chat, the sponsor read, the tangent about the guest's holiday. It was fine on the show. It doesn't belong in the article.
Step 3: write for readers
Now write. The transcript is your source, not your draft.
- Answer the question in the first paragraph. Readers and search engines both reward a post that gets to the point. Say the answer, then spend the rest of the article explaining it.
- Turn speech into writing. Spoken language is full of restarts and filler. Keep the ideas and the voice, and write complete sentences.
- Quote sparingly and exactly. Use two to four direct quotes, chosen for the lines that are sharpest in the speaker's own words. Paraphrase everything else. Check each quote against the audio.
- Attribute everything. Make it clear what the guest said and what is your own view. A guest's point written up as the host's insight is a mistake they will notice.
- Add what the audio couldn't. Links to what was mentioned, a definition of the jargon, a table that summarises a comparison, a step-by-step list the guest described out of order.
- Keep your voice. If the article sounds like marketing copy, it has drifted from the episode. Read it aloud and cut anything you wouldn't say on the show.
Step 4: make it a page that can rank
A well-written article still needs a few basics to be found:
- A title that matches the search. Put the main phrase near the start and keep it under about 60 characters so it isn't cut off in results.
- A meta description of about 150 characters that says what the reader gets.
- Headings that answer sub-questions. Someone skimming only your H2s should understand the argument.
- The episode embedded, with a line inviting readers to listen to the full conversation.
- Links in and out. Link to the episode page, to one or two related articles on your site and to anything the guest mentioned.
- A clean URL, like
/blog/why-big-clients-hurt-agency-margins, not/episode-862. - The guest's name and company, spelled correctly. People search for them, and the guest will share a page that gets them right.
How to avoid thin and duplicate content
This is where podcast websites most often go wrong. An episode can easily end up with three pages saying the same thing: the host's episode page, a page of show notes on your site and a "blog post" that is the transcript again. None of them is clearly the best, so none of them does well.
Google's guidance is that it doesn't punish sites for duplicate content as such. It groups pages that are the same or nearly the same, and shows the one it thinks is best. The practical problem is that your pages compete with each other, and a page that adds nothing new is unlikely to be the one shown. Give each page a distinct job instead:
| Page | Its job | What it contains |
|---|---|---|
| Episode page | Get people to listen | Player, show notes, chapters, links, guest |
| Transcript | Accessibility and exact lines | The full text, on the episode page or its own page |
| Blog post | Answer a question for readers | One argument, written as an article, linking to the episode |
A few rules keep this clean:
- Never publish the same text twice on your site. If the transcript lives on the episode page, don't also publish it as a post.
- Make the article different from the show notes. Notes summarise the whole episode. The article develops one idea properly.
- If you republish elsewhere, on LinkedIn articles or Medium for example, publish on your own site first and link back to it.
- Don't publish an article for every episode just to have one. A short, generic post for an episode without a clear idea is exactly the thin content that doesn't rank. Write articles for the episodes that deserve them, and let the others be served by good show notes.
A real example outline
Here is how I would outline an article from episode #862 of Smart Agency Masterclass, where Jason Swenk talks to Charlie Clark, who runs an SEO agency, about client size and profit. The quotes come from the public pack for that episode on our community page, where you can read the transcript and check them.
The episode covers Charlie's origin story, early pricing, big clients, productising and team alignment. That is five topics. The article needs one idea, and the strongest one is the counterintuitive claim about client size.
Title: Why your biggest agency clients may not be your most profitable
Intro (answer first)
Big retainers look like big profit, but enterprise clients can squeeze
margins to almost nothing. Charlie Clark's agency now targets clients
in the 3 to 6k a month range, and here is why.
H2: The problem with big retainers
Quote: "I always used to think big retainer, big profit, but when you're
working with enterprise clients, they can squeeze your margins until
there's almost nothing left."
Context: what "squeezing margins" looks like (over-delivery, payment terms)
H2: Why mid-sized clients stay longer
Quote: "Our longest lasting clients aren't the biggest—they're the ones who
value consistency and stay with us for years at the 3 to 6k mark."
H2: Packaging the work so it stays profitable
Quote: "The sweet spot for us is predictable, packaged services—our team
knows exactly what to do, and the business runs smoother for everyone."
Add: a short list of what to standardise (SOPs, templates, scope)
H2: How to check your own client mix
Add: a simple table: client, monthly fee, hours, margin, years retained
(the episode argues the point; the article gives readers a way to act on it)
Close
One line on the full conversation, with the episode embedded
Notice what is left out: the origin story, the event announcement at the start and most of the pricing history. All good listening, none of it needed to answer the question. Notice too what is added: context the audio assumed, and a practical table the episode implied but never spelled out. That is the difference between an article and a transcript with headings.
A checklist before you publish
- The title is a question or claim someone would search for
- The first paragraph answers it
- Each H2 is one sub-point, and the H2s alone tell the story
- Two to four direct quotes, each checked against the audio
- Every point attributed to the person who made it
- Context added wherever the episode assumed it
- Episode embedded, and linked from the article
- No paragraph copied from the transcript or the show notes
- Links to what was mentioned and to related posts on your site
- Guest's name, role and company spelled correctly
Doing it by hand versus letting it run
By hand, an article like this takes a few hours: reading the transcript, choosing the idea, outlining, writing and checking the quotes. It is worth doing for your best episodes even if you do nothing else.
If you would rather start from a draft, PodRescale writes a blog article for every episode as one of its eleven specialists: a full post with headings and quotes, written from the transcript and in your voice, ready to edit and paste into your site. The same run writes the show notes and chapters, LinkedIn posts, clips, quote cards and the newsletter. Paste your RSS feed to try it on your last episode for free, no card. The how it works page shows the full pipeline, and pricing has the plans.
The article is one piece of the pack. The complete repurposing workflow covers the rest, and how to turn a podcast episode into a newsletter covers the other piece that is written for readers rather than the feed.
Frequently asked questions
Can I publish my podcast transcript as a blog post?
You can, but it won't work well as one. Transcripts are long, unfocused and written in spoken language, so they rarely hold readers or rank for anything specific. Put the transcript on the episode page for accessibility, and write the article as a separate, shorter piece.
How long should a blog post from a podcast episode be?
Long enough to answer its question properly, which for most episodes is 1,000 to 1,500 words. A deep, practical episode can support more. Don't pad it to hit a number. A focused 900-word article beats a padded 2,000-word one.
Will Google penalise me for duplicate content from my podcast?
Google doesn't penalise duplicate content as such. It chooses one version of near-identical pages to show. The real cost is that your pages compete and the weaker ones don't appear. Give the episode page, transcript and article different jobs and don't publish the same text twice.
Should the blog post and the show notes be the same page?
Usually not. Show notes summarise the whole episode for someone deciding whether to listen. An article develops one idea for someone who may never listen. For episodes without a strong single idea, good show notes on the episode page are enough.
Can AI write the blog post from my episode?
It can write a good first draft if it works from your transcript rather than a generic prompt, so every point traces back to what was said. Read it against the episode, check the quotes and cut anything that doesn't sound like you before you publish.
To create and check the draft in PodRescale, follow the podcast-to-blog screenshot walkthrough. It includes a worked outline and a free article brief.
Founder of PodRescale and a PhD in Data Science. Questions about this post go straight to him.
Follow on LinkedIn[email protected]