How do you write a newsletter swap blurb that readers actually click on?

Write for the host's readers, not your own

The most common mistake in swap copy is writing it like a landing page. The people reading it have never heard of you, they trust the host who put it in front of them, and they are skimming. Your blurb needs to answer one question quickly: why would someone who likes this newsletter also like mine? Start from the overlap between the two audiences, not from your origin story or your mission. Related: Which delivers more new listeners for a podcast swap, a feed drop or a host-read mention?

Practically, that means reading three or four recent issues of the partner's newsletter before writing a word. Note the tone, the reader's level of expertise, and the recurring themes. If their readers are operations managers who like blunt checklists, a whimsical blurb will feel like an ad dropped into the wrong publication. Match the register first, then say the specific thing you offer that the host does not. Related: When should a small podcast or newsletter run its very first audience swap?

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.

Lead with a concrete promise, not a category

'A weekly newsletter about productivity' is a category. 'Every Tuesday, one system a solo consultant can set up in under an hour' is a promise. Categories are forgettable because the reader already subscribes to something in that category. A promise tells them what changes if they add you to their inbox, and it quietly signals frequency and format, which are two of the biggest reasons people either subscribe or bounce. Related: What should a newsletter writer do when a swap partner never delivers their side?

A useful drafting trick is to describe your newsletter to an imaginary friend of the host, out loud, in one breath, and write down what you said. Then cut every adjective that is doing no work. Words like insightful, curated, and essential are invisible to readers because everyone uses them. Replace them with a specific example: a recent issue topic, a recurring segment, or a real problem you help with.

Keep the structure tight and the call to action honest

Most hosts will give you somewhere between forty and one hundred words, and they will often trim what you send. Assume the first sentence is the only one that survives. A reliable structure is one sentence stating who it is for and what they get, one sentence with a concrete proof point or example, and one short line with the link. Anything beyond that should be easy to cut without breaking the meaning.

The call to action should describe the destination truthfully. 'Subscribe free' works if it is free. 'Read the latest issue' works well when your archive is public, because it lowers the commitment and lets skeptical readers sample before handing over an email address. Avoid vague verbs like 'check it out' and avoid urgency language, which reads as spammy in a recommendation context and reflects poorly on the host who ran it.

Make the host's job easy

Send the blurb as plain text with the link on its own line, plus a one-line alternative that is shorter, in case space is tight. If the host uses images, provide a simple square logo or headshot and say it is optional. Do not send a formatted block with brand colors and buttons; it will clash with their template and they will end up rewriting it anyway, often without telling you what changed. Related: What should a simple cross-promotion swap agreement spell out before anyone hits send?

Finally, ask the host whether they would rather write the intro in their own voice. Many will, and a host-written line such as 'I read this every week and it is the only one I forward' converts far better than anything you can write about yourself. Your job in that case is to give them raw material: two or three true, specific things about your newsletter that they can pick from without doing research.