Newsletter website content checklist
A newsletter site has to make the case for subscribing in one screen, show what an issue looks like and keep the archive findable. The slow parts are the archive export, sponsor details and consent wording on the signup form.
Where to start
- Subscribe. The platform choice and the form drive the layout, and consent wording needs the writer's approval.
- Home. The promise and the sample are the site's sales pitch and can be settled in one conversation.
- Archive. Exporting and choosing the best-of issues takes time, so start it while the design progresses.
- Paid tier. Plans and prices affect the form and navigation, so confirm them before the page is built.
- Sponsors and advertising. Rates and permissions come from old emails, so ask for them early and add the page last.
The checklist
Home
A visitor decides whether to subscribe from the promise, the frequency and one sample, and many newsletter sites open with the author's biography instead.
- Newsletter name as written Short text, requiredSpell it with the capitalisation and punctuation you use in the masthead of each issue, including any 'The' at the start.
- One-sentence promise Short text, requiredWhat a reader gets and how often, in plain words. Example: 'One long read on urban planning, every Sunday morning.'
- Publishing frequency Single choice, requiredPick the pattern you keep to today. The signup box states it so readers know what lands in their inbox.DailySeveral times a weekWeeklyFortnightlyMonthlyIrregular
- Who the newsletter is for Long text, requiredDescribe the typical reader by job, interest or location, and what they do with an issue. Use what you learn from replies.
- Subscriber count to show Short textA number you can read from your platform dashboard today, with the date. Leave blank if it is small or you prefer not to show it.
- Header image or masthead Image uploadThe banner or logo used on the issues. At least 2000 pixels wide, with the text outlined if it is part of the image.
Subscribe
The signup box is the only thing that earns money or readers, and it breaks when the form belongs to a platform nobody on the project can edit.
- Email platform Single choice, requiredPick the service that sends the issues. The designer embeds or links its form and matches its fields.SubstackbeehiivGhostKit (ConvertKit)MailchimpButtondownOther
- Signup form embed or link Link, requiredThe form address or the embed code from your platform. Test that a new signup receives the welcome email.
- Welcome email text Long textThe first message a new subscriber receives. The designer reads it so the thank-you page uses the same tone.
- Consent wording on the form Long text, requiredThe line shown next to the button about how you use the address and how to unsubscribe. Check the rules where you and your readers are, and keep a record of the wording.
- Double opt-in turned on Yes or no, requiredSay whether new subscribers must confirm by email. The thank-you page tells them to check their inbox if so.
- Postal address in the footer Short textSome places require a sender address in each email. Check the rules where you operate, and give the address you want shown.
About the writer
Readers subscribe to a person, so this page needs a real voice, a face and the reasons the author is worth reading.
- Author bio Long text, requiredThree short paragraphs: what you write about, what qualifies you and why you started. Name the places your work has appeared.
- Author portrait Image upload, requiredA well-lit portrait, at least 1500 pixels on the short side. Choose one that looks like you on a normal day.
- Other work and links LinkA book, podcast or past column you want readers to find. Include only links that work and that you would send a friend.
- Press mentions and endorsements Long textWhere the newsletter has been quoted or recommended, with the outlet, the date and the link. Ask a named person before you quote them.
- Contributors or editors Long textAnyone else who writes, edits or designs the issues, with a role and one line each. Confirm each agrees to be named.
Archive
The back catalogue shows new visitors what they will get, and the problem is usually getting the issues out of the platform in a usable form.
- Archive visibility Single choice, requiredPick who can read past issues on the site. The paid and free rules shape the page.Fully publicPublic after a delayFree issues public, paid issues for subscribersSubscribers only
- Archive export File uploadThe export from your platform, as a ZIP with the posts in HTML or Markdown. Say how many issues it holds and how far back it goes.
- Best-of issues Long text, requiredFive to eight links to issues new readers should start with, each with a one-line reason. Choose the ones people reply to.
- Topics or tags Multiple choiceTick or add the categories your issues fall into so the archive can be filtered. Use at most six.EssaysInterviewsLinks and roundupsTutorialsNews analysisReviews
- Sample issue File uploadOne full issue as a PDF or link, chosen to show the usual length and layout. Visitors read this before they sign up.
Paid tier
Paid subscribers fund most newsletters, and unclear differences between free and paid are the main reason they do not upgrade.
- Paid plans and prices Long textEach plan's name, price, billing period and currency, with the annual discount if any. Leave blank if the newsletter is free.
- What paid subscribers get Long textList the extras, such as extra issues, the full archive or a community. Say what free readers receive for contrast.
- Payment provider LinkThe checkout address, usually from Stripe through your platform. Say who owns the account.
- Cancellation and refund terms Long textHow a subscriber cancels and what happens to the rest of the period. Use the wording on your platform.
- Gift or team subscriptions Yes or noSay whether you sell gift or group plans. If yes, the page needs a short section and a separate link.
Sponsors and advertising
Sponsors want audience facts and rules before they spend, and publishers often have neither written down.
- Sponsorship rate card File uploadThe ad formats and prices as a PDF, with the date the prices apply from. If you have none, say which formats you would sell.
- Audience facts for sponsors Long textOpen rate, click rate and the reader profile, each taken from your platform with the date. Leave out any number you cannot show in a screenshot.
- Past sponsors with permission Long textSponsors you may name on the site, each with their written agreement. Add the logo files they approved.
- Sponsor disclosure wording Short textThe label you put on paid placements, such as 'Sponsored'. Check the rules where you operate for what a label must say.
- Sponsor enquiry contact Short textThe email where sponsors write, and who replies. A separate address keeps these out of your reader inbox.
Contact and brand
Readers write back more than any other audience, and the logo, colours and typefaces make the site look like the issues.
- Contact email Short text, requiredThe address readers should write to. Say if you reply to every message or only some.
- Social profiles LinkThe accounts where you share each issue and are active. Skip any you have left unused for months.
- Logo files File upload, requiredSVG or high-resolution PNG of the logo or wordmark, on light and dark backgrounds. If a designer made it, ask for the source file.
- Brand colours ColourHex codes from your issue template. If you have none, name the issue whose look you want matched.
- Brand fonts FontThe headline and body typefaces in your issues. Say if they are your platform's defaults, and the designer will pick close web fonts.
- Privacy policy address Link, requiredThe live page that explains how you use subscriber emails and analytics. If your platform supplies one, link to it and say so.
- Tracking tools on the site Multiple choice, requiredTick every analytics or ad tool you want on the site, so the cookie notice matches.PlausibleGoogle AnalyticsFathomMeta pixelPlatform's built-in analyticsNone
What clients get stuck on
An archive stuck in the platform
Exports from email platforms are messy, with broken images and tracking links. Ask for a sample of ten issues first, and decide whether to import all or only the best-of list.
Subscriber numbers that change daily
A number quoted on a page goes stale in a week. Ask for a rounded figure with a date, or pull it from the platform if it offers an embed.
Sponsor details kept in email threads
Past sponsors and their rates live in old messages. Ask for a one-page summary, and a yes from each sponsor before their name appears on the site.
Consent wording nobody wrote
The signup form often has only a button. Ask the writer to approve a line about how addresses are used and a link to the policy before the form is styled.
A paid tier that is still an idea
Creators describe a paid plan they have not built. Ask what exists today, and leave a section out until prices and benefits are real.
Copy the checklist
Plain Markdown you can paste into a doc or an email.
# Newsletter website content checklist
## Home
- [ ] Newsletter name as written (Short text, required)
- [ ] One-sentence promise (Short text, required)
- [ ] Publishing frequency (Single choice, required)
- [ ] Who the newsletter is for (Long text, required)
- [ ] Subscriber count to show (Short text)
- [ ] Header image or masthead (Image upload)
## Subscribe
- [ ] Email platform (Single choice, required)
- [ ] Signup form embed or link (Link, required)
- [ ] Welcome email text (Long text)
- [ ] Consent wording on the form (Long text, required)
- [ ] Double opt-in turned on (Yes or no, required)
- [ ] Postal address in the footer (Short text)
## About the writer
- [ ] Author bio (Long text, required)
- [ ] Author portrait (Image upload, required)
- [ ] Other work and links (Link)
- [ ] Press mentions and endorsements (Long text)
- [ ] Contributors or editors (Long text)
## Archive
- [ ] Archive visibility (Single choice, required)
- [ ] Archive export (File upload)
- [ ] Best-of issues (Long text, required)
- [ ] Topics or tags (Multiple choice)
- [ ] Sample issue (File upload)
## Paid tier
- [ ] Paid plans and prices (Long text)
- [ ] What paid subscribers get (Long text)
- [ ] Payment provider (Link)
- [ ] Cancellation and refund terms (Long text)
- [ ] Gift or team subscriptions (Yes or no)
## Sponsors and advertising
- [ ] Sponsorship rate card (File upload)
- [ ] Audience facts for sponsors (Long text)
- [ ] Past sponsors with permission (Long text)
- [ ] Sponsor disclosure wording (Short text)
- [ ] Sponsor enquiry contact (Short text)
## Contact and brand
- [ ] Contact email (Short text, required)
- [ ] Social profiles (Link)
- [ ] Logo files (File upload, required)
- [ ] Brand colours (Colour)
- [ ] Brand fonts (Font)
- [ ] Privacy policy address (Link, required)
- [ ] Tracking tools on the site (Multiple choice, required)
Questions about this checklist
Should a newsletter have its own website or just use the platform page?
A platform page is fine to start. Your own site gives you control of design, search and the archive, and the signup form still points at the platform, so moving later is easy.
Should the whole archive be public?
Public issues bring in search traffic and show new readers what they will get. If paid content is the product, show some issues in full and the rest as excerpts with a clear subscribe button.
What must a newsletter signup form say?
How the address will be used, how often you write and how to unsubscribe, with a link to the privacy policy. Rules vary, so check the rules where you and your readers are.
Related checklists
Online course
An online course site has to say what a student can do at the end, show a sample lesson and make enrolment a single click. The slow items are the curriculum document, student results with permission and refund wording.
Membership community
A membership site has to sell a room that visitors cannot see inside, so it needs a clear promise, honest member numbers and plain rules for joining and leaving. Most delays come from pricing decisions, community rules and permission to show members.
SaaS landing page
A SaaS landing page has to say who the product is for, show it working and give a price or a clear next step. Real screenshots, customer permission to use names and a pricing page that is still changing cause most of the delay.