Build a newsletter archive website that brings in new subscribers
Every issue you've sent is writing that only your subscribers have seen. Published as web pages, those issues can be found in search, linked to and shared, and each one can ask a new reader to subscribe. A newsletter archive website keeps them in one place you own, with an address that doesn't depend on your email tool.
Why an archive of your own
Most email platforms offer a hosted web archive, and for many writers that's fine. A newsletter website of your own does a few things better: it lives at your domain, so the links you share keep working if you change email tools; it can be designed like a publication rather than a list of emails; and it puts a sign-up where search visitors land, on the issue page itself.
If you keep your platform's archive public as well, two copies of each issue compete with each other in search. Pick one to be the main, indexable version, usually your own site, and turn off or limit the other where your platform allows it.
Editing an email for the web
An email pasted straight onto a web page reads oddly. Spend five minutes on each issue before publishing it:
- Remove email furniture: "view in browser", unsubscribe footers, personalisation like "Hi there," and merge tags.
- Write a real title. The subject line "#42: some thoughts" won't be searched for; "Why small bakeries are dropping sourdough" might be.
- Add a summary of one or two sentences, used in the archive list and in search results.
- Check dated references ("this week", "tomorrow's event") and add a date line at the top.
- Fix links that pointed to tracking redirects; use the real destinations.
- Leave out subscriber-only material such as private offers or reader replies you didn't get permission to publish.
Issues as a collection
Keep issues in a CMS collection, one entry per issue, with fields for the number, title, date, summary and body. Each issue is served as its own page at /<collection>/<slug> and the collection page becomes the past issues page, listing them all. Entries are edited in the dashboard, so publishing last week's issue is a matter of pasting the edited text and saving.
You don't have to publish everything. Many writers hold back the most recent issue or two as a reason to subscribe, or publish only the evergreen pieces. Say on the archive page what readers are seeing: "Every issue from 2024 onwards, published a month after it's sent."
A sign-up on every issue
The point of an archive is to turn readers into subscribers, so the sign-up has to be where they finish reading. Anticode's newsletter form asks for an email only, which is the right amount. Ask for it at the end of each issue page and in the site header, then check in the preview that it appears where you asked. Send sign-ups to Mailchimp or Kit, which receive newsletter sign-ups as they arrive; Mailchimp uses double opt-in, so new readers confirm by email first.
Write a line above the form that sells the next issue, not the newsletter in general: "Every other Thursday: one long read about small food businesses. Free." Each submission is also saved in your dashboard, and connectors send each one once, without retries, so if a sign-up doesn't appear in your email tool you still have it.
Being found
Every published site serves its own sitemap.xml, robots.txt and llms.txt, so search engines and AI assistants can find the issue pages. Check your sitemap after publishing the first batch to confirm they're listed. Page views per day by source in your dashboard, counted without cookies and including referrals from AI assistants, show which issues bring people in; those are the topics worth writing about again.
Building it
Describe the newsletter: "a site for my fortnightly newsletter about independent bookshops, with an issues collection, an About page and a sign-up form on every page". The Architect shows a plan first. Editorial (Geist) is the natural design system for long reading. Publish on your own domain on a paid plan, so the archive's addresses stay yours.
Limits
- No automatic import from your email platform. Each issue is added as an entry.
- No RSS feed, comments or scheduled publishing.
- No paid tier or subscriber-only archive. Paid newsletters stay on your platform.
- No sending. Anticode collects sign-ups; your email tool sends the newsletter.
Questions people ask
Will publishing issues hurt my open rates?
Usually not. Subscribers read in their inbox; the archive mostly reaches people who've never heard of you. Delaying publication by a few weeks is a common compromise.
Do I need every past issue?
No. Start with your best ten and add the rest over time.
Can I use Kit and Mailchimp at the same time?
Pick one as the list you send from. Two lists drift apart and confuse unsubscribes.