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 walks through the practical setup, from picking a plugin to configuring the details that actually affect your rankings.
Why a recipe card plugin matters
Without a recipe card plugin, a food blog runs into a handful of predictable problems. Recipes appear as plain text, which is genuinely hard to scan while you’re mid-recipe with flour on your hands. There’s no Recipe schema, which means no rich snippets in Google. There’s no “jump to recipe” button, which leaves readers annoyed and scrolling. There’s no print button, which is inconvenient for anyone cooking from a screen. Nutrition info stays unstructured, and Pinterest Rich Pins won’t show recipe details at all.
With a plugin installed and configured properly, you get all of the above solved at once. The recipe becomes a structured object that Google, Pinterest, and readers can all understand and act on.
WP Recipe Maker
WP Recipe Maker is the most popular recipe plugin on WordPress, and for good reason: it pairs a solid free core with a deep premium feature set.
Pricing
- Free: basic recipe card and schema output.
- Premium: from $49/year for a single site.
- Pro: from $99/year for a single site.
- Elite: from $149/year for a single site.
Multi-site licenses cost more but bring the per-site price down considerably, so check WP Recipe Maker’s official pricing page before you commit, since these numbers shift periodically.
Strengths
- The most features of any recipe plugin on the market.
- A strong, well-maintained schema implementation.
- Recipe import tools from other plugins, which matters if you’re switching.
- Multiple recipe card templates to choose from.
- A nutrition calculator on premium tiers.
- Built-in recipe analytics.
Weaknesses
- The interface is heavy, with a lot of settings to work through.
- Some genuinely useful features are locked behind the higher tiers.
Tasty Recipes
Tasty Recipes is made by WP Tasty and is a paid-only plugin, but it’s built specifically around ease of use.
Pricing
- Basic: from $49/year for a single site.
- Plus: from $99/year for three sites.
WP Tasty runs frequent introductory discounts, so confirm current rates on the official Tasty Recipes pricing page rather than relying on numbers you saw elsewhere.
Strengths
- The cleanest user interface of the three main options.
- Beautiful default styling that needs little customization.
- A strong “jump to recipe” feature out of the box.
- Solid schema markup.
- Easy to use even if you’re not particularly technical.
Weaknesses
- Fewer advanced features than WP Recipe Maker.
- No free tier to try before you buy.
Create by Mediavine
Create is made by Mediavine, the ad network, and it’s free for every user, whether or not you actually run Mediavine ads.
Strengths
- Completely free to use.
- Performance-optimized, since Mediavine has a direct interest in fast-loading pages for ad viewability.
- A genuinely decent feature set for a free plugin.
- Schema built in from the start.
Weaknesses
- Fewer features than the paid options.
- Some defaults and integrations are built with Mediavine publishers specifically in mind.
Which to choose
- Just starting out: Create by Mediavine (free) or the WP Recipe Maker free tier.
- Want the cleanest UX: Tasty Recipes.
- Want maximum features: WP Recipe Maker Premium or Pro.
- Already running Mediavine ads: Create, since it’s already optimized for that setup.
Schema configuration
Recipe schema is the structured-data format Google needs in order to show your recipe as a rich result. All three plugins generate it, but it’s worth verifying every field is filled in rather than assuming the defaults cover you. Check for:
- Recipe name.
- Image (large, high-quality).
- Description.
- Prep time, cook time, and total time.
- Yield or servings.
- Ingredients as a structured list.
- Instructions as structured steps.
- Nutrition info (optional, but genuinely helpful).
- Author.
- Date published.
- Category, such as Dinner.
- Cuisine, such as Italian.
- Recipe-specific keywords.
- Aggregate rating, if you have reviews to show.
Test every recipe template with Google’s Rich Results Test before you consider the setup finished. For the full list of required and recommended fields, Google’s own Recipe structured data documentation is worth reading once, even if the plugin handles most of it for you.
Jump-to-recipe button
This is a critical UX feature. It lets readers skip past your intro and personal story straight to the recipe itself, which matters more than most bloggers want to admit.
All three plugins offer this feature. Place it at the top of the post, and consider adding a second button mid-post for longer entries. On very long posts, a sticky or floating button keeps it within reach the whole time a reader is scrolling.
Readers who can’t quickly reach the recipe simply leave the page. Make the button impossible to miss.
Print button
A print-friendly recipe button strips out ads and unrelated content, then formats the recipe cleanly for paper. All three plugins offer this functionality, and there’s little reason not to enable it.
Nutrition information
Displaying nutrition per serving has become close to an expectation for readers. Plugins generally offer a few ways to get there:
- Manual entry, where you fill in the values yourself.
- Automatic calculation, a premium feature that calculates nutrition from your ingredient list via an API.
- External services, such as Nutritionix or Edamam, accessed through the plugin.
It’s worth the setup time because health-conscious readers expect it, it adds useful fields to your schema that Google may surface directly, and it helps you rank for searches like “low-carb dinner” that depend on nutrition data.
Ratings and reviews
Recipe ratings and reviews matter for a few overlapping reasons. They show as star ratings in Google search results, which is a genuinely powerful click-through booster. They act as a trust signal for readers deciding whether to commit to a recipe. And they function as an engagement signal that keeps people coming back to leave feedback.
Enable the rating feature and encourage commenters to rate the recipes they try.
Google has tightened its review schema policies in recent years, so make sure you only display reviews you actually received. Follow the general structured data guidelines on this, since fabricated or incentivized reviews can get your schema disabled.
Recipe categorization
Recipes need a proper taxonomy to be genuinely browsable. That typically means course (Breakfast, Dinner, Dessert), cuisine (Italian, Mexican, and so on), diet (Vegan, Keto, Gluten-Free), cooking method (Slow Cooker, Air Fryer, Grill), and main ingredient (Chicken, Pasta, etc).
Most plugins create custom taxonomies for these categories automatically. Configure them properly so readers can browse recipes by category rather than relying entirely on search.
Recipe templates
Most plugins offer several visual templates to choose from. Pick one that fits your site’s design and stick with it, since consistency across the blog matters more than novelty on any individual post. If you’re running Aurora, the theme’s clean typography and flexible layout options pair well with recipe cards, since the theme doesn’t fight the plugin’s own styling the way heavier, busier themes sometimes do.
Always test the final result on mobile, since that’s where most readers will actually see your recipes.
Featured image best practices for recipes
- Use a bright, well-lit photo of the finished dish.
- An overhead shot or a 45-degree angle tends to work best.
- Include a hint of scale, like a utensil or a garnish, so the dish reads as real food rather than a stock photo.
- Square or vertical crops perform best on Pinterest.
- Store multiple aspect ratios: a hero shot (1200×800), a Pinterest-optimized version (1000×1500), and a square crop (1000×1000).
Recipe-specific SEO
- Make sure the recipe name includes the actual search term, since people search “chicken pot pie recipe,” not just “chicken pot pie.”
- Use a title format like “Recipe Name | Blog Name” or “Easy [Recipe Name] Recipe.”
- Write a meta description that includes prep time, key ingredients, and the occasion the recipe suits.
- Add an FAQ section covering common questions, like substitutions, storage, and reheating.
- Link internally to related recipes wherever it makes sense.
If you want a deeper walkthrough of the SEO side beyond recipes specifically, our guide to setting up Yoast or Rank Math correctly covers the settings that affect every post type, recipes included.
The “story” before the recipe
Food bloggers get mocked constantly for long pre-recipe stories, but the reality is more nuanced than the jokes suggest. Pre-recipe content is genuinely necessary for SEO, since Google wants context around a recipe, not just a bare ingredient list. Tips and an FAQ section placed before the recipe box tend to help rankings. That content also provides real value beyond the recipe itself, covering substitutions, technique tips, and why your particular version works.
The catch is that you still need a clear jump-to-recipe button so readers in a hurry can skip straight past all of it. The balance is real, useful content paired with an easy bypass for anyone who just wants the ingredients.
Migrating recipes between plugins
Switching recipe plugins later is genuinely painful, since recipes stored in one plugin’s format don’t always transfer cleanly to another.
WP Recipe Maker has the strongest import features of the three. Tasty Recipes and Create both have more limited import options by comparison.
Pick carefully the first time, because migrating 200 recipes by hand is a real cost in time you probably don’t want to pay.
Performance impact
Recipe plugins do add some load to your pages, but there are a few reliable ways to keep that in check. Disable any features you don’t actually use, run a caching plugin to cache recipe pages, and optimize your recipe images aggressively rather than uploading them straight from the camera. Our guide to setting up WordPress caching walks through the specifics if you haven’t configured this yet.
Recipe video integration
If you make recipe videos, most plugins let you embed the video at the top of the recipe card, add VideoObject schema linked to the recipe, and display custom thumbnails instead of relying on the platform’s default.
Host the video on YouTube or Vimeo and embed it through the plugin rather than self-hosting, both for bandwidth reasons and because platform hosting handles adaptive streaming for you. If you want the full picture on embedding video without hurting page speed, see our post on adding video to a WordPress blog without slowing it down.
Getting the recipe card to actually match your site
A recipe card plugin generates its own styling by default, and that default rarely matches your blog’s typography and color palette out of the box. Most plugins let you override fonts, colors, and spacing to align with your theme, and it’s worth spending the time to do this properly rather than leaving a recipe card that visually clashes with the rest of the post. This is where a theme with clean, predictable typography and layout, which is a big part of what Aurora was built for, makes the styling work go faster since you’re not fighting inconsistent defaults elsewhere on the page.
From casual hobby to real food publication
A recipe card plugin is non-negotiable for food blogs at this point. WP Recipe Maker offers the most features, Tasty Recipes offers the cleanest experience, and Create by Mediavine is free and solid enough to start with. Configure schema completely, enable jump-to-recipe and print buttons, add nutrition info, and turn on ratings. Pick one plugin and commit to it, since migration later is genuinely painful. The recipe card is what transforms a recipe blog from a casual hobby into something that reads as a real food publication.
