Content publishing
Write a newsletter subject line the issue supports
Name the most useful item in the issue in the words a reader would use for it. Then confirm that a section of the newsletter delivers exactly what the line promises. If you cannot point to the section, change the line.
A text to start with
My newsletter issue for [audience] contains these sections: [section titles with one-line summaries]. The most useful item for readers is [item]. Write [number] subject line options with matching preview text. For each, name the section that delivers on it. Avoid urgency, exclusivity or benefits the issue does not state, and flag any option that overpromises.
Example request. Change the details to fit your situation.Subject line support check
Issue date or name: [ ] Subject line option: [ ] What it promises: [ ] Section that delivers it: [ ] Where that section appears in the issue: [ ] Preview text: [ ] Does the preview match the same section? [ ] Urgency or exclusivity wording used: [ ] Where the issue establishes it: [ ] Benefit claimed: [ ] Where the issue shows it: [ ] Decision: [ ]
Promises the issue cannot keep
A subject line can claim more than the issue holds. Words such as last chance, exclusive or don't miss imply a deadline or access the content may not establish. Check that every date, number or benefit in the line appears in the body. The preview text needs the same check, since readers see it beside the subject. A line naming one item misleads if that item is a small part of the issue, so compare its weight in the line with its weight on the page. A line that hides the topic to create curiosity usually fails this test.
Ask another agent to check the result
Read each subject line and preview text against the issue contents I listed. Reject any urgency, exclusivity or benefit the issue does not establish. Name the specific word that overreaches and say what the issue supports instead. Also say whether the preview text points to a different section than the subject line does.
Pick one and check it against the issue
Choose the option whose promised content appears early and plainly in the issue. Read the subject line, preview text and first screen of the issue in sequence and confirm they agree. Ask one reader what they expect to find from the subject alone, then compare that with the content. Keep rejected options with a note on why each failed.