How to build release newsletters and permanent author-page issues that feed traffic into each other — using two pieces of bonus content, and AI to do the heavy lifting.
Most authors send a release email, it gets one open, and the work evaporates. The Looping Method turns every release into a closed circuit that keeps moving readers between your inbox and your website — long after send day.
The core idea is simple. Every release produces two destinations and two pieces of bonus content. The destinations point at each other. The bonus content is the bait that makes readers cross from one to the other. Done right, a single release keeps working for weeks: the email drives subscribers to your site, the site converts strangers into subscribers, and both sell the book.
Ship a newsletter (your distribution) and a matching author-page issue (your permanent archive); put two bonus pieces in play so each destination has a reason to send readers to the other — and use AI to produce all of it in your voice.
We'll use a real example throughout: K.S. Valentina's gothic romance series Vauclain Monsters, whose monthly newsletter The Sinner's Syllabus ships both an email and a permanent issue page on her author site. You'll see exactly how her two-magnet issues are wired.
Every release cycle, you produce two pieces that share content but differ in format, platform, and job.
This goes out by email (Substack, MailerLite, Kit, or any ESP) and lands in inboxes. It is personal, short-ish, and in your author voice. Its job is to reach the people you already have and move them somewhere. Technically it is plain, inline-styled, email-safe HTML.
This is a full, beautifully styled web page that lives permanently on your author site (e.g. yoursite.com/[pen-name]/[book]/). Its job is to be the permanent home of the content — discoverable, linkable, shareable — and to convert strangers into subscribers. It can be lavish: hero, cover art, drop caps, multiple CTAs.
The email is the distribution; the page is the archive. The email expires in the inbox. The page works forever — in search, in your link-in-bio, in every future post that references it. Build both, every time.
This is the engine. Each issue ships two pieces of bonus content — and you place them so each destination dangles the one the reader can't get without crossing over.
Pick two bonus pieces per release, aimed at two different readers:
Then you cross-wire them:
For the Brightwater release, Valentina shipped two magnets in one issue:
Magnet A (broad): "The Feu Follet of Louisiana" — a folklore primer on the swamp-light myth behind a love interest. No spoilers; perfect for new readers. It headlines the email.
Magnet B (deep): "The Frostwoven Line" — a deep history connecting Vauclain Monsters to her other series for crossover superfans. It anchors the permanent page, and the email teases it.
Both deliverables share the same skeleton. The email is the lean version; the page is the lavish version. Build the content once, in this order:
Address readers consistently (Valentina opens "Sinners —"; some authors use "Friends"). Land emotions in one sentence, not paragraphs of hype. Be specific over general. Keep one standing sign-off. Whatever your voice is, lock it once (Module 5) and reuse it forever.
AI won't replace your voice — it amplifies it, if you lock the voice first and drive the process. Here is the exact four-step workflow and a copy-paste prompt for each. Use them with any capable AI assistant.
Before drafting anything, capture a reusable "voice card." Paste 2–3 samples of your own writing — back-cover copy, a favorite paragraph, a past newsletter.
Below are 2–3 samples of my writing. Build me a reusable VOICE CARD I can paste into future prompts. Capture: sentence rhythm and length; signature moves (fragments, repetition, etc.); words and images I reach for; words/clichés to BAN; how I address readers; my standing sign-off; my emotional register (warm? cold? wry?). Keep it under 200 words, written as instructions to an AI. Then list 8–12 "banned" words/phrases that would break my voice. SAMPLES: [paste 2–3 samples here]
I'm planning a release newsletter. Interview me to fill this brief, asking only for what's missing: - Book title, series + number, release date, KU status - Buy/preorder link(s) - The one-line hook (no spoilers) - What's next after this (preorder / finale / new series) - Two candidate bonus-content angles: one BROAD (new readers, spoiler-free) and one DEEP (superfans / cross-series) Then summarize the brief back to me as a clean block I can reuse.
Using my brief, design the TWO-MAGNET loop for this issue. MAGNET A (lives in the email): broad, spoiler-free, welcomes new readers. Give a title, a 1-line premise, who it's for, and the ~600–1500 word piece itself. MAGNET B (lives on my permanent author page): rewards superfans or connects two of my series. Give a title, a 1-line premise, who it's for, and the piece itself. Also write: - the TEASE LINE the email uses to send readers to Magnet B on my site - the TEASE LINE the page uses to send readers back to subscribe for Magnet A Use my voice card. No spoilers for the new book.
Write my NEWSLETTER POST using my voice card and brief. Structure: masthead line · headline · italic dek · "Note from the author" · Magnet A in full · one-line tease + link to Magnet B on my site [URL] · what's next + buy links · sign-off · footer. Output as PASTE-READY HTML: a single <div> max-width 580px, serif font stack (Georgia), font-size 17px, inline styles ONLY, NO <style> block, simple <hr> dividers, links in my accent color, NO drop caps. It must survive pasting into an email editor.
Now write the PERMANENT AUTHOR-PAGE version of this issue — the lavish archive. Same release; more elaborate: hero with cover image, drop-capped note, Magnet B in full, a callout pointing back to subscribe for Magnet A, a preorder CTA, and a backlist grid. Output ONE self-contained HTML file (inline <style> allowed). Use this design system: [paste your color tokens + font choices — or say "match this file" and attach an existing page]
Audit this draft against my voice card. Flag, with line quotes: - clichés and "AI tells" (stacked tricolons, "the thing most likely to…", hollow hype) - any of my BANNED words/phrases - anything that reads as forced or over-composed - factual risks (wrong issue number, wrong book number, dead links) List fixes as a numbered list. Do NOT rewrite the whole thing unless I say so.
Always run Step 4, and always read the result aloud. AI over-writes: it stacks "It has teeth. It has heat." triads and reaches for "the thing most likely to get you killed." Your voice card's banned list is what catches it. Treat the first draft as clay, never as final.
The same inline-styled email HTML works across platforms — the how-you-paste-it differs. Pick your platform:
Substack's editor strips custom CSS but keeps structure. The reliable method:
Keep max-width ~580px, Georgia serif, no <style> block. That's exactly why the Step-3 email prompt is built that way.
<style> block reliably across clients.<style> blocks.max-width:600px.alt text.Host your covers and images on your own domain (e.g. yoursite.com/Cover.png). Then the same URL works in the email and on the page — no duplicate uploads, no broken art. (Watch case-sensitivity: Cover.png ≠ cover.png on most web hosts.)
Your permanent issue page is a single self-contained HTML file in your site repo. A few conventions keep it clean and discoverable:
Use a readable, per-issue or per-book slug:
On your main author page, keep a "This month" block that always points at the newest issue. Update its issue number, blurb, and link each cycle. That one block turns your homepage into a living funnel.
If your site is on a static host (Netlify, Vercel, GitHub Pages), the issue page deploys the moment you push/redeploy — as long as the file (and its images) live in the repo. Two gotchas worth a checklist line: filenames are case-sensitive, and image paths must be relative to the file's folder (a page in /valentina/brightwater-live/ reaches a root image as ../../cover.png).
Here is my existing author-page issue [attach the HTML file]. Build the NEXT issue from it: keep the exact design system, fonts, and components; swap in the new issue number, hero book, note, Magnet B, CTAs, and backlist. Keep all image paths relative the same way. Output the full new HTML file.
Fill this in and it builds you a ready-to-run master prompt for your next issue — both magnets, both deliverables, both teases. Paste the result into your AI assistant.
Space the loop across the launch so it keeps moving:
You’ve got the whole loop. Two doors from here:
Ready for the full curriculum? The Darkling Collective store has in-depth masterclasses on craft, marketing, and the business of authorship.
Visit the Store →Join the Author Collective on Skool for more free courses, live workshops, and a room full of working authors.
Join the Skool →