Why put recipes on a store?
Three reasons, for a food, drink or kitchenware brand.
People search for dishes, not for your product. A recipe for chili oil noodles can be found by someone who has never heard of your chili oil. The recipe shows the product in use, which a product photo can’t. And when an ingredient is something you sell, the reader can add it to the cart from the recipe.
What Google needs for recipe results
Google builds recipe results (photo, rating, cooking time) from Recipe structured data. Two properties are required: name and image. The recommended ones make the result useful: prepTime, cookTime and totalTime, recipeIngredient, recipeInstructions, recipeYield, nutrition.calories, aggregateRating, author and datePublished (Google Search Central).
Unlike FAQ results, which Google ended in 2026, recipe results are still shown. Markup makes a page eligible; it doesn’t guarantee the result.
A normal blog post has none of this markup. That’s the gap the three routes below close, or don’t.
Route 1: recipes as blog posts
Best for a few recipes, when being found through Google’s recipe results doesn’t matter to you.
- In the admin, go to Content › Blog posts, click Manage blogs and add a blog called Recipes.
- Add a blog post. Title: the name of the dish. Featured image: the finished dish.
- In the content, write a short intro, then an H2 “Ingredients” with a bulleted list and an H2 “Method” with a numbered list.
- Link ingredients you sell to their product pages.
- Add tags from your tag plan and publish.
What’s missing: no Recipe markup, so no recipe result in Google. No fixed card, so every post looks slightly different. No print view, no servings or times in a consistent place, and no add-to-cart button next to an ingredient.
Route 2: metaobjects and theme code
Best for stores with a developer, or an owner at home in Liquid, who want full control and no subscription.
A metaobject is a custom content type with fields you define. Shopify can publish each entry as its own page (Shopify Help Center).
- Go to Settings › Custom data (or Content › Metaobjects) and add a definition called Recipe.
- Add fields:
title(single line text),image(file, image),description(multi-line text),published(date),prep_minutesandcook_minutes(integer),servings(single line text),ingredients(single line text, list),steps(single line text, list) andproducts(product, list). - Under Features, select Web pages, and save.
- In the theme editor, open the page selector and choose the Recipe metaobject template. It starts empty (shopify.dev). Add sections and connect them to the recipe’s fields.
- Add a Custom Liquid section to the same template and paste the markup below.
{%- liquid
assign prep = metaobject.prep_minutes.value | default: 0
assign cook = metaobject.cook_minutes.value | default: 0
assign total = prep | plus: cook
-%}
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Recipe",
"name": {{ metaobject.title.value | json }},
"image": [{{ metaobject.image.value | image_url: width: 1600 | prepend: 'https:' | json }}],
"description": {{ metaobject.description.value | json }},
"author": { "@type": "Organization", "name": {{ shop.name | json }} },
"datePublished": {{ metaobject.published.value | date: '%Y-%m-%d' | json }},
"prepTime": "PT{{ prep }}M",
"cookTime": "PT{{ cook }}M",
"totalTime": "PT{{ total }}M",
"recipeYield": {{ metaobject.servings.value | json }},
"recipeIngredient": {{ metaobject.ingredients.value | json }},
"recipeInstructions": [
{%- for step in metaobject.steps.value -%}
{ "@type": "HowToStep", "text": {{ step | json }} }{% unless forloop.last %},{% endunless %}
{%- endfor -%}
]
}
</script>Times are written in ISO 8601 form (PT25M is 25 minutes), which is the format in Google’s examples. Leave aggregateRating out unless real customers rated the recipe.
Limits: you build the visible recipe page yourself from theme sections, and the field keys in the snippet must match your definition exactly. A theme change means rebuilding the template. There are no ratings, no print view and no add-to-cart button unless someone codes them. If you get stuck fitting this to your theme, write to service@ahoiapps.com with your theme’s name.
Route 3: a recipe app
Best for anyone who wants recipe cards, markup and linked products without code.
A recipe app gives you a form for ingredients, steps, times and servings, renders a consistent card, writes the Recipe JSON-LD, and links ingredients to products. Facts below are from each Shopify App Store listing on 17 Nov 2026.
- Recipe Kit ‑ Blog Post Recipes: free for 5 recipes, then from $25/month. 4.9 from 107 reviews. Adds nutrition labels and analytics per recipe.
- Recipe Stack—Sell with Recipes: from $14/month for 50 recipes, 30-day trial. 4.2 from 15 reviews. Shows recipes on product pages and has filters by cuisine or diet.
- Ahoi Apps: Easy Recipe Pages is ours: from $0.99/month, 14-day free trial. Recipes live in your store’s blog and the app adds the recipe as a theme section. Every plan includes unlimited recipes, Recipe JSON-LD, products linked to ingredients with add-to-cart buttons, customer ratings, translations, multiple images for directions, social sharing and blog tag filters.
Limits, honestly. Easy Recipe Pages has no reviews yet and no free plan. Its listing doesn’t state a recipe block for product pages, nutrition facts, analytics, a print view, search inside recipes or an import; Recipe Kit and Recipe Stack name several of those. All five apps we looked at are in best recipe apps for Shopify.
Recipes on product pages
To show “recipes with this product” on a product page, you need a link from the product to its recipes.
With metaobjects: add a product metafield of type Metaobject (list) that points to your Recipe definition, with the key custom.recipes. Pick the recipes on each product. Then add a Custom Liquid block to the product template:
{%- assign recipes = product.metafields.custom.recipes.value -%}
{%- if recipes != blank -%}
<h2>Recipes with {{ product.title | escape }}</h2>
<ul>
{%- for recipe in recipes -%}
<li><a href="{{ recipe.system.url }}">{{ recipe.title.value | escape }}</a></li>
{%- endfor -%}
</ul>
{%- endif -%}With an app: check the listing for a product page block. Recipe Stack and BentoSMB Recipes state one. Easy Recipe Pages doesn’t: its recipes sit on blog posts and link to products from the ingredient list, so the path runs from recipe to product. For the other direction, link the recipe posts by hand in the product description.
A recipe collection people can search
Plan the index before the tenth recipe, because retagging fifty posts is no fun.
Decide on four groups of tags and stick to them: cuisine (Italian, Thai), course (breakfast, dessert), diet (vegan, gluten-free) and main ingredient (chickpeas, salmon). One or two tags per group, spelled one way.
What each route can filter:
- Blog posts and tag-based apps: by tag, through
/blogs/recipes/tagged/vegan. Combining tags works in the URL but needs an interface; the snippets are in our guide to blog categories and filters. - Metaobjects: whatever you build. Fields for cuisine or diet can drive a custom index page, in code.
- Apps: check each listing. Recipe Stack and Recipe Junction name their own recipe filters; Recipe Kit and Easy Recipe Pages use blog tags.
A food blog you already have elsewhere
You have two choices. Keep the blog where it is and link to it from the store’s menu, which Shopify’s Help Center describes as an option. Or move the recipes.
What moves cleanly: titles, text and images. What usually doesn’t: the recipe cards of a WordPress plugin, which are stored in the plugin’s own format, and the ratings attached to them. Expect to re-enter ingredients and steps in whichever route you chose above. For every moved recipe, redirect the old URL to the new one, so existing links keep working.
Checklist: what a good recipe page needs
- One H1, which is the name of the dish.
- A photo of the finished dish, at least 1,200 px wide.
- Prep, cook and total time, visible and in the markup.
- Ingredients as a list, one per line, with amounts.
- Steps numbered, one action each.
- The ingredients you sell linked to their products.
- A print or jump-to-recipe link if the intro is long.
- A pass in Google’s Rich Results Test with Recipe detected.
Mistakes we see most
- The recipe as an image. A pretty recipe card saved as a JPEG can’t be read by Google, a screen reader or a phone at arm’s length.
- Ingredients in a paragraph. Nobody shops from a sentence.
- Two Recipe blocks. A theme snippet plus an app both writing Recipe markup gives Google two versions. Keep one.
- Ratings the store made up. Ratings in markup have to come from real users (Google’s review snippet guidelines). Five stars from the owner is a policy problem, not a growth tactic.
- A tiny photo. Google asks for high-resolution images in 16:9, 4:3 and 1:1. Sizes are in Shopify blog image size.
- Thirty recipes that never mention a product. Then it’s a cooking blog, with a shop attached somewhere else.