Turning a Podcast into Blog Articles with AI: A Complete Method

This article is part of the series "Rebuilding a Website with AI". Previous episode: How to Make a Next.js Site Multilingual.
A Treasure Trove of Dormant Content
Since 2021, I've been producing the Tech Culture Network (TCN) podcast. 13 episodes, 3 seasons, conversations with Swiss entrepreneurs, developers and creatives: Mélanie Burnier, Théo Fischer, Fabien Favre, Sophie de Quay, Steve Louissaint, David Narr, and many others.
Each episode runs between 30 and 60 minutes. That's hours of rich content, insights on entrepreneurship, tech, and startup culture in Switzerland. And on my website? Nothing. A handful of existing articles with a two-line summary and a link to the podcast. A monumental waste in terms of content and SEO.
8 New Articles Written in French
For episodes that didn't yet have an article, Claude Code worked from the audio transcripts. No simple copy-paste of the transcription. Each article was structured like a proper blog post: an introduction of the guest with their background and the relevance of the conversation, the 3 to 5 key ideas that emerge from the episode, standout quotes that capture the guest's thinking, context and perspective relative to the Swiss tech ecosystem, and a call to action with the link to the full episode.
The articles for Battista Ravanne, David Narr, Luis Gutierrez, Marine Doll, Sergio Attanasio, Sophie Cuendet, Steve Louissaint and Thibaut Jaime all received the same editorial treatment.
Revamping Existing Articles
The older articles (Elisa Vanrullen, Florian Bourqui, Théo Fischer and others) had a minimal format. Claude Code reworked them to enrich the content with more details drawn from the transcripts, standardise the format with the new articles, add missing metadata (category, id, canonicalUrl) and fix the frontmatters for compatibility with the new multilingual system.
Translation into English and Portuguese
Each article was then translated into English (21 .en.mdx files) and Portuguese (21 .pt.mdx files). Not word-for-word via Google Translate, but genuine localisation that adapts idiomatic expressions, cultural references, tone (more direct in English, more narrative in French) and formatting conventions.
Three complete versions of each article, each with its own dedicated MDX file.
A Specialised Agent for the Future
The bonus: Claude Code created a BMAD agent (podcast-article-writer), a reusable template that defines exactly how to turn a podcast transcript into a blog article. Format, tone, structure, metadata — everything is codified. For upcoming episodes, the process will be even faster.
The Tough Question: Is It Actually Good?
My honest answer: these are excellent first drafts. The structure is solid, the information is accurate (it comes directly from the transcripts), and the tone is professional.
What did I need to adjust? The personal nuances when I know the guest and want to add an anecdote that the transcript alone doesn't capture. The editorial tone, sometimes too neutral, where I injected more personality. And a few factual details like verifying dates, job titles and company names.
But the time-to-quality ratio is unbeatable: rather than spending 2 to 3 hours per article writing from scratch, I spent 15 to 20 minutes per article refining. Multiply that by 50 articles and the maths speaks for itself.
The Numbers
In total, 8 new articles in French, 5 existing articles revamped, 21 English translations, 21 Portuguese translations — that's 50 MDX files created with 12 associated images added.
The SEO Impact
50 new indexable articles means 50 new entry points from Google. Long-tail keywords on niche topics like Swiss entrepreneurship, tech culture or Romandy startups. Content in 3 languages targeting different audiences. And internal links that strengthen domain authority.
The blog went from a handful of articles to a genuine content library in a single afternoon.
Tomorrow, we switch gears. No more content, no more translations. We're talking pure code: how Claude Code created complete new landing pages with interactive components and structured data, without me writing a single line. This is where things get truly impressive.

Toni Dias
Full-Stack Developer at AsuOs
Related articles

How to Make a Next.js Site Multilingual with next-intl: A Real-World Experience
Taking an entire Next.js site to 3 languages (FR, EN, PT) with next-intl, without breaking everything. Route migration, 1,155 translation keys, multilingual slug management. All done in 2 hours thanks to Claude Code. Episode 2/7.

Rebuilding a Website with AI: My Experience with Claude Code
40 commits, 185 files, 14,500 lines of code. In 8 hours of work, Claude Code transformed asuos.ch from top to bottom. First episode of a series where I tell you everything, unfiltered.
Ready to transform your digital business?
AsuOs supports you in your digital strategy with tailored solutions.