CHRISTINE Give Every Episode a Second Life in Search
Podcast To Blog reads a full episode transcript, finds the one question that episode answers better than anything else on the internet, and writes the post in your spoken words — word for word — structured the way people actually ask AI.
← Back to the Skills LibraryInstalled in under a minute. No tech skills required.
You don't need to know how to code, and you don't need to set anything up. There are two blocks below. If you can copy and paste, you can install this.
Paste the instruction
Copy the first block and paste it into a brand-new Claude conversation. Don't hit send yet — it's the note that tells Claude what to do.
Paste the skill underneath, then send
Copy the full skill block and paste it right below the instruction. Send it. Claude builds the skill, personalizes it to your business, and confirms when it's ready.
Install the skill below for me. Keep the skill text exactly as written, then personalize its defaults from what you already know about me — my business, my voice, my priorities, and the places I keep my notes and files. Confirm when it's installed and show me exactly how to run it.
--- name: podcast-to-blog description: Turn any recorded podcast episode into an AEO-optimized, publish-ready blog post that keeps your spoken voice word for word. On first run the skill interviews you to wire in your podcast host, your blog, and your language, then runs your version every time after. Use whenever you say "podcast to blog," "turn this episode into a blog post," "publish episode [number] as a post," or drop an episode transcript and want it turned into a post. --- # Podcast to Blog: Episode Intelligence Publisher Turn a recorded podcast episode into an AEO-optimized blog post that reads like you talking, structured for how people ask AI. Every post keeps your spoken voice, answers one clear question better than anything else on the internet, and passes an AEO audit before it ships. This is your episode, structured to get found and cited. ## First Run: Design Your Version The first time you run this skill, set it up. Ask me these questions one at a time, save my answers into this skill file as a CONFIG block, and use them on every run after this. If the answers are already saved, skip straight to the workflow. 1. What do you use to host and record your podcast, and how do you get transcripts? (Zoom, Riverside, Descript, a transcription tool, or a transcript you paste.) This tells me how to get the episode text. 2. Where does your blog live, and how does it publish? (WordPress, Ghost, Webflow, a static site in a git repo, or a CMS.) This is where the finished post lands and how it goes live. 3. Whose voice should the post be written in, and which signature phrases should stay word for word? Name the host and list the phrases to preserve. This keeps the post in your own spoken voice. 4. Where do you track your episodes and content? (A Notion database, a spreadsheet, a content calendar, or a folder.) This is where I read the episode from and mark it published. 5. What is your podcast called? I use this in the episode attribution line at the bottom of every post. If I ever say "redesign podcast to blog," run this interview again. ## Input - An episode name or number from wherever you track content (I pull the transcript) - A pasted transcript - "Publish the next episode in my queue" (I find the next episode marked ready) ## Workflow ### Step 1: Get the Episode Pull the transcript from the host or tracker you set up, or use the one you paste. Grab the episode title, number, publish date, audio URL, description, and any keyphrases already mapped. If the transcript is empty or the episode is not marked ready, skip it and move to the next one. ### Step 2: Find the One Big Idea Read the full transcript. Identify the single most valuable idea by answering this question: "What is the single question this episode answers better than anything else on the internet?" That question becomes the angle for the whole post. Everything else in the transcript is supporting material. Pick the idea with the highest combination of specificity, actionability, and searchability. A named framework the host teaches wins first. A concrete, do-it-now insight wins next. A mindset shift that reframes the topic wins after that. A story carrying a clear lesson wins last. When several strong ideas compete, choose the one a listener would actually type into AI. ### Step 3: Preserve the EEAT Voice This is the part that makes the post impossible to fake. From the transcript, pull and keep: - Exact phrases and signature language the host uses, word for word - Specific stories and moments, with real names and identifiers removed - Real numbers and data points the host cites - Analogies the host uses to make hard ideas simple - Challenge language where the host speaks straight to the listener Use these as close to spoken as possible while they fit a written post. Do not paraphrase the host's raw language into polished prose. The spoken words are the content. The structure organizes the thinking. It never replaces the voice. ### Step 4: Write the Post Follow this template exactly. Every element is required. **Title (H1)** - Include the primary keyphrase naturally - Refine the episode title if a cleaner version reads better - Conversational. A question or a bold statement both work. - Skip colon-based titles **Key Takeaways Block** - 3-5 bullets summarizing the key takeaways, placed right after the title and date - These are the first 200 words AI reads, so make them count - Each bullet is a standalone insight that delivers value on its own **Opening (3 sentences max)** - Lead with what the reader gets: the framework, the insight, the actionable thing - Skip the backstory about the show or the episode - Within 3 sentences the reader knows exactly what this post delivers and why it matters to them - Open with a confident declaration that stakes a position **Question-Based H2 Sections (4-6)** - Each H2 is phrased as a question someone would ask AI - CRITICAL: a bold direct answer leads the first 1-2 sentences after every H2. This is what AI extracts for citations. Give the definitive answer in bold before any story or depth. - Then go deep with the host's stories, exact spoken language from the transcript, specific examples, and steps - Each section stands alone. If AI pulls only this section, it fully answers the H2 question. **H3 Sub-sections (where the framework needs them)** - If the episode teaches a framework with named parts, each part gets its own H3 with real depth - Use the host's transcript language for each one **Closing Section** - One H2 like "Where Do You Start?" with a bold direct answer - Specific actions the reader can take this week - Pull the host's exact challenge language from the transcript if they gave one **Episode Attribution Line** Always end the body with a line like: *This post is adapted from Episode [NUMBER] of [your podcast name]. [Listen to the full episode here.](AUDIO_URL)* ### Step 5: Score Against the AEO Audit Scorecard Score the draft against all 25 criteria. Total: 100 points. Target: 85+. **AEO Structure (25 points)** - Question-based H2 headings matching real search queries (5 pts) - Bold direct answer leading every H2, within the first 40 words (5 pts) - Key takeaways or summary at the top (5 pts) - Clear hierarchy with proper H1, H2, H3 tags (5 pts) - 1,500+ words of substantive content (5 pts) **EEAT Signals (30 points)** - First-person lived experience with real stories (6 pts) - Specific examples with real numbers and data (6 pts) - Original frameworks or methodology referenced (6 pts) - Real conversations, anonymized (6 pts) - Depth of expertise evident throughout (6 pts) **Answer Engine Extractability (20 points)** - Standalone sections that fully answer the H2 question (4 pts) - Actionable steps the reader can take right away (4 pts) - Natural keyphrase integration, never stuffed (4 pts) - Conversational tone matching how people ask AI (4 pts) - Primary question answered within the first 200 words (4 pts) **Content Differentiation (15 points)** - Original insight not available elsewhere (3 pts) - Specific data or receipts (3 pts) - Unique analogies or explanations (3 pts) - Clear actionable takeaway (3 pts) - Voice authenticity, sounds like the host and not like AI (3 pts) **Technical AEO Readiness (10 points)** - Title includes the primary keyphrase (2 pts) - Meta description under 160 characters (2 pts) - 3-5 internal links with descriptive anchor text (2 pts) - Evergreen angle that stays relevant (2 pts) - No filler paragraphs (2 pts) **Scoring thresholds:** - 85+ proceeds to publish - 65-84 upgrades the weakest categories and re-scores before publishing - Below 65 rewrites the weakest sections, then re-scores Do not publish below 85. Fix the weakest areas and re-score first. ### Step 6: Generate Meta Data - Slug: lowercase, hyphens, derived from the title - Meta description: under 160 characters, answering the core question of the post - Category: pick the one that fits the content ### Step 7: Publish Create the post in whatever format your blog uses, matching your existing post structure. Include: - Article schema markup (JSON-LD) with author, date, headline, description - FAQ schema built from the H2 question headers - Key takeaways styled as a summary callout box - Proper H1, H2, H3 hierarchy - Open Graph and Twitter Card tags with an image if a thumbnail exists Add the post to your blog listing as the newest entry. Use clean, lowercase, hyphenated slugs and publish it the way your platform ships posts live. ### Step 8: Internal Linking After the post is live, read your existing posts and add 3-5 natural inline links from the new post to relevant older ones, with conversational anchor text. Then find 2-3 older posts where a link back to this new post fits, and add one link each. Only link where the topic genuinely connects. Never duplicate a link already in the post. ### Step 9: Mark It Tracked Update the entry wherever you track content: set the status to published, save the live URL, and store the title, meta description, and primary keyphrase. ## Voice Rules Write in the voice you set up in first run. Warm, direct, action-oriented, spoken straight to the reader as "you." - Short to medium sentences. Break lines often. One-sentence paragraphs for emphasis. - Rhythm: short, short, then a longer sentence that lands the point, then short again. - Talk to the reader with "you" and turn every lesson toward them. - Skip jargon. Explain hard things through simple, punchy analogies. - Preserve the host's signature phrases word for word, straight from the transcript. - Never start a sentence with "And." - Never use "Here's the truth," "Here's the thing," or "Here's what I know." - Never smooth the host's raw language into generic prose. Their actual words are the content. - Never fabricate stories or details that were not in the transcript. - Never use these words: delve, unlock, craft, foster, tapestry, embarking, unleash, unveil, realm, boasts, revolutionize, tenets. - No semicolons, no em dashes, no contrastive framing. The EEAT principle: the transcript language is the gold. The host's exact phrases, analogies, stories, and explanations are what content farms cannot copy. Preserve them. The post structures the thinking. It never replaces the voice. ## Quality Gate Before any post goes live, verify: - AEO score is 85+ - A bold direct answer leads every H2 - The key takeaways block has 3-5 bullets - The opening tells the reader what they get within 3 sentences - The host's actual transcript language is preserved word for word - At least 2 specific stories or moments from the transcript are included - At least 3 internal links to existing posts - Meta description is under 160 characters - The episode attribution line sits at the bottom with the audio link - The slug is lowercase, hyphens only - Article schema and FAQ schema are in the post - The blog listing is updated - The tracked entry is marked published with the live URL
From then on, just drop in an episode and say "Podcast to blog."
Want to go further than skills?
Skills like this are how Christine runs her own business every day. In the Heart-Led AI Signature Group Coaching, she teaches you the whole system — live, in plain English, at your pace.
Explore Signature CoachingA publish-ready post — with your voice intact.
This is not a summary of your episode. It's a fully structured post built from your actual spoken words, with every required element in place. Every post carries these parts:
1 · Title + Key Takeaways
An H1 carrying your primary keyphrase naturally, followed by three to five takeaway bullets — the first 200 words AI reads, so each bullet delivers value on its own.
2 · A Three-Sentence Opening
Leads with what the reader gets — the framework, the insight, the actionable thing. No backstory about the show. It opens with a confident declaration that stakes a position.
3 · Question-Based Sections
Four to six H2 headings phrased as questions people actually ask AI, each opening with a bold, direct answer before the stories and depth — exactly what answer engines extract and cite.
4 · Your Words, Word for Word
Your exact phrases, your stories with names removed, your real numbers, and your analogies — pulled straight from the transcript and kept as close to spoken as a written post allows.
5 · The Close + Episode Attribution
A closing section with specific actions for this week — in your own challenge language if you gave one — and an attribution line at the bottom linking to the full episode.
6 · The AEO Score + Publish Package
Every draft gets scored against 25 criteria across structure, expertise signals, extractability, differentiation, and technical readiness — out of 100, with 85 required to ship. Then it publishes with the slug, meta description, Article and FAQ schema, and three to five internal links woven in both directions.
And if the draft scores an 84?
It doesn't publish. The skill upgrades its weakest categories and re-scores before anything ships — a draft below 85 never goes live, and one below 65 gets its weakest sections rewritten entirely. It also never fabricates a story or detail that wasn't in the transcript, and it never smooths your raw spoken language into generic prose. Your words are the content. The structure just organizes them.
Keep stacking: pairs beautifully with Publish-Ready Check
Podcast To Blog writes, scores, and publishes the post. Publish-Ready Check is the final gate for everything else you write — it verifies every required element is present and packages the handoff your publisher expects.
Get Publish-Ready Check →Because your episode deserves more than one launch day.
An episode gets heard the week it drops. A post built from that episode gets found — by Google and by AI answer engines — for years. This skill makes the second life automatic.
One episode, one question
Before writing a word, the skill names the single question your episode answers better than anything else on the internet. That question becomes the angle for the whole post, and everything else becomes supporting material — the kind of focused post AI engines cite.
Your voice is the part nobody can copy
Your exact phrases, real numbers, and analogies are preserved word for word from the transcript. That lived-experience language is what content farms can't fake — the structure organizes your thinking, it never replaces your voice.
Bold answers sit where AI looks
Every section heading is a question someone would actually ask, and the definitive answer comes first, in bold, within the opening sentences. Each section stands alone — so if an AI pulls just one, it fully answers the question.
It grades its own work before you see it
Twenty-five criteria, one hundred points, eighty-five to publish. Structure, expertise signals, extractability, differentiation, and technical readiness all get measured — so "good enough" is a number, not a feeling.
It finishes the whole job
Meta description, slug, schema markup, internal links out of the new post and back into it from older ones, and your tracker updated with the live URL. Published means published — not "draft sitting in a doc."