How to write local newsletter summaries that stand on their own
Rewrite one item from your next issue three ways, a bare link, a clipped paragraph, and a short summary, and learn which one treats the email as the product.
By the end of this guide you will have rewritten one item from your next issue three ways and picked the version that works. You need two things before starting: the current draft of your next issue, and the source story behind each link in it. I write this from my own desk, because this is an editorial judgment I make every week, and the judgment is the part worth teaching.
The question behind every item is how much of the story to give away in the email. My position is simple. The newsletter is the product. A reader who opens your email on a Tuesday morning should finish it knowing what happened in their town, even if they never click a link. That standard forces you to decide what the news actually is, and it shows up in the item itself, in the length, the specificity, and the words you put in the link.
The three versions, side by side
For a worked example I will use a real, sourced item rather than invent a fake news event. The item is the Local Media HQ guide on writing a local newsletter, which is fair game as a newsletter item because it is a public article a local media operator could genuinely run. The guide's relevant content, for this exercise, is its format advice: lead with what's happening, be specific, keep news items short, and design for sustainable editorial effort. I will present that item three ways.
- 01Write the bare-link version
The item is a headline and a URL, nothing else. Write it and look at it cold. It tells the reader a guide exists but gives them no information. This is the version to beat.
- 02Write the clipped-paragraph version
Copy or paraphrase the opening of the source and stop after a sentence or two. For the guide, that opening talks about people copying a well-known newsletter format. It stops before the format advice, so the reader learns that a discussion exists and nothing about what to do.
- 03Write the useful-summary version
State the news itself in two or three specific sentences. Here that means naming the guide's format advice: lead with what's happening, be specific, keep items short, and keep editorial effort sustainable. The reader now has the substance.
- 04Write a descriptive read-more link
Replace Read more or a bare URL with words that say where the link goes, such as the full newsletter format template. The link becomes a menu entry, and a reader who skips it loses nothing essential.
- 05Compare all three against the no-click test
Ask whether a reader who never clicks still learned the news. The bare link fails. The clipped paragraph mostly fails because it stops early. The summary passes.
- 06Check the summary against the source
Open the original and confirm every material claim, date, and affected party in your summary. Fix anything the summary got wrong or overstated before the issue goes out.
When a bare link is acceptable
There is a legitimate place for link-only listings, and it is smaller than most writers assume. If the item is a directory or utility slot, a calendar line, a job posting, a permit notice, a listing where the pointer itself is the service, a bare link does the job. The reader asked for the address, and the address is the item. Editorial slots, where you are telling a reader something happened, need the summary. If you cannot tell which kind of item you are writing, that is a sign the item has no news in it, and the honest edit is to cut it.
Where people get stuck
The summary runs long. The usual cause is trying to convey every qualification in the source story. A summary cannot carry all the caveats, and it should not try. Carry the material facts, the what, the who, the date, the conditions that change the reader's understanding, and let the link carry the rest. If you find yourself writing a fifth sentence, you are writing the article again, in the wrong place.
The summary disagrees with the source. This happens most often when a draft was summarized under time pressure or by a tool and nobody checked it. Verify against the original before it ships. If a fact in your summary does not appear in the source, cut the fact or cut the item. I treat this as a hard rule, and the check takes one minute per link.
The link text says nothing. Read more, here, and the raw URL all waste the one place in the item where you can promise the reader what the click returns. Write the link text as a description of the destination, in a few words, and keep it honest. If the destination is a template, say template. If it is an agenda, say agenda.
Where the work gets easier
Summarizing at this level is judgment work, and it does not compress to zero effort no matter what tools you use. My team at Local Media HQ runs more than 20 local publications with 175,000+ subscribers, and our house software, larkfeed, lightbreak, and greetform, exists because we kept doing these edits by hand. The judgment on which version of an item to ship stays with an editor either way. If you want help standing up this kind of operation, we work with publishers through a strategy call, Meta ads management, and advisory and AI ops.
One question, answered straight
Does giving away the story hurt clicks? I cannot promise a click number, and I would not trust anyone who does promise one without showing their test. What I can say is what the choice is actually between. A clipped paragraph gets some clicks from readers who feel withheld from, and a summary gets fewer, better-qualified clicks from readers who know exactly what the destination adds. The guide I cited as the worked example makes the same underlying case: lead with what's happening and be specific. You are choosing which reader you are writing for, and I write for the one drinking coffee who wants to know what happened.
Here is the edit for your next issue. Open the draft, pick the one item you would be embarrassed to read without clicking, and rewrite it as a three-sentence summary with a descriptive link. Check it against the source, then ship. If the rewrite works on that item, the same move works on the rest of the issue.
