Recommending a podcast on LinkedIn sounds like the easiest post in the world. Drop a link, say "great listen," tag the host, done. Then it gets four likes and you quietly wonder why you bothered.
The problem is almost never the podcast. It is that most recommendation posts skip the only part the reader cares about: why this show changed something for you. Get that right and a podcast rec becomes one of the most natural, low-pressure posts you can write, the kind that pulls comments from people you have never met and makes the host remember your name.
Why a Podcast Recommendation Works Better Than You Think
A good recommendation post does three quiet jobs at once. It shows your taste, which signals how you think. It hands your audience something genuinely useful, which builds goodwill. And it gives you a reason to post that is not about you, which lowers the bar to publishing.
That last part matters more than people admit. A lot of folks freeze up writing about their own work because it feels like bragging. Recommending someone else's show removes that wall. You are pointing at something you love, and enthusiasm reads as honest in a way that self-promotion never does.
There is a relationship angle too. Hosts notice who shares their work and what they say about it. A thoughtful recommendation is one of the cleanest ways to get on a creator's radar without a single cold DM. I have seen people land podcast invitations of their own simply because they wrote a sharp post about an episode and the host saw it.
Lead With the Specific Idea, Not the Show Name
Here is the single biggest mistake: opening with the title. "I have been loving the Acquired podcast lately" tells the reader nothing. They cannot tell if it is for them, so they scroll.
Instead, lead with the one idea that stuck with you. Try this shape:
"I have been chewing on a line from a podcast for three days: most companies do not die from competition, they die from indecision."
Now the reader is hooked on the idea, not the brand. They want to know where it came from. You name the show in the next line, after curiosity is already working for you.
The test is simple. If you removed the podcast name entirely, would the first two lines still make someone stop? If not, your hook is leaning on the title to do work it cannot do. This is the same discipline behind how to write a post with a strong hook, and it applies to LinkedIn just as much as X. The first line earns the second. The second earns the expand.
Tell Them What Changed for You
A recommendation without a personal stake is just an advertisement, and the feed is allergic to advertisements. The fix is to show the before and after in your own head.
Pick one concrete thing the episode shifted. Not "it was insightful." Something you can point at:
- A decision you made differently because of it
- A belief you held that the episode dismantled
- A specific tactic you tried that week and what happened
- A question it left you stuck on for days
For example: "I used to write my onboarding emails to sound professional. After episode 142, I rewrote them to sound like a text from a friend. Reply rate went from 8 percent to 22 percent." That is a recommendation with proof baked in. The reader does not just learn a show exists, they see what listening to it actually did.
Specificity is the whole game here. "Changed how I think about marketing" is forgettable. "Made me delete an entire pricing page and start over" is a post. Reach for the smallest true detail rather than the grandest claim.
Structure the Post So People Finish It
LinkedIn is read on phones in stolen seconds, so the shape on screen matters as much as the words. A recommendation post that runs as one dense block dies even when the writing is good.
A reliable skeleton looks like this:
- The idea or line that stuck (one or two lines, your hook)
- Where it came from, naming the show and episode
- What it changed for you, with a concrete detail or number
- One reason your specific audience should listen
- A soft invitation to reply
Keep paragraphs to one or two lines with white space between beats. Put a clean line break before your closing question so it lands. And resist the stacked one-sentence-per-line broetry look. It reads as a formula now and pulls people out of the story.
When you have your draft, it helps to run it through a LinkedIn post generator to tighten the phrasing and try a few hook variations, then cut anything that drifts back toward sounding like a press release. The tool gives you options; your judgment picks the one that sounds like you.
Mind the Length and the Link Question
Two technical things quietly decide whether your recommendation gets seen.
First, length. A recommendation post does not need to be long. The sweet spot is usually 600 to 1,300 characters: enough to tell the story, short enough that your closing question is not clipped. Before you publish, run the draft through a character counter so you know your hook clears the "see more" fold and nothing important gets truncated on mobile.
Second, the link. This is where most recommendation posts shoot themselves in the foot. LinkedIn tends to show posts with outbound links to fewer people, because a link pulls users off the platform. So pasting the Spotify URL straight into the body can quietly cap your reach.
The cleaner play is to write the post with no link, then drop the link in the first comment and edit the post to say "link to the episode in the comments." If you want the full reasoning on when an external link helps versus hurts, the difference between a link vs text post is worth understanding, because it shapes how far almost everything you publish travels. For a pure recommendation, text body plus link-in-comment is almost always the stronger choice.
Give the Reader a Reason That Fits Them
A recommendation lands harder when you tell a specific person why it is for them. "Everyone should listen to this" is weak because it targets no one. "If you run a small team and you are drowning in meetings, episode 88 is your permission slip to cancel half of them" targets someone exactly.
Think about who follows you and what they are stuck on. Then write the one line that says: this episode is for you, specifically, because of this. That single line does more for your reach than any hashtag, because it triggers the comment "saving this, that is exactly my situation."
This is also where you can borrow the host's authority without being weird about it. Naming the guest and one surprising thing they said gives the reader a taste, which is far more persuasive than describing the show in general terms. People share things that already gave them a small win, not things that promise a win later.
Close With a Question, Then Show Up
The last line of a recommendation post should open a door, not close one. End with a genuine question that invites people to reply with their own picks.
Good closers sound like:
- "What is one podcast that changed how you work? I am building a list."
- "Has anyone else heard this episode? Curious if it hit you the same way."
- "Drop your favorite business podcast below, I need new ones for my walks."
Then, and this is the part everyone skips, be there for the first hour. Reply to every comment. Ask a follow-up. When you keep the conversation alive early, more people see the post, which feeds your LinkedIn reach and tells the platform the post is worth pushing further. A recommendation post that sparks a thread of other people's picks can outrun your usual numbers by a wide margin, purely because you turned a monologue into a conversation.
Common Mistakes That Sink Podcast Recommendation Posts
Most of these are invisible while you write and obvious once you know them.
- Opening with the show name. Lead with the idea. The title is the second line, not the first.
- No personal stake. If the episode did not change anything for you, the reader has no reason to care. Find the one thing it shifted.
- Vague praise. "So insightful" and "must listen" are noise. Quote the actual line or tactic that stuck.
- Pasting the link in the body. This caps reach. Put it in the first comment instead.
- Recommending the whole show, not an episode. "Check out this podcast" is a chore. "Listen to episode 142 on the drive home" is a click.
- Over-tagging. Tagging the host once is friendly. Tagging the host plus six co-hosts and the network looks like an engagement grab.
- Posting and ghosting. If you do not answer the early comments, the conversation dies and so does the reach.
- Making it secretly about you. A recommendation that pivots to "and that is why you should hire me" reads as a bait and switch. Let the goodwill be the point.
Turn One Recommendation Into a Repeatable Habit
The people who get real mileage out of recommendation posts are not posting once. They keep a running note of lines and episodes that stuck, and once a week they turn one into a post using the structure above.
Do that for a month and you have built a quiet reputation as someone with good taste who shares generously, which is one of the most magnetic things you can be on this platform. The same instinct extends naturally to other formats too. Once you are comfortable recommending a show, it is a short step to share a tool you recommend using the exact same idea-first, proof-second skeleton.
The real takeaway: a podcast recommendation is not a link drop, it is a small story about what listening did for you, ending in a question that invites others in. Write it that way and it stops being filler and starts building relationships.
When you want to turn the episodes you love into a steady rhythm of posts instead of a once-in-a-while afterthought, PostInstantly helps you draft each recommendation in your own voice, check the length, and schedule them so your taste shows up consistently in the feed.