Which delivers more new listeners for a podcast swap, a feed drop or a host-read mention?

What each format actually asks of the listener

A host-read mention is a short segment, usually somewhere between thirty and ninety seconds, where the host describes another show in their own words and tells listeners where to find it. It asks very little of the listener: keep listening, maybe remember a name. A feed drop is a full episode, or a substantial excerpt, of the partner show published directly into your feed. It asks the listener to spend a long stretch with an unfamiliar voice, which is a much bigger request. Related: What should a newsletter writer do when a swap partner never delivers their side?

That difference in ask explains most of the difference in outcomes. A host-read reaches nearly everyone who plays the episode, but conversion depends on the listener acting later: opening their app, searching, and following. A feed drop reaches fewer people, because some will skip it, but those who finish it have already experienced the show and are far more likely to follow. One format is broad and shallow, the other is narrow and deep.

Keep reading: Why Cross Promotion Works, Finding Fair Swap Partners, Audience Fit Over Audience Size. See how CrossPromoly helps you cross-promotion swap matcher for podcasts and newsletters.

When a host-read mention is the better choice

Host-reads win when the two shows are adjacent rather than identical. If a personal finance show is swapping with a career-advice show, the audiences overlap in interest but not in format expectations, and a full episode drop can feel like a bait and switch. A warm, specific mention along the lines of 'if you liked our episode on negotiating a raise, this show did a whole series on it' gives listeners a reason to try it on their own terms. Related: What is the best way to swap audiences between a podcast and a newsletter?

Host-reads are also the right tool when either show has a tight release cadence or a strong sense of continuity, such as narrative seasons or a Monday morning news format. Dropping a foreign episode into that rhythm annoys loyal listeners. The mention slides into the existing structure, can be repeated across two or three episodes for reinforcement, and is easy to trim out of the archive later if you prefer evergreen episodes to stay clean.

When a feed drop earns its keep

Feed drops work best when the shows are close in style and the swapped episode is genuinely one of the partner's best. Pick an episode that stands alone, needs no prior context, and shows off the host's personality within the first few minutes. A pilot or a rambling catch-up episode is a poor choice even if it is recent. The partner should get a veto on which episode you use, and you should get the same in return.

The drop needs a proper wrapper. Record a short intro explaining what the listener is about to hear and why you chose it, and a short outro with a clear follow instruction. Title the episode honestly in your feed so nobody feels tricked. Handled this way, a feed drop is closer to a guest appearance than an ad, and listeners tend to respond to it as a recommendation from someone they already trust.

Combining both, and how to judge the result

The strongest swaps often use both formats in sequence: a host-read mention in one episode to prime the audience, then a feed drop a week or two later, then a brief callback afterward. The mention lowers the skip rate on the drop, and the callback catches people who meant to follow and forgot. It also spreads the promotional load, so no single episode feels like it exists to sell something. Related: When should a small podcast or newsletter run its very first audience swap?

Judge each format on its own terms. For host-reads, watch follower growth and any custom link clicks in the days after release, and expect a slower, longer tail. For feed drops, look at completion on the dropped episode and follower growth on the partner side in the same week. Neither number will be huge for a small show, so agree with your partner on what a good outcome looks like before either of you sees the data. Related: What should a simple cross-promotion swap agreement spell out before anyone hits send?