Every podcast episode
writes its own blog post.
Every episode I record auto-becomes a full WordPress post with embed, rewritten description, internal links, categories, SEO tags, and featured image, all without me logging into WordPress. The blog stays fresh, listeners stay on my domain, SEO compounds. The work of an editor, done in the background.
Every recording day, a full blog post writes itself.
Most podcasters ship an episode, post it on the host, and never get around to building the proper blog post that turns the audio into a real article on their own domain. The post-production for a single episode is hours of manual WordPress work: log in, paste the embed, rewrite the description, pick a category, fill in SEO tags, choose a featured image, fix the slug. There is a different way. Let a small bot wait one hour after syndication, then write the whole post for you. Here is who it is for, what goes wrong without it, how it works, and what you get back.
Who it’s for
Podcasters, YouTubers, course creators, and interview-show hosts who already publish weekly and want every episode to live on their owned domain, not only on Spotify and Apple. Especially useful if you have a WordPress blog that earns from leads, ads, or product sales. If you record content and your website does not show it, this is for you.
What goes wrong
Without the bot, the blog post is the step you skip when you are tired. The episode goes up on Spotify and dies there. Search traffic finds nothing on your site for the topic you just covered. Listeners stay on someone else’s platform. Your domain gets no SEO equity from work you already paid to produce. An episode that never becomes a blog post is half a piece of content.
How the machine works
The trigger fires when a new episode appears in your RSS or YouTube feed. The bot waits one hour for syndication, fetches metadata and transcript, rewrites the description into blog format, embeds the player, picks internal links from the back catalog, assigns categories, generates the SEO title, meta description, tags, and featured image, then publishes through the WordPress REST API. You record. The bot writes. The blog grows.
What you get back
A fresh blog post every recording day with embedded audio, structured description, internal links, proper categories, and full SEO metadata. Listeners arrive through search and stay on your domain instead of Spotify. Roughly $25 to $40 of attributable revenue per post over its life, ~$3,000 to ~$6,000 a year, compounding to ~$30,000+ across five years. An owned blog that fills itself, one episode at a time.
I was leaving every episode on someone else’s platform.
For the first year of the podcast, every episode lived on Spotify, Apple, and YouTube and nowhere on my actual website. I told myself I would write the proper blog post later, when I had more time. Later never came. The post-production for one episode (log in, paste the embed, rewrite the description, pick a category, fill in SEO tags, choose a featured image, fix the slug) took me about 90 minutes if I was focused. With three episodes a week, that was four and a half hours of pure WordPress admin gone every week.
The cost was bigger than the time. Listeners who found me through search were sent to Spotify or Apple, not my own pages. My WordPress blog was dead for months at a time. Google had nothing to rank for the topics I was covering on the podcast. The asset I cared most about (the owned domain) was getting starved while the platforms I rented attention from quietly grew their hold on my audience.
So I built a small bot. One hour after a new episode syndicates to every platform, the bot fires. It pulls the episode title, the description, and the transcript from the RSS feed. It rewrites the description into a blog-format intro and body. It embeds the audio player at the top of the post. It picks two or three internal links from the back catalog that match the topic. It assigns the right categories. It generates the SEO title, the meta description, and the tag list. It picks a featured image. It renames the slug to a clean URL. Then it publishes to WordPress through the REST API.
The total cost of running it is a few cents per episode in API calls. The total time I spend on a new blog post is zero. The blog now gets new content every single time I record, which used to be never. Listeners arriving through Google search land on my domain instead of Spotify, see the embedded player on the page, and stick around for the internal links and the CTAs that live next to the audio. The owned asset finally compounds the way it was supposed to.
Proof point: the blog this engine writes against is martinebongue.com itself, and the podcast that feeds it is Freedom by Choice on YouTube. The mechanics are also covered in the Growth Hacking series, so the time-saved and ranking lift numbers on this page read as checkable.
Three moves that turn every episode into a full blog post on autopilot
What made this work was treating the WordPress post not as an afterthought but as the second half of a single piece of content. The audio is half. The blog post is the other half. The framework hangs on three moves: wait one hour for the platforms to finish syndicating, build the full post (embed, rewritten description, internal links, categories), then ship the post with SEO tags and a featured image with no human log in. That is the whole engine. Done right, it gives back ~225 hours a year, around 9 working weeks, and adds ~$3,000 to ~$6,000 in attributable revenue from posts that simply did not exist before.
Wait one hour for full syndication
The bot fires one hour after the episode goes live, not the moment it does. The reason is mechanical. Spotify, Apple, and the rest of the directories take time to ingest the new episode and surface the embed code. If the bot fires immediately, the embedded player on the blog post will half-work or show an error for the first hour, which is the worst possible launch state. The one-hour wait makes the post arrive on a clean rail, with the audio playable from the first listener.
Build the full post in one pass
The bot does not write a thin description and call it a day. It rewrites the show notes into a proper blog intro and body. It embeds the audio player at the top. It picks two or three internal links from your back catalog that match the topic. It assigns the right categories so the post lands in the right archive page. Every field that a human editor would fill in gets filled in, in one pass, so the post that goes live looks like a deliberate article, not a feed dump.
Ship with SEO tags and a featured image, no log in
The last move is the one that decides whether the post ranks. The bot generates the SEO title, the meta description that fits inside Google’s snippet length, the tag list, and the featured image alt text. It picks a featured image either from your media library by keyword or from a free placeholder source. It renames the slug to a clean URL. Then it publishes through the WordPress REST API. No log in. No copy paste. No tab opened. The post is fully shipped before you have closed the recording software.
Once those three moves are in place, the blog stops being the step you skip when you are tired. It becomes the second half of every episode you ship, on a schedule, with zero manual work.
Before the bot
- ~90 minutes of WordPress admin after every episode
- Episodes lived on Spotify, Apple, and YouTube, never on the owned domain
- Google had nothing to rank for the topics covered on the podcast
- Listeners arriving via search were sent to a rented platform, not the site
- Blog was dead for weeks at a time even with three episodes a week shipped
After the bot
- Zero manual time per episode on WordPress, the post writes itself
- Every recording day a fresh, structured article goes live on the owned domain
- SEO tags, meta description, featured image, and clean slug filled by default
- Listeners arriving via search land on the site, see the player, see the CTAs
- ~$3,000 to ~$6,000 a year in attributable revenue from posts that never existed before
Prompt 1: rewrite a podcast description into WordPress blog format
The raw description from your podcast host is written for the player UI, not for a blog post. Use this prompt to rewrite the description into a proper article intro and body that reads like a real WordPress post, with the audio in mind but not as a transcript dump.
Podcast-to-blog description rewriter
Act as a podcast editor turning audio descriptions into WordPress blog posts. The post will host the embedded audio player at the top and live on the owned domain, so the body needs to read as a real article, not a transcript paste. Episode title: [paste] Original podcast description / show notes: [paste] Episode transcript or summary: [paste] Target reader: [one sentence describing who lands on this post] Blog tone: [casual / business / educational, your three adjectives] Produce a complete blog body in this exact structure: a 90-word hook paragraph that frames why this episode matters, three subheadings (H2) each covering one key idea from the episode in 120 to 150 words, one pull-out callout block highlighting the single best takeaway, and a 60-word closing paragraph that points to a related episode and to one CTA. Do not paste the transcript. Reference the audio as something the reader can listen to above. Use the first person to match the podcast voice.
The output of this prompt is what gets pushed into the WordPress body field by the bot. Lock it once for your show, the bot reuses it on every episode.
Prompt 2: generate the SEO title, meta description, and tags for an episode
SEO metadata is the difference between a post that ranks for the topic and a post that nobody finds. Use this prompt to generate the title, the meta description, and the tag list for every new episode, in a format the bot can drop straight into WordPress.
Episode SEO metadata generator
Act as an SEO editor for a podcast blog. I publish a post for every episode and I need the SEO metadata generated automatically so each post has a fighting chance of ranking for the topic the episode covered. Episode title: [paste] Episode topic in one sentence: [paste] Three key terms a listener would type into Google to find this episode: [paste] My niche: [paste] Produce four things. One: an SEO title under 60 characters that opens with the main keyword and reads naturally, not stuffed. Two: a meta description between 140 and 158 characters ending on a full stop, written as one sentence that includes the main keyword once. Three: a tag list of 5 to 8 tags, lowercase, no duplicates, ordered from broadest to most specific. Four: one alt-keyword variant for the SEO title in case the first one is already used on the blog.
This metadata is what the WordPress REST API receives. Run this prompt for every episode, the bot pastes the output into the right fields automatically.
The 3-minute overview of how this works
Before the build steps, watch this short overview. It’s the exact video from the Automations Made Easy page, and it walks through the mechanics behind machines like this one. 1,000+ students have used these mechanics to save two hours a day, with zero coding.
Want to learn the mechanics behind podcast-to-blog automations like this?
I teach the same mechanics that make this quiet publisher run inside Automations Made Easy. 1,000+ students have used these mechanics to save two hours a day and turn one piece of content into a full blog every recording day. No coding required.
Week one: three episodes shipped, three blog posts that wrote themselves.
Most people quit a system like this in the first week because the first post feels too quiet. There is no big spike, no traffic surge, no inbox flood. The first week of the quiet publisher is meant to feel small. The point is to confirm the bot fires one hour after syndication, the post lands clean in WordPress, every field is filled in, and the embedded player works from the first listener.
Week one looks like this. You record three episodes across the week. Each episode syndicates as normal. One hour after each publish, the bot fires, builds the full post, and ships it to WordPress. Three new articles go live without you logging in once. That is roughly 270 minutes of WordPress admin you did not do, four and a half hours of the week back. Each post will earn ~$25 to ~$40 over its life in leads, product clicks, and SEO traffic. Quietly, in the background, while you record the next one.
The point of the first week is not the traffic. The point is to prove the loop closes: episode publishes, bot waits, post writes itself, embed works, SEO tags are filled, the blog finally has a piece of you on it without you doing anything.
From there the maths is simple. ~90 minutes saved per episode across ~150 episodes a year is ~225 hours, roughly 9 working weeks bought back every year. ~$25 to ~$40 of attributable revenue per post across ~150 posts is ~$3,000 to ~$6,000 a year. Over five years, with SEO equity stacking and the product catalog growing, that compounds into ~$30,000+ from articles that would never have existed without the bot.
All of this runs while you record, sleep, or take a week off. The bot does not care. The trigger reads the feed, the cooldown runs the clock, the builder writes the post, the publisher hits the API. The blog grows on a schedule that matches the show, and the owned domain finally captures the value the platforms were quietly keeping.
Prompt 3: pick the right internal links from my back catalog for this episode
Internal links are what turn a single post into a network. Use this prompt to pick the two or three best internal links from your back catalog for every new episode, so the post is wired into the rest of the site from the moment it goes live.
Internal link picker
Act as an SEO editor for a podcast blog. I publish a new post for every episode and I want the post to link to two or three of the most relevant older posts on the same site, so the catalog wires itself into a network instead of a list. Episode title and topic: [paste] Full list of existing blog post titles and URLs in my back catalog: [paste] Episode summary or transcript: [paste] Pick the three most topically relevant older posts from the list. For each pick, write the suggested anchor text (4 to 7 words) the new post should use, the one-line reason this link makes sense for the reader, and the exact URL. Then propose where in the new post each link should sit (in the intro, in the body, or in the closing paragraph). Return the result as a small table with four columns: anchor text, target URL, placement, reason.
The bot drops these three links into the WordPress body before publishing. The back catalog stops being a list and starts being a network.
Prompt 4: write the featured image alt text and image search prompt
Every WordPress post needs a featured image and alt text. Use this prompt to generate both for every new episode, so the bot can pull a free placeholder or pick from your media library and ship the post with proper accessibility and SEO.
Featured image alt text and search prompt writer
Act as an editor preparing a featured image for a WordPress blog post. The post is built from a podcast episode and will live on my owned domain. I need both an alt text and a search prompt so the bot can pull a free image and ship the post with proper accessibility and SEO. Episode title: [paste] Episode topic in one sentence: [paste] Visual mood I want for the blog (calm, bold, cinematic, etc): [paste] Brand colour palette in three hex codes: [paste] Produce three things. One: a featured image alt text between 80 and 125 characters, written as a single descriptive sentence that includes the main keyword once and never starts with the words "image of". Two: a short image search prompt of 6 to 10 words that I can paste into Unsplash, Pexels, or a free generator to find a strong on-topic image. Three: one fallback search prompt in case the first one returns weak results.
The bot uses the search prompt to pull a placeholder if your media library does not already have a match. Free, on-brand, accessible by default.
The exact build, step by step
Wire the RSS or publish trigger that fires on every new episode
The trigger is the source of truth for the whole bot. Point a small workflow (n8n, Make, or Zapier all work) at your podcast RSS feed or your YouTube channel’s RSS. Every time a new item appears in the feed, the workflow fires once. Filter for items that match the show you actually publish so test feeds and trailers do not trigger it. The trigger does not write anything yet, it only carries the new item ID forward to the next step. This single piece is what makes the whole engine event-driven instead of scheduled.
Build the one-hour cooldown timer before the post is assembled
Insert a delay node right after the trigger. Sixty minutes, hard. The reason is mechanical. Spotify, Apple, Google, and the rest of the directories take time to ingest a new episode and serve the embed code reliably. If the bot fires the moment the trigger does, the embedded player on the blog post will half-work or error for the first hour, which is the worst possible launch state. One hour later the platforms have caught up, the embed serves cleanly, and the post that lands is ready for the first listener.
Fetch the episode metadata and the full transcript
When the cooldown ends, the bot pulls everything it needs to write the post. From the RSS or API: the title, the publish date, the duration, the show-notes description, the audio URL, and the artwork. From a transcription source (Whisper, Deepgram, AssemblyAI, or the YouTube transcript if the episode is also on YouTube): the full transcript with timestamps. The metadata fills the structured fields. The transcript fills the body. Without both pieces, the post is shallow and the SEO ceiling is low.
Rewrite the description for blog format and embed the player
This is where the post stops being a feed dump and becomes an article. The bot runs the description and the transcript through the rewrite prompt (Prompt 1 above) to produce a real blog body, with an opening hook, three H2 subheadings, a callout block, and a closing paragraph. At the very top of the body it pastes the embed snippet from your podcast host so the audio player is the first thing the visitor sees. Embed first, article body second, closing CTA third. The visitor can either listen or read, both stay on your domain.
Assign categories, tags, and pick the featured image
Before the post can ship, three structured fields need to land. Categories tell WordPress which archive page the post belongs in, so the post shows up on the right hub page automatically. Tags feed the SEO snippet and the related-posts widget. The featured image becomes the share card on social, the cover on the archive, and the OG image search engines use. The bot runs Prompt 2 to generate categories and tags, and Prompt 4 to generate the alt text and image search prompt, then pulls the image either from your media library or a free placeholder source.
Push to WordPress via the REST API and log the new post URL
The last step is a single HTTPS request. The bot builds the JSON payload with the title, slug, body, categories, tags, featured image ID, SEO title, meta description, and status (publish or draft). It POSTs to /wp-json/wp/v2/posts on your WordPress with an application password for auth. WordPress returns the live post URL. The bot writes that URL to a tiny log file or Airtable row so you can see every auto-posted article in one place. No log in, no UI, no manual step. The post is live before you have closed the recording software.
Trigger fired
RSS or YouTube feed sees the new episode, the workflow fires once with the episode ID.
Cooldown done
One-hour delay runs, every directory finishes syndicating, the embed code goes live.
Post built
Metadata and transcript pulled, description rewritten, embed pasted, internal links picked, categories assigned, SEO metadata generated, featured image attached.
Post live
WordPress REST API publishes the post, the new URL gets logged, the blog has a fresh article without you opening a tab.
Build this quiet publisher inside the same playbook 1,000+ students use
Automations Made Easy teaches the mechanics behind bots like this one. Step by step, no code, plain English. Pull a full blog post out of every episode you record without touching WordPress.
The six months after I switched it on
Here is the shape of the first six months after I turned the auto-post bot on for the podcast. The line is intentionally modest in the early months and steady from there, because that is how a quiet publisher actually behaves.
Attributable revenue from auto-posted blog posts, per month
Caption: Monthly revenue from leads + sales attributed to the auto-published blog posts. Three things matter on this chart. The line stabilises around $300 a month and stays there. The revenue comes from articles that did not exist before the bot. And every single one of those months happens without you logging into WordPress.
What other students built
I teach the simple skills behind machines like this in Automations Made Easy. Students who built their own version sent back what changed in their first month.
“I had been recording two episodes a week for nine months and my blog showed three posts. Two weeks after switching this bot on, the blog had 78 articles. Same effort, an actual website.”
“The first auto-posted article ranked on page one for a long-tail keyword in eleven days. That had never happened with my hand-written posts because I never wrote them in the first place.”
“Used to skip the blog post step every single Friday because I was tired after recording. Now the post is up before I have made coffee. The owned domain finally gets the value I record.”
“I added the bot to my existing show and added 4 hours back to my week instantly. I now use those four hours to record one more episode, which the same bot turns into another post.”
What’s inside Automations Made Easy
AME isn’t a library of pre-built automations. Every business is slightly different. What’s reusable across all of them is the underlying mechanics: how to set up little machines that listen, write, and follow up while you sleep, and how to wire the pieces together without writing code.
The program walks you through six modules: The Right Tools (the cost-effective, no-code stack I actually use), Task Selection Mastery (which automations are worth building first), Design Secrets (mapping an automation before you build it), Zero to Hero (complete beginner to confident automator), Real-World Application (we build a full automation together, end to end), and Monetization Mastery (turn the skill into a side-business).
It also includes done-for-you templates you import in two clicks, over-the-shoulder training videos, and the same playbook 1,000+ students have used to save two hours a day. No coding required. If you can copy and paste, you can build this.
The auto blog post bot: common questions
Pulled from what readers and Automations Made Easy students ask most.
Will Google penalise me for duplicate transcript content?
No, if you do it the way this bot does. The bot does not paste the raw transcript. It rewrites the description into a blog-style summary, adds internal links to related episodes, embeds the audio player, and assigns proper categories. Google sees a structured page with original framing around the audio, not a transcript dump. Pages built this way rank for the topic the episode covered, because the post is a real article that happens to host the audio, not a copy of it.
Which platforms does this work with, WordPress only?
WordPress is what this build uses because the WordPress REST API is the easiest publish endpoint, but the same mechanic works for Ghost, Webflow CMS, Wix, and Squarespace as long as the platform exposes a publish API or a webhook. Static-site setups (Hugo, Astro, Next.js with a Git-backed CMS) work too: the bot opens a pull request with the new post instead of hitting an API. The brain of the bot does not change, only the last step does.
What if I want to edit the post before it goes live?
Two ways. Option one: the bot publishes to a draft status in WordPress instead of public, sends you a Slack or email link, and you hit publish after a quick read. Option two: the bot publishes live but tags the post with a review label for the first 24 hours, so you can clean anything you want during a single coffee-and-review session the next morning. I run option two because the bot is reliable enough that 9 out of 10 posts need zero edits. Pick the option that matches your tolerance.
Do I need an embed player or just a YouTube link?
Embed the player. A YouTube link alone sends the listener away from your site, which is the exact opposite of what this engine is for. The whole point is that listeners arriving through search stay on your domain, listen to the episode there, and see your product links and internal links in the same view. Most podcast hosts give you an embed snippet (Buzzsprout, Captivate, Spotify for Podcasters all do). Drop that snippet into the template once and the bot pastes it on every new post.
What if my podcast isn’t transcribed?
Run a cheap transcription step in front of the bot. Whisper via OpenAI, Deepgram, or AssemblyAI all do it for a few cents per episode. Feed the transcript into the bot and the description-rewrite prompt does the rest. If you genuinely have nothing, the bot can still publish a usable post from the title, show notes, and the embed, but the SEO ceiling is much lower because there is no body content for Google to rank. Transcription is the single biggest-payoff upgrade for this whole engine, do it from episode one.
More Money Makers like this one
Built from the same handful of mechanics. Each one captures, converts, or earns money that would have walked out the door.
Run this quiet publisher yourself, or learn the mechanics inside Automations Made Easy.
If you want to learn the mechanics behind podcast-to-blog automations like this and build your own at home, Automations Made Easy is the playbook. Step by step, no code, plain English. If you want to talk through which trigger, transcription source, and publish flow would work for your specific show first, I take a small number of consulting clients each month.
€497 one-time · Lifetime access · 1,000+ students
