A recipe card plugin is the most important piece of infrastructure for a food blog. It produces the formatted recipe box readers expect, generates the Recipe schema Google needs, and unlocks rich snippet eligibility in search results. This post is the practical setup.

Short answer: The three main options are WP Recipe Maker, Tasty Recipes, and Create by Mediavine. WPRM has the most features (and most complexity). Tasty Recipes is the cleanest UX. Create is free if you’re with Mediavine. Configure schema, print button, jump-to-recipe, and nutrition automatically.
A formatted recipe card on a food blog showing ingredients, instructions, and rating stars

Why a recipe card plugin matters

Without a recipe card plugin:

  • Recipes appear as plain text. Hard to scan.
  • No Recipe schema = no rich snippets in Google.
  • No “jump to recipe” button = annoyed readers.
  • No print button = inconvenient for cooks.
  • No structured nutrition info.
  • Pinterest Rich Pins won’t show recipe details.

With a plugin: all of the above, plus the recipe is a structured object Google can understand and surface.

WP Recipe Maker

The most popular recipe plugin. Free core + paid premium.

Pricing

  • Free: basic recipe card, schema.
  • Premium: $79/year.
  • Pro: $129/year.
  • Elite: $179/year.

Strengths

  • Most features of any recipe plugin.
  • Strong schema implementation.
  • Recipe import from other plugins.
  • Multiple recipe templates.
  • Nutrition calculator (premium).
  • Recipe analytics.

Weaknesses

  • Heavy interface — lots of settings.
  • Some features locked behind tiers.

Tasty Recipes

Made by WP Tasty. Paid only.

Pricing

  • $79/year single site.
  • $199/year up to 5 sites.

Strengths

  • Cleanest UX of the three.
  • Beautiful default styling.
  • Strong “jump to recipe” feature.
  • Good schema.
  • Easy to use even for non-technical bloggers.

Weaknesses

  • Fewer advanced features than WPRM.
  • Paid only (no free tier to try).

Create by Mediavine

Made by Mediavine (the ad network). Free for all users.

Strengths

  • Free.
  • Performance-optimized (Mediavine cares about ad load).
  • Decent feature set.
  • Schema built in.

Weaknesses

  • Fewer features than paid options.
  • Mediavine-centric defaults (some integrations only matter to Mediavine publishers).

Which to choose

  • Just starting: Create by Mediavine (free) or WP Recipe Maker free tier.
  • Want clean UX: Tasty Recipes.
  • Want max features: WP Recipe Maker Premium or Pro.
  • On Mediavine ads: Create (already optimized for them).

Schema configuration

Recipe schema is the structured-data format Google needs for recipes. All three plugins generate it. Verify it’s complete:

  • Recipe name.
  • Image (large, high-quality).
  • Description.
  • Prep time, cook time, total time.
  • Yield / servings.
  • Ingredients (structured list).
  • Instructions (structured steps).
  • Nutrition info (optional but helpful).
  • Author.
  • Date published.
  • Category (e.g., Dinner).
  • Cuisine (e.g., Italian).
  • Keywords (recipe-specific).
  • Aggregate rating (if you have reviews).

Test with Google’s Rich Results Test (search.google.com/test/rich-results).

Jump-to-recipe button

Critical UX feature. Lets readers skip past your intro and life story to the recipe.

All three plugins offer this. Place it:

  • At the top of the post.
  • Optionally a second button mid-post.
  • Sticky / floating button on long posts.

Readers who can’t quickly reach your recipe leave. Make it impossible to miss the button.

Print button

Print-friendly recipe button strips ads and unrelated content, formats nicely for paper.

All three plugins offer print functionality. Enable it.

Nutrition information

Display nutrition per serving. Plugins offer:

  • Manual entry (you fill in values).
  • Automatic calculation (premium feature, calculates from ingredients via API).
  • External services (Nutritionix, Edamam) accessed via plugin.

Worth it because:

  • Health-conscious readers expect it.
  • Adds to schema (Google may show it).
  • Useful for searches like “low-carb dinner.”
Recipe card showing nutrition information panel with calories, protein, carbs, and fat per serving

Ratings and reviews

Recipe ratings and reviews matter:

  • Show as stars in Google search results (powerful click-through booster).
  • Trust signal for readers.
  • Engagement signal.

Enable the rating feature. Encourage commenters to rate.

Google has tightened review schema policies — ensure you only display reviews you actually received. Don’t fabricate.

Recipe categorization

Recipes need taxonomy:

  • Course (Breakfast, Dinner, Dessert).
  • Cuisine (Italian, Mexican, etc.).
  • Diet (Vegan, Keto, Gluten-Free).
  • Cooking method (Slow Cooker, Air Fryer, Grill).
  • Main ingredient (Chicken, Pasta, etc.).

Most plugins create custom taxonomies for these. Configure them so readers can browse recipes by category.

Recipe templates

Most plugins offer multiple visual templates. Pick one and stick with it. Consistency across your blog matters.

Test on mobile — that’s where most readers will see recipes.

Featured image best practices for recipes

  • Bright, well-lit photo of the finished dish.
  • Overhead shot or 45-degree angle works best.
  • Include a hint of “scale” (utensil, garnish).
  • Square or vertical crops work best on Pinterest.
  • Multiple aspect ratios stored: hero (1200×800), Pinterest (1000×1500), square (1000×1000).

Recipe-specific SEO

  • Recipe name includes the search term (people search “chicken pot pie recipe”).
  • Title format: “Recipe Name | Blog Name” or “Easy [Recipe Name] Recipe.”
  • Meta description includes prep time, key ingredients, occasion.
  • FAQ section covering common questions (substitutions, storage, reheating).
  • Internal links to related recipes.

The “story” before the recipe

Food bloggers are mocked for long pre-recipe stories. Reality:

  • Pre-recipe content is necessary for SEO (Google wants context).
  • Tips and FAQ before the recipe help rankings.
  • Provide value beyond just the recipe (substitutions, technique tips, why this version is good).
  • BUT: provide a clear jump-to-recipe button so readers in a hurry can skip.

The balance is real content + easy bypass.

Migrating recipes between plugins

Switching recipe plugins is painful — recipes stored in one plugin’s format don’t always transfer cleanly.

WP Recipe Maker has the best import features. Tasty Recipes and Create have more limited imports.

Pick carefully the first time. Migrating 200 recipes is a real cost.

Performance impact

Recipe plugins add some load. Mitigations:

  • Disable features you don’t use.
  • Use a caching plugin to cache recipe pages.
  • Optimize recipe images aggressively.

Recipe video integration

If you make recipe videos, the plugin can:

  • Embed video at the top of the recipe card.
  • Add VideoObject schema linked to the recipe.
  • Display custom thumbnails.

Host on YouTube or Vimeo, embed via the plugin.

The honest summary

A recipe card plugin is non-negotiable for food blogs. WP Recipe Maker offers the most features; Tasty Recipes the cleanest experience; Create by Mediavine is free. Configure schema completely, enable jump-to-recipe and print buttons, add nutrition info, and use ratings. Pick one plugin and commit — migration is painful. The recipe card transforms a recipe blog from “casual hobby” to “real food publication.”