Most "link in bio for newsletter writers" articles tell you the same five things: put your subscribe link first, add a couple of best-of issues, link your social profiles, track UTMs, optimize for mobile. That advice is fine. It's also the advice every creator gets, with "newsletter" swapped in for the noun.
This post is for newsletter operators with at least 25 issues published and a list large enough that growth math actually matters, somewhere past the first few hundred subscribers, when the bio page starts being a real acquisition channel rather than just a placeholder. The problems no one writes about: your back archive is invisible after 30 issues. Visitors can't tell whether you're a weekly habit or an abandoned project. Your cross-promotion partners change every month and your bio page can't keep up. And the bio page is trying to serve two completely different audiences (subscribers looking for back issues, and visitors deciding whether you're worth their email) with one layout.
Here's how to actually solve those.
TL;DR
A newsletter operator's link-in-bio page has four jobs that generic advice ignores:
- Make your archive discoverable by topic, by reader pick, not just chronologically. Past issues are your best growth asset; a flat reverse-chronological list buries them.
- Signal cadence and consistency. Visible "next issue Tuesday" or "weekly since 2023" trust markers convert better than mystery.
- Manage cross-promotion and recommendations operationally. Featured swaps, recommendation partners, and referral programs change frequently; your bio page needs to reflect current reality.
- Serve subscribers and visitors differently. They want different things and a single flat list of buttons fails both. Sub-collections solve this cleanly.
Then handle the obvious stuff (subscribe CTA, latest issue, social links, paid tier). In that order of priority: operational pain first, conventions second.
If you're just starting your newsletter: the four problems below mostly apply once you have 25+ issues and meaningful list size. If you're at issue 3 with 80 subscribers, your bio page only needs three things: a clear about block, your subscribe CTA, and your latest issue. Skip down to "The full structure" section for the complete layout, but don't overbuild yet. Your time is better spent on issue 4 than on archive sub-collections that have nothing in them.
The four problems generic advice doesn't address
Problem 1: Your archive is invisible after about 30 issues
Newsletter platforms have improved their archive UX, but the surface stops working at scale. Substack's archive is reverse-chronological by default, with tagging and section pages available but underused by most operators. beehiiv is similar in default behavior. Ghost gives you tags but most operators don't curate them. Kit has public profile pages with broadcast archives, but the archive UX is weaker than the others.
The result: your 47th issue, which might be your single best piece of writing, lives 8 scrolls deep on your archive page. New visitors don't find it. Returning subscribers who half-remember "that one issue about X" can't find it either.
This matters because back archive is your single highest-ROI growth asset. New subscribers who arrive via social referrals or recommendations need a way to evaluate whether you're worth subscribing to. Showing them only your latest issue is showing them one data point. Showing them a curated "if you're new, start here" path of 4 to 5 issues hand-picked to demonstrate range is showing them why their email is worth it.
What to do instead:
Organize your archive into discovery layers. Examples:
- "If you're new, start here" is 3 to 5 hand-picked issues that represent your range and best work. One-line context on each: "This one if you want X. This one if you want Y." Updated rarely.
- "Best of by topic" is sub-collections grouped by your recurring themes. A business newsletter might have Pricing & Strategy, Growth Tactics, Founder Interviews. A culture newsletter might have Profiles, Reviews, Essays.
- "Reader favorites": if your bio tool supports voting or visible click counts, this is the easy answer to "which issues should I read first?" The crowd-curated list often surfaces issues you wouldn't have picked yourself. Note: voting only generates meaningful signal once you have enough visitor traffic to produce votes (typically a few thousand monthly bio-page visitors). Smaller newsletters can use visible click counts as a similar mechanism, or stick with manual editor's picks until traffic builds.
- "Latest 4 issues": recent enough that returning subscribers can catch up.
- Year-in-review collections like "Best of 2025" or "Most-shared issues of 2024". Evergreen URLs you can link from current issues to drive subscribers back into your archive.
The mechanism that matters most here is unlimited collections. Tools that limit you to a single bio page or two "Featured" layouts can't handle this. You need separate, addressable sub-collections that link to each other and to a main hub.
Problem 2: Cadence is invisible to visitors
A visitor arrives at your bio page from a friend's recommendation. They have 8 seconds to decide whether to subscribe. They see your subscribe button and your last three issue titles. What they don't see:
- Whether you've published consistently for 6 months or 6 years
- Whether the next issue lands tomorrow or in three weeks
- Whether you're still actively writing or quietly winding down
Cadence is the trust signal that converts skeptical visitors into subscribers. Newsletter platforms surface this poorly. Substack shows "X subscribers" and a posting frequency on your homepage but the signal is weak. beehiiv shows it on hosted pages. Ghost typically doesn't unless you customize. Kit's public profile shows recent broadcasts but doesn't emphasize cadence.
What to do instead:
A "What you'll get" or "About this newsletter" block near the top of your bio page that explicitly states:
- Cadence: "New issue every Tuesday morning" or "Twice weekly, Mondays and Thursdays" or "Monthly deep-dives on the first of each month"
- Consistency: "Weekly since March 2023" is concrete, time-bounded, and verifiable
- What it's about: one sentence describing the focus. Specific beats clever. "Practical pricing strategy for B2B founders" converts better than "Thoughts on building things."
- What's free vs paid if you have a paid tier, surfaced clearly so visitors don't bounce when they hit a paywall they didn't expect
The "next issue lands [day]" specifically, even if it's not pinned to a literal day, having it visible on the page, is one of the highest-leverage trust signals you can add. It tells visitors you're committed and active, two things newsletter graveyards aren't.
If you publish on a less rigid schedule, frame it as a feature: "When I have something worth sending, usually 2 to 3 times per month." Honesty beats fake precision.
Problem 3: Cross-promotion and recommendations are operationally messy
Modern newsletter growth runs on cross-promotion. beehiiv has Recommendations and Boosts. Substack has Recommendations. The Sample, SparkLoop, Refind, and dozens of newsletter-recommendation services exist. Most operators using one or more of these end up with:
- 3 to 8 newsletters they're recommending or being recommended by, changing monthly
- Featured-swap partners for specific weeks
- Affiliate relationships with newsletter tools (beehiiv, ConvertKit, etc.)
- "Newsletters I read" sections in their welcome sequence
Your bio page should reflect what you currently recommend. But updating it every time a partnership changes is friction most operators skip. So most bio pages end up months out of date, listing newsletters the operator no longer reads, missing the new partner they actively want to send traffic to, with broken links to defunct projects.
What to do instead:
A dedicated "Newsletters I Recommend" sub-collection, separated from your main archive. Easier to maintain when it's its own surface rather than buried in a single flat link list. A few patterns that work:
- A small permanent set of 3 to 5 newsletters you genuinely read and would recommend regardless of any partnership. These rarely change.
- A rotating "currently featured" slot for active swaps and time-bounded partnerships. Update at the start of each campaign.
- Disclosure where relevant: if an entry is a paid recommendation or affiliate, label it. "Sponsored, and a newsletter I read anyway" converts better than hidden affiliations and keeps you credible.
- Past partners archive: optional, but useful for showing you've been around the network. Or just remove old partnerships entirely.
The win here is that recommendation revenue compounds when partners can actually find your bio's recommendation slot. A newsletter operator running active SparkLoop recommendations who's not surfacing them on their bio page is leaving real subscriber acquisition on the table. The partner who arrives at your bio expects to see themselves.
Problem 4: Your bio page is serving two audiences with one layout
Two distinct types of visitor arrive at a newsletter operator's bio page:
The visitor evaluating whether to subscribe. They've never read your work. They want to assess: is this person a real writer? Are they consistent? Do their topics match my interests? They want a curated path through your best work, social proof of your audience, and a clear subscribe CTA.
The existing subscriber looking for something specific. They already get your emails. They came to your bio because they want to find a back issue, share a specific piece, get to your paid tier, or reach out. They want fast navigation to a specific destination, not another subscribe pitch.
Generic link-in-bio advice treats these as the same audience. They aren't. A flat list of buttons that prioritizes "Subscribe" at the top works for visitor #1 but is annoying for visitor #2, who already gets your emails and doesn't need to be re-subscribed. A back-issue archive deep on the page works for visitor #2 but visitor #1 never reaches it.
What to do instead:
A bio page structure that serves both audiences in distinct sections:
- Top section: "New here?" orients visitor #1. Subscribe CTA, "if you're new, start here" recommended issues, the about/cadence block.
- Middle: latest content serves both. Latest 3 to 4 issues or current featured piece. Both audiences engage with this.
- Lower middle: "If you've been reading" orients visitor #2. Archive by topic, paid tier, recommendations, how to reply or contact. Subscriber-only resources if you have them.
- Bottom: secondary stuff. Social, contact form, sponsor inquiries, less-frequent navigation.
This pattern is harder to execute on tools that limit you to a single linear list of buttons. Platforms with section/grouping support, or with unlimited sub-collections that can be arranged in a layout, handle it cleanly.
If your tool doesn't support sectioned layouts, the workaround is two distinct landing pages: a subscribe page for new visitors (your generic bio link points here) and an archive or library page for subscribers (linked from your welcome email and footer). Both audiences end up where they want, neither has to wade through the other's content. Tools that cap your free plan at one page make this expensive; tools with unlimited collections make it free.
The full structure for a newsletter operator's bio page
Now that the four problems have answers, here's the full layout. Top to bottom in priority order:
1. Hero / About block Name, what you write, cadence. "Maren Holloway: weekly recommendations of underrated software tools for indie founders. Tuesdays since 2023."
2. Subscribe CTA Big, prominent, unambiguous. The single highest-conversion element on the page. If you have a paid tier, separate paid-vs-free clearly so visitors don't feel surprise-paywalled.
3. Latest issue Most recent send. Updated weekly (or whatever your cadence is). Auto-update if your tool supports it.
4. "If you're new, start here" 3 to 5 hand-picked issues. One-line context per issue. Updated rarely.
5. Best of by topic, sub-collections The thematic organization of your archive. Where unlimited collections matter.
6. Reader favorites Crowd-curated list of most-read or most-voted issues. Self-organizing if your tool supports voting; manually curated otherwise.
7. Paid tier (if you have one) What's behind the paywall, what subscribers get, founding-member options. Separate from the main subscribe CTA so visitors who want the paid tier specifically can find it.
8. Recommendations / newsletters I read Your cross-promotion surface. Honest disclosures where relevant.
9. Recent year archives "Best of 2025", "Best of 2024": evergreen collection links that drive traffic back into your archive months later.
10. Subscriber-only resources If you provide tools, templates, or perks to subscribers, they live here. Often gated behind your welcome email rather than public, but the link belongs on the bio page.
11. Reply / contact How to reach you. Newsletter operators often forget this and end up with their email scraped from a footer somewhere; better to surface it intentionally.
12. Social and elsewhere Below the fold. Twitter/X, LinkedIn, podcast appearances, your day job if relevant. Don't lead with these. They pull readers off the page.
A subtle but important point: most of these blocks are living, not static. Latest issue updates weekly. Featured issues rotate quarterly. Recommendations change monthly. Year-in-review collections refresh annually. The bio page is editorial work, not a setup-and-forget asset. Operators who treat it as living see better growth from it.
What most link-in-bio tools get wrong for newsletter operators
The category was built for influencers consolidating links. Newsletter operators have a different shape:
- Linktree, Stan Store, Bento, Carrd: built for the "single bio page with a list of links" pattern. Sub-collections for archive organization require workarounds. You build multiple "Featured Layouts" that can't easily reference each other, or you pay for a tier that unlocks more pages. None handle the visitor-vs-subscriber split natively. None have crowd-curation features for "reader favorites."
- Beacons: better at creator monetization (storefront, courses) but the same flat-list pattern for the bio page itself. No archive-specific organization.
- beehiiv's bundled bio page: native to your newsletter, decent for basic use. But locked to your beehiiv brand, weaker on sub-collections, and migrates poorly if you ever leave beehiiv.
- Custom websites: solve everything in theory. Most newsletter operators don't have time to build and maintain them. The "I'll do it later" trap.
The category gap most newsletter operators with 25+ issues hit: a tool that gives you unlimited collections (so archive organization works), supports the visitor/subscriber audience split, surfaces reader-curated favorites, and updates fast enough to keep up with rotating recommendation partners, without a paid plan that costs more than your newsletter platform.
This is where, in most "X for newsletter writers" articles, the author pretends their product solves everything. So here's the honest version.
Where Shelfy fits (and where it doesn't)
Shelfy.Today is a free link-in-bio and link curation tool. For newsletter operators, it does several things well and a few things not at all. The honest version:
Where Shelfy works for newsletter operators:
- Unlimited collections on the free plan. You can build a main hub, separate "best of by topic" collections, a recommendations collection, year-in-review archives, all linked to each other.
- Community voting lets readers upvote favorite issues. Your "reader favorites" section reorders organically based on what actually resonates. No other link-in-bio tool in the category has this. For curators and recommendation-driven newsletters specifically, this is the highest-fit feature in the category.
- Free custom domains mean you can use
read.yourname.cominstead of a generic link-in-bio URL. Brand independence matters more for newsletters than most categories. Your subscribers trust you, not your platform. - Follow + notify lets readers subscribe to be notified when you add new issues to a collection, separate from your email list. A second, lighter-touch audience capture for visitors not ready to give an email.
- Collection redirects are useful for "current featured issue" or "current swap partner". Publish
yourname.com/featuredand update where it points without changing the URL across all your social posts and welcome emails. - Real REST API means you can sync new issues from your platform automatically if you're technical enough to set it up. Beats manually adding every Substack post.
Where Shelfy doesn't fit:
- No native subscribe form integration. You can link out to your Substack/beehiiv/Ghost/Kit subscribe page, but you can't capture emails directly inside Shelfy. For some operators, this is a meaningful friction. (For others, those who want all subscriber capture happening on their newsletter platform anyway for analytics consistency, it's actually preferred.)
- No native subscriber-only gating. Subscriber-only collections are a manual workaround (private collection URLs shared via your welcome email) rather than a permission-based system.
- No automatic content import from RSS. You add issues manually or via the API. For high-frequency newsletters, this is real friction; for weekly publications, it's a 30-second weekly task.
The clean recommendation: if you want native email capture inside the bio page itself or automated RSS import, use a newsletter-platform-native bio tool (beehiiv's, or Substack's built-in homepage). If unlimited collections, voting, free custom domains, the visitor/subscriber split structure, and the ability to surface what readers actually like matter more, Shelfy works, and it's free forever.
Many newsletter operators run their actual subscribe form on their newsletter platform's homepage and use Shelfy as the bio-link curator that points there. That's a valid pattern; nothing forces you to pick one tool for everything.
A reasonable objection at this point: "If the actual signup happens on Substack/beehiiv anyway, why am I building a Shelfy bio page at all? Why not just point my Instagram bio at my Substack URL directly?"
The answer: your Substack URL is one page doing one job, convert a visitor to a subscriber. Your bio page is doing four jobs: orient new visitors, surface back archive for returning subscribers, manage rotating recommendations, handle paid-tier conversion separately from free. A platform homepage isn't designed for any of those. Pointing your Instagram bio directly at Substack works fine if your only goal is "subscribe button visible." It works less well once you have 30 issues to surface, two audience types to serve, and rotating swap partners to feature. The bio page is the curation/discovery layer; the platform is the capture layer; they serve different jobs and the right answer is often to use both, each for what it does well.
If you don't have 30 issues and don't run swaps, this is overkill. Point your bio at your subscribe URL and move on. The four problems exist for operators at scale.
Already convinced? Shelfy is free forever, every feature included. Try it now →
Or keep reading for the worked example, common mistakes, and FAQs.
A worked example: what this looks like in practice
Take a fictional newsletter, The Tuesday Tools, a weekly recommendation of underrated software tools for indie founders, designers, and PMs. ~18,000 free subscribers, ~250 paying at $8/month. Substack-based. Started March 2023.
The Shelfy page at tools.marenholloway.com would have:
- Top: "The Tuesday Tools: one underrated software tool every week for indie founders. Tuesdays since March 2023."
- Subscribe CTA: large, prominent, with paid-tier note: "Free weekly | $8/month for archive + reader chat | Founding member option"
- Latest issue: "#127, The CRM I switched to after Pipedrive's price hike"
- "If you're new, start here": 4 hand-picked issues representing the range. A tool review, a pricing analysis, a reader-favorite, a comparison piece.
- Best of by topic, sub-collections:
- Tool reviews (54 issues)
- Pricing breakdowns (12 issues)
- Indie founder interviews (8 issues)
- "What I'm avoiding" essays (15 issues)
- Reader favorites: same back catalog, reordered by reader votes. Some surprises here, things Maren wouldn't have picked.
- Paid tier landing: separate page explaining what's behind the paywall.
- Newsletters I recommend: 4 permanent picks + 2 currently featured swap partners, with sponsored disclosure where relevant.
- 2024 Year in Review: top-voted and editor's-choice issues from last year.
- Reply or pitch: how to reach Maren, including pitching a tool for review.
- Social: Twitter/X, occasional podcast appearances.
The whole structure takes 2 to 3 hours to set up initially and ~10 minutes per week to maintain. Latest issue updates weekly. Featured swap partners rotate per campaign cycle. Recommendations refresh quarterly. Year-in-review pages get built once a year and link permanently.
Common mistakes to avoid
A few patterns that hurt newsletter operator bio pages specifically:
Burying the subscribe CTA. It's the highest-conversion element on the page. It belongs near the top and again near the bottom. Listing it third under "Latest issue" and "Social" reverses the funnel.
Using Substack/beehiiv's hosted page when you have audience equity to migrate. Building backlinks and audience trust on yourname.substack.com accumulates equity for the platform, not for you. If you might ever leave (and most operators do, eventually), every social bio update is wasted leverage. Custom domains are the fix.
Mystery cadence. If your bio doesn't tell visitors when issues land, you're asking them to commit to an unknown. "Tuesdays since 2023" is a 4-word trust signal that meaningfully improves conversion.
Outdated recommendations and partners. A bio page recommending newsletters the operator stopped reading 8 months ago is worse than no recommendations at all. It signals neglect. Either maintain it or remove it.
Treating the bio page as static. Newsletter operators are publishers. Bio pages need editorial maintenance, not just initial setup.
One CTA for everything. A subscribe CTA, a paid-tier CTA, a recommendations CTA, and a "reply to me" CTA each serve different visitor intents. Bundling them into a single button list dilutes all of them.
Writing for a generic creator audience. Your bio page should feel like you. Newsletter operators have voice; their bio pages should too. Generic creator-marketing copy converts worse than copy that sounds like the actual writer.
Ignoring the data. Whatever tool you use, look at what readers actually click. The "if you're new, start here" issue you picked might not be the one that converts visitors to subscribers. Update based on data, not gut.
Try Shelfy free for your newsletter
If the operational problems above sound familiar (invisible archive, cadence trust gap, recommendation partner churn, or the visitor/subscriber split) Shelfy is free forever, every feature included.
Build your newsletter bio page in 10 minutes →
If you're weighing tools, the Shelfy vs Linktree comparison and Shelfy vs Beacons comparison cover the alternatives in detail. Different tools, different verdicts.
If you also publish on YouTube, the link in bio for YouTubers guide covers the equivalent operational lens for sponsor rotation, gear lists, and multi-topic channels. The same logic in a different format.
Frequently asked questions
Do I still need a link-in-bio tool if I'm on Substack or beehiiv?
It depends. Substack and beehiiv both give you a hosted homepage that serves as a basic bio surface, adequate if you only want a subscribe button and an archive. You'd benefit from a separate link-in-bio tool if you're on multiple social platforms and want more control over what visitors see, want sub-collection organization for your archive, want features like community voting or follow-and-notify, or want to use a custom domain that survives any future platform migration. For newsletter operators staying on one platform with simple needs, the platform's native homepage is fine.
How do I add a subscribe form to my Shelfy bio page?
Shelfy doesn't capture emails directly inside the bio page. You'll add a prominent button that links out to your newsletter platform's subscribe URL (Substack, beehiiv, Ghost, Kit, etc.). For most operators, this is preferred because subscriber capture stays consistent with their main platform's analytics. If you specifically need native email capture inside the bio page, beehiiv's or Substack's built-in homepage handles this; for operators where this is a hard requirement, those tools are a better fit.
Last reviewed: May 2026. Newsletter platform features and recommendation network tools change regularly. Verify current details before publishing strategic decisions.

