Why Recipe Cards in Emails Convert 3x Better Than Links

Every food creator faces the same dilemma: you’ve spent hours developing a recipe, testing it, photographing it, writing it up. Now you want to share it with your email subscribers. So you write a teaser, drop in a link to your blog, and hit send.

Here’s the problem: most of your subscribers will never click that link.

The click-through problem

Industry data shows that average email click-through rates hover around 2-3%. Food and cooking newsletters tend to perform slightly better, around 3-5%, because the content is highly visual and personal. But that still means 95% of your subscribers read your email and never see the recipe.

This is not because your recipes aren’t good. It’s because you’re asking people to leave their inbox. Every click is a decision point, and most people choose not to decide. They’ll read your email, maybe enjoy the teaser, and move on.

What happens when the recipe is in the email

When you embed a recipe card directly in the email — with the title, photo, ingredients, timing, and a beautiful layout — something different happens. The subscriber sees the recipe without clicking anything. They engage with your content right where they are.

Food creators who switched from link-based emails to embedded recipe cards report three key changes:

Higher engagement rates. When subscribers don’t have to click to see the recipe, more of them actually read it. We’ve seen engagement rates (measured by time spent, saves, and replies) increase by 3x or more compared to link-only emails.

More recipe saves. Including a “Save This Recipe” call-to-action inside the email card gives subscribers a low-friction way to interact. Saving is easier than clicking to a blog, bookmarking the page, and hoping you remember where you put it. Save rates on embedded cards run 4-6% of recipients, compared to 1-2% click-through on links.

Better subscriber data. Every save is a signal. When a subscriber saves your vegan Thai curry, that tells you something about their preferences. Over time, these signals build a detailed picture of what each subscriber wants to eat. You can’t get that data from a blog link click.

How it works technically

Email clients are notoriously limited in what they can render. No JavaScript, limited CSS, inconsistent image handling. That’s why most food creators default to images or links — it’s hard to make structured content look good in email.

Dough solves this by rendering recipe cards as HTML tables — the same technique that email marketers have used for decades to ensure consistent rendering across Gmail, Outlook, Apple Mail, and every other client. The recipe card includes the photo (hosted on our CDN for fast loading), ingredients, timing, nutrition highlights, and a prominent CTA button.

You don’t have to write HTML tables. Dough’s Kit editor plugin lets you search your recipe library and insert a card with one click. The HTML is generated automatically and optimized for every major email client.

The strategy shift

Moving from link-based emails to embedded recipe cards is more than a formatting change. It’s a strategy shift. Instead of using email to drive traffic to your blog, you’re using email as the primary content experience. Your blog still exists, but the email becomes the first place subscribers experience your recipes.

This shift has downstream effects. Your blog becomes more focused on SEO and new audience discovery, while email becomes your engagement and monetization channel. You can include recipe cards alongside product recommendations, seasonal meal plans, and subscriber-only content — all without asking anyone to click away.

Getting started

If you’re using Kit and you want to try embedded recipe cards, Dough makes it straightforward. Import your recipes, install the Kit editor plugin, and start dropping cards into your next broadcast. The difference in engagement is immediate and measurable.

Stop asking your subscribers to leave their inbox. Bring the recipe to them.