One Substack Post Can Serve Four Tiers—but Crawlers See Only One

Substack lets one post vary selected sections for four reader states: not subscribed, free subscriber, paid subscriber, and founding subscriber. The shared article stays in the ordinary editor, while targeted blocks can change a call to action, exercise, offer, example, or acknowledgment according to the reader’s subscription status.

The distribution rule is just as important as the personalization. Logged-in readers and email recipients receive the applicable version, but Substack’s official instructions specify that RSS feeds and search-engine crawlers receive only the Not subscribed rendering of each audience section. That public version therefore needs enough context to make sense on its own.

Create the first audience-specific block

Write the material every reader needs in the ordinary draft. Where the post should diverge, open More, select Audience-specific content, choose a prepared option or define a custom audience, and add the targeted material. An independent walkthrough of the editor control shows that the block can also include optional alternative content for readers outside the selected audience.

1. Keep the post’s essential argument, instructions, and context outside conditional blocks.
2. Insert a block where subscription status changes what is useful to show.
3. Select the intended audience; combine reader groups when they need the same version.
4. Add a coherent For everyone else alternative when omission would create an awkward transition or missing explanation.
5. Use Preview to inspect the result for each reader state before publishing.

A block should perform a specific editorial job, not conceal an entire parallel article. If nearly every paragraph is conditional, revisions become harder to follow and the public rendering may lose the context needed to represent the post accurately.

Map the four reader states before writing

Plan the variants as a small matrix before inserting blocks. For each state, identify what the reader already has and what information or action is relevant next. This avoids asking paid members to purchase access they already own or showing visitors instructions for a benefit they cannot use.

• Not subscribed: preserve the section’s meaning, then offer a relevant reason to subscribe if one belongs there.
• Free subscriber: recognize that the reader is already subscribed and describe a specific paid benefit only when it relates to the post.
• Paid subscriber: replace acquisition copy with the promised material, an eligible offer, or a useful next resource.
• Founding subscriber: show the paid version when the next step is identical, or provide a distinct benefit or acknowledgment when the founding tier carries an additional promise.

Four available states do not require four different messages. Paid and founding subscribers can share a block, while not-subscribed visitors and free subscribers can share another. Split them only when the difference changes the content’s meaning, eligibility, or next action.

Use reusable blocks for distinct editorial jobs

The strongest patterns are modular. Gabby Gazdag’s implementation examples demonstrate differentiated endings, exercises, case-study depth, product offers, and messages for paying or founding readers within one post.

In a call-to-action block, a visitor can receive a subscription invitation, a free reader can see the relevant reason to upgrade, and a paid member can be directed to the next resource instead. Publishers refining these endings can adapt a few context-specific CTA patterns rather than repeating the same conversion request in every view.

An exercise block might give all readers a complete basic exercise while adding deeper prompts or a worksheet for eligible members. A case-study block can keep the conclusion and necessary evidence public while reserving a detailed process or troubleshooting notes for a member version. These are editorial patterns, not rules imposed by Substack.

A product block can separate a visitor-facing introduction, a free-subscriber upgrade path, and access instructions for eligible members. An acknowledgment block can thank paid readers without showing them acquisition copy, while a founding-only message should reflect a real distinction in the publication’s membership offer.

Keep restricted fulfillment details inside the selected audience’s content. A download link, discount code, private invitation, or answer key intended only for eligible members does not belong in shared prose or in the alternative displayed to everyone else.

Preview every identity—and treat the public view as canonical

Review the post as not subscribed, free, paid, and founding. Read the transition into and out of every conditional section, rather than checking the block in isolation. Each rendering should remain grammatical, preserve necessary context, and offer an action appropriate to the reader’s existing access.

• Confirm that the shared article remains intelligible in all four views.
• Check that restricted links, codes, answers, and invitations appear only for eligible readers.
• Remove subscription or upgrade prompts from readers who already have the requested access.
• Inspect links, embeds, images, offer terms, and time-sensitive wording in every visible variant.
• Read the not-subscribed rendering as a complete public page.

The crawler does not receive all four variants as separate searchable material. Because RSS and search systems receive the not-subscribed rendering, subject-defining language placed only in a paid or founding block should not be expected to provide public search context or appear in the publication’s public feed.

The final public-view check has two goals: restricted material must remain outside the not-subscribed rendering, and the visible section must still explain what the post is about. Once that version stands alone, the subscriber blocks can concentrate on relevance without weakening the public article.

Also read:

• Four Blog CTAs That Move Readers Forward Without Blocking the Article
• YouTube Subscribers Help a Business, but the Count Is Not the Audience
• Write a How-To Post Readers Can Finish Without Guessing