---
title: Newsletter Website, Archive and RSS Feed | SendHQ
description: Give a SendHQ list a public newsletter site at sendhq.cc/n/your-name with a double opt-in signup form, a page per published issue, an archive and an RSS feed.
canonical: https://sendhq.cc/newsletter/website
last-updated: 2026-11-06
updated: 2026-11-06
---
# A website for your newsletter, with an archive and RSS

Turn on a site for any list and it gets a public home at sendhq.cc/n/your-name: a signup form, an archive of the issues you choose to publish, a page for each issue and an RSS feed. New readers who confirm can get a welcome email from that list.

[Start for $19 a month](https://sendhq.cc/app?plan=indie_hackers_marketing&price=19) [SendHQ for newsletters](https://sendhq.cc/newsletter.md)

## Who it is for

- **Indie founders** who want a link to share for their build-in-public updates without building a blog.
- **Creators running a newsletter** who want past issues to be findable on the web and a form that turns visitors into readers.
- **SaaS teams sending product updates** who keep a public archive of product updates and changelog emails.
- **Agencies** who set up a separate site for each client's list from one workspace.

## What a site includes

- **A home page** with your title, description and accent colour, a signup form, and the archive of published issues, newest first, with pinned issues on top.
- **A page per issue** with its own address and canonical link, and a signup box at the end for readers who found it on the web.
- **An RSS feed** of your 50 most recent published issues at `/n/your-name/feed.xml`.
- **Per-issue choice.** An issue appears on the site only when you publish it to the web, so some issues can stay inbox-only.

## Signup and welcome email

The signup form uses double opt-in: the reader confirms by email before they are added, and the form has a hidden honeypot field for bots. Each list can have a welcome email, written in HTML or Markdown with merge tags, sent once when someone confirms.

## Your design and footer

Workspace newsletter settings set the accent colour, the font (sans, serif or mono) and left or centred alignment for issues, and your postal address for the footer of every issue. Each site can use its own accent colour.

## Built to be safe to publish

- Merge tags on the web copy show their fallback text, so no reader's name or fields are published.
- Issue HTML is sanitized, and every site page is served with a strict Content Security Policy that runs no scripts.
- Reserved names such as admin, billing or paypal cannot be used as a site address.

## From the API and your AI agent

An agent can turn on a list's site, publish a sent issue to the archive and pin it. The same features are in the REST API under `/api/v1`, the `sendhq` CLI, and the MCP server, so Claude, ChatGPT or Cursor can do this work for you through the hosted connector at `https://mcp.sendhq.cc/mcp`. See the [campaigns API reference](https://sendhq.cc/docs/api-reference/campaigns.md).

REST API

```
# Turn on the site for a list
curl https://sendhq.cc/api/v1/lists/lst_123 -X PATCH \
  -H "Authorization: Bearer $SENDHQ_API_KEY" -H "Content-Type: application/json" \
  -d '{"site":{"enabled":true,"slug":"weekly-notes","title":"Weekly Notes"}}'
```

## Honest limits

- Sites live at sendhq.cc/n/your-name. Custom domains for the site are not supported.
- Design options are the accent colour, font and alignment. There is no theme editor or custom pages.
- There are no paid subscriptions, comments, referral program or recommendation network.
- A site is online only while the workspace has an active paid plan and sending is not paused.

## Questions

**Does SendHQ host a newsletter archive?**

Yes. Each list can have a public site at sendhq.cc/n/your-name with an archive of the issues you publish to the web, a page per issue and an RSS feed.

**Can I use my own domain for the newsletter site?**

Not at the moment. Sites are served from sendhq.cc/n/your-name. Your issues still send from your own verified domain.

**Does the newsletter site have a signup form?**

Yes. It uses double opt-in, so readers confirm by email before they are added, and each list can send a welcome email once they confirm.

**Is a reader's name shown on the web version of an issue?**

No. On the web copy, merge tags show their fallback text instead of anyone's details.