Skip to content
GPLWP Guides

How to create recipe cards in WordPress

Content Time About 20 minutes Updated 14 Sep 2026

CONTENT
The short answer

You can build a basic recipe card with WordPress blocks, but core WordPress does not provide recipe fields, print styling or Recipe structured data. For a food blog, a recipe plugin is the practical route because it keeps the card, schema and printable version together.

What you need

  • A WordPress site with editor access
  • The recipe title, image, ingredients and method
  • Preparation, cooking and total times
  • Nutrition and serving information, if available
The fast route

Let WpTasty Tasty Recipes Plugin do it

Structured recipe cards with nutrition fields, print views, and rich snippets for food bloggers publishing recipes.

Get WpTasty Tasty Recipes Plugin

Sources

  1. developers.google.com /search/docs/appearance/structured-data/recipe?utm_source=op…

Questions

Can I create a recipe card without a plugin?
Yes, you can create a basic visual card with WordPress Group, Heading, List, Image and Table blocks. This works for a small number of recipes, but you must handle styling, print layouts and structured data separately. If you later change the card design, you may need to edit every post manually.
Do recipe cards improve Google rankings?
Recipe cards do not guarantee higher rankings, but their structured data helps Google understand recipe details such as ingredients, times, yield and nutrition. Use accurate visible content and validate the markup. Google requires the recipe name and image for eligibility, and rich results are never guaranteed.
What should a WordPress recipe card include?
A useful recipe card includes the dish name, image, description, servings, preparation time, cooking time, total time, ingredients, instructions and notes. Add cuisine, category, ratings and nutrition when they are genuine and relevant. Do not add invented ratings or nutrition values just to fill fields.
Why does a recipe card print the whole page or show a 404 error?
The print feature normally depends on the plugin’s print URL, card markup and theme styles. A theme conflict, caching rule, changed block identifier, broken permalink or translated card label can make the wrong page print or produce a 404. Clear caches, resave permalinks, test with the default theme and check the plugin’s support notes.