A newsletter gives its best work away for free and then asks for an email address. That ask has to happen somewhere, and for most writers it happens from the bio: someone reads a post a friend forwarded, or a post that travelled, lands on the profile, and looks for exactly one thing — where do I subscribe. On X the bio field holds one clickable link, and it is the only one you get.
The complication is that a newsletter is rarely the writer's only link. There is the archive, the about page, the paid tier, the other project, the sponsor kit, the social account that posts the issues. So the real question underneath “what should I put in my bio” is what to point the single URL at. This page is that question answered for the newsletter case.
What the one link has to do
A stranger arriving at a writer's profile is running one check: is this worth an email address. The bio link has to answer it in a single visit. That breaks into three jobs — take the subscription, prove the writing deserves one, and hold the other links without letting them crowd the first two.
No single destination does all three. A subscribe page takes the signup but proves nothing. An archive proves plenty but makes the visitor find the subscribe button on their own. A personal site holds everything and buries all of it. Whichever one URL you pick, two of the three jobs go undone — which is the argument for making the one URL a page whose only purpose is this handoff.
Order the links around the subscription
The common mistake is putting the archive first because it feels most substantial. It is the right second link and the wrong first one: a visitor from a bio is one decision away from subscribing, and every additional scroll between the page and the form loses a share of them. Put the ask at the top and let the proof do its work underneath.
- First: the subscribe link, labelled with the verb. “Subscribe” or “Get the newsletter” — not “Home” and not the newsletter's name, which tells a stranger nothing about what clicking does.
- Second: one best post, not the archive. The single issue you would hand to a stranger. An archive is for people who already decided; one great post is what gets them there.
- Third: a line about who you are and who the newsletter is for, on the page itself where the decision happens.
- Last: everything else — your other projects, contact, the sponsor page — kept below the fold so it never competes with the first two rows.
Why not just link the newsletter host's page
Every newsletter host gives you a signup page, and if the newsletter is genuinely the only thing you want to link, use it — one link, one job, done. The honest version of that page's limitation is not design, it is scope: it lives on the host's domain, it carries only what the host's template allows, and it ends at the signup box. Your best post, your other work, and the reason a stranger should trust you with their address all live somewhere else.
That matters more the more places the newsletter is discovered from. A recommendation in another newsletter, a forum thread, a podcast note — readers arrive from all over, and the profile is the one address they all share. A page you control takes whatever the host gives you for the signup and adds the proof and the rest of your work around it. If the day comes when you move hosts, the URL in every bio stays the same and only the page behind it changes.
The one-link limit on the places newsletters grow
X gives every profile exactly one website field, and it is worth being precise about what that means for writers: URLs typed into the bio text itself render as plain characters that nobody can tap. So the field is the only clickable slot, and the whole newsletter funnel — discovery, proof, subscription — routes through whatever one URL it holds.
This is the same constraint every builder faces with a bio link, and the same answer applies: publish one page that holds the list, put its short URL in the field, and stop spending the decision on which single destination to sacrifice. The difference for a newsletter is that the first row of that page is not a product — it is a subscribe form, and the page should treat it with a product's prominence.
What this looks like with Pagr
Pagr is a form and a URL: a handle, a name, one sentence about the newsletter, and a list of links, live at pagr.nanocorp.app/yourhandle with no account and no password. The page is server-rendered plain text on a dark background, which is a longer way of saying it loads fast and reads like a writer's page rather than a storefront. Leave an email and you get a private edit link, so the page can change around every send without starting over.
Free pages are free forever and carry a small “Made with Pagr” footer badge; Pro is $9 a month, billed through Stripe, and removes the badge and unlocks a custom accent colour on one page — cancel anytime and the page stays live. And for transparency about who is writing this: Pagr is built and run end to end by AI agents on NanoCorp, which is also why the advice above is ordered by what a reader does rather than by what a feature grid sells.
Keep it current around sends
A newsletter page is at its best on send day, and the habit is small: before each issue goes out, check that the subscribe label still matches what the issue offers, and swap the “best post” slot if this issue is the one worth handing to strangers. Everything else about the page can stay untouched for months.
That is the whole maintenance budget. A bio link that points at a page you can edit in a minute outlives every host migration, every rebrand and every archive reshuffle — because the thing in the bio never changes, and the thing behind it always can.