Help readers find and return to your recipes

Your publication is public. How do you get the first readers to it? Start with the audience that already asks you for recipes, and give them a direct link to one dish.

Share your first recipe from Instagram

1. Choose View website on your Crumb dashboard and copy the homepage address.
2. In Instagram, use Edit profile → Links → Add external link and paste it. Use a label readers will recognize, such as “My recipes”.
3. Open a free, public recipe on your publication and copy its address.
4. Create a Story with a photo of that dish. Add a link sticker and paste the recipe link.
5. Tell readers what the link opens. For example: “The full tomato toast recipe is on my website. Tap to cook it, and subscribe for new recipes.” Adapt the wording to your dish and voice.

Before sharing, open the link in a signed-out browser. It should show the recipe without a dashboard login or private preview. If it does not, check your publishing status.

Give every post a destination

When you publish a recipe on Crumb, use its direct link in a Story, email, or another place where readers can follow it. In a regular Instagram caption, direct readers to the link in your bio. A direct recipe link is more useful than sending someone to a homepage and asking them to search.

Use the same recognizable title and cover image across both places. Readers should immediately know that they reached the recipe they saw in your post.

Build a useful archive

A large recipe count is less important than a collection that is easy to understand. Start with the recipes your audience already asks for, then:

• group them into clear categories such as weeknight dinners or baking;
• write titles using the words a reader would search for;
• include useful timing, yield, and substitution notes;
• link back to older recipes when a new one pairs well with them;
• keep seasonal favorites updated before interest peaks.

Invite readers to subscribe

Public Crumb sites can collect reader email addresses. Your dashboard shows subscriber status and source, and lets you search, filter, and export the matching list as CSV.

Explain what someone will get before asking them to subscribe. A specific promise such as “one new weeknight recipe each Friday” is stronger than a generic “join my newsletter.” Only promise a schedule you can maintain.

When publishing recipes, review the email announcement choice. You can publish without emailing, or prepare an announcement for your subscribers. Check its delivery status in the dashboard; publishing a recipe and sending an email are separate outcomes.

Check whether someone subscribed

Open Audience overview on the dashboard to check visits and subscribers. Open Subscribers to look for new active subscribers who are not your own test addresses. A reader may visit and cook without subscribing, so a quiet list does not prove that nobody opened the recipe.

If there is little response, check the public link again and make the next invitation more specific: show the dish, say what is on the page, and point to the link. You can ask one reader whether they could find and open it before changing the whole website.

A simple launch rhythm

For your first few weeks:

1. Publish the strongest recipes from your existing archive.
2. Add the Crumb site to your social bio.
3. Share direct recipe links when you post or resurface a dish.
4. Notice which recipes and categories readers ask for again.
5. Improve the archive based on those real questions.

Consistency matters more than publishing everything at once. A smaller collection that readers can trust is a better foundation than a large import that has not been reviewed.

Next guideOwnership, exports, domains, and monetization →