How to Create an Embedded “Save This Recipe” Form in 4 Steps

Home » Blog » How to Create an Embedded “Save This Recipe” Form in 4 Steps

An embedded “Save this Recipe” form can turn casual readers into subscribers without disrupting their flow. In this guide, I’ll show how to create a save this recipe embedded form that fits your design, loads fast, and captures the right details.

I’ll focus on practical placement, targeting, and setup steps I use in these cases. You’ll see where the form belongs in a recipe post, how to connect it to your email capture, and how to test it before publishing.

By the end, you’ll have a clear, repeatable process to launch a trustworthy, on-brand form that increases signups and gets readers back to your recipes later.

What you’ll learn in this tutorial:

i 3 Table Of Content

If you prefer a click-to-open option instead, read How to Create a Save This Recipe Popup Triggered by Click, then compare results after launch.First up: what an embedded “Save this Recipe” form is, and when to use it.

What an Embedded “Save Recipe” Form Is, and When to Use It

In short: an embedded “Save this Recipe” form is a small HTML form placed directly inside your recipe post. It lets readers enter their email so you can send the recipe link, and optionally a brief summary straight to their inbox. Because it lives in the content (not a popup), it stays visible as people scan ingredients or steps, keeping friction low.

Why not auto‑trigger a popup? When a popup appears just seconds after someone lands on a post, many readers will close it immediately. On blog posts, I prefer either a popup that opens only on button click AND/OR an embedded form placed in strategic spots within the content.

Embedded forms work especially well on mobile, where popups can feel cramped. You can also control exactly where the form shows by limiting it to certain recipe URLs or categories, and excluding others using rules like “is,” “contains,” “begins with,” “ends with,” and wildcard matching. You can target by device as well, ensuring the form only appears on desktop, tablet, or mobile as needed.

Use an embedded form when:

Longer prep recipes, meal plans, and batch‑cooking posts; any scenario where readers want to save the recipe for later.
Intent‑driven sections like after Ingredients or near Step 1, when readers are deciding to try the dish.
If you want to compare results, test a button‑triggered Popup Box version alongside your embedded form.

Include these by default:

Ask for the minimum (email only, or email plus first name). Add more fields later with progressive questions to keep friction low. For a deeper dive into why fewer, clearer fields win, see Baymard’s analysis of form-field counts and friction; while this analysis is centered on ecommerce, the principles carry over to email capture.
Keep labels clear and helper text brief so the form is scannable.
Include a consent checkbox when required to meet privacy rules.
Use targeting rules (URL patterns, device, audience) and exclude existing subscribers or anyone who already completed your progressive fields.

Where to Place It on Recipe Posts and Why

As a rule of thumb, put the form where intent peaks. In testing, I see higher engagement when the form sits near the Ingredients list or just below the first step. The reader is already committed, and a “Save this recipe” action feels natural there.

High-performing locations are:

Below Ingredients: Readers have scanned what they need and want to save the list. Pair with a short call to action like “Email me this recipe”.
After Step 1: Momentum is high; the save action feels like progress, not distraction.
End of Post: Good as a secondary instance for readers who scroll all the way through.

To prevent clutter, add the embedded form only in strategic sections. If you’ve placed the same form across posts and other pages but want it limited to recipes, use display rules so it appears only on recipe URLs (not on non‑recipe pages). You can target by exact URL, URL fragments, or patterns using “contains”, “begins with”, or “ends with” for flexible placement across templates.

Once you’ve picked your placements, test in a safe environment to confirm targeting, form behavior, and post‑submit actions.

Try it first in a test environment

Before you go live, you can get a free test environment. It lets you implement the steps, preview on desktop and mobile, and confirm everything works end to end. Run these quick checks to catch targeting or submission issues early:

Fields: Only the fields you intend should load; keep it minimal for higher completion.
After‑submit: Confirm the thank‑you message, redirect, or email sends as expected.
Display rules: If you only want the form on recipe pages, set URL targeting (is, contains, begins with, ends with, wildcard) so it doesn’t appear site‑wide.
Devices: Make sure device targeting behaves as expected across desktop, tablet, and mobile.

Step‑by‑Step to Build the “Save Recipe” Embedded Form

Here’s the process I recommend. It’s fast, reliable, and easy to scale across recipes. I’ll reference key settings you can copy.

Create the form

Go to Site > Popups & Forms.
Open the Popup Templates tab.
Search for:

Save This Recipe | In Recipe Post | Embedded | 1

Click the three dots (⋮) and choose Copy to Popups & Forms.

Edit basic details

In Popups & Forms, find the copied embedded form and click (⋮), then Edit.
Rename if you like (e.g., “Save Recipe | Embedded Form”) or keep the template name.
Add a clear description, for example:

This ‘Save Recipe’ form emails a recipe link and short summary after submission.

Click Continue to edit settings.

Set as a Lead Gen Form

From the form’s menu options (⋮), select Set as Lead Gen Form. This makes the embedded form selectable during the email capture campaign setup, and integrates with your after-capture actions.
You’ve just enabled the form to fit into your email capture flow; next, confirm fields and the submit action so it routes correctly.

Form and submit behavior

Click the Design button (bottom‑right) to open the builder.
Confirm fields (First Name, Email) and microcopy.
In the form content module, set Submit action to Lead Form.
Click Save.

There you have it! your embedded form is configured, targeted, and ready to route submissions. Now, let’s cover the most frequently asked questions about the “Save this Recipe” embedded form.

FAQs

Is an embedded form better than a popup?

Short answer: it depends on your readers and placement. Start with an embedded form near Ingredients (high‑intent moment), then A/B test a button‑click popup near the top.

When you test, compare:

Completion rate (form submissions vs. views)
Dismiss and close rate
Mobile vs. desktop performance

You can also run both: keep an in‑post embedded form and add a click‑to‑open popup. Because both are intent aligned, and reader initiated, they rarely disrupt the recipe experience. Just cap frequency and exclude existing subscribers to prevent overexposure.

Do I need plugins or advanced skills?

No. Most setups involve pasting an embed or iframe code, plus installing a tracking script.

Can I limit which pages show the form?

Yes. use URL rules like “is,” “contains,” “begins with,” “ends with,” or wildcards to include categories or specific templates. This keeps how to create a save this recipe embedded form only scoped to recipe posts.

Can I target by audience or device?

You can display the form to all visitors or filtered segments (e.g., returning readers, people on a list, or by referral), and choose devices (desktop, tablet, mobile).

How do I test safely?

Use the test environment to validate the trigger, fields, and post‑submit action across desktop and mobile before you roll it out site‑wide.

What should I measure?

Track form views, submissions, and conversion rate.

Next step: Create an email capture campaign for your “Save this Recipe” flow. Connect the embedded form so you can start collecting emails and building richer subscriber profiles.

Save This Post

Get Test Demo

Try It Free