What lands in the card
WPRM stores a recipe as its own post type with dozens of fields. Copying an AI answer into the editor only fills the parts you remember. RecipeFox maps every generated value to the field WPRM expects.
| WPRM field | What RecipeFox sends |
|---|---|
| Ingredients | Amount, unit, name and notes split per line, in groups when the recipe has a sauce or topping |
| Instructions | Grouped steps written as actions, each step referencing only ingredients that exist in the list |
| Times | Prep, cook, rest and total, checked so the total actually adds up |
| Servings and yield | Number plus a unit such as portions, cookies or a 9-inch tart |
| Nutrition | Calculated per serving from the ingredient list, not guessed by the model |
| Course, cuisine, keywords | Matched to the terms already on your site before anything new is created |
| Image | A photoreal hero image uploaded to your media library with descriptive alt text |
How the publish step works
- Connect the site
Add your WordPress URL and an Application Password (WordPress core feature, no admin password shared).
- Install the Bridge
A small plugin that exposes one authenticated endpoint for WPRM data and SEO meta. Without it, WPRM ignores most fields sent through the normal REST API.
- Generate
Type a keyword. Claude writes the article; three images are created (hero, process, serving).
- Publish or schedule
The post, the WPRM recipe and the Yoast, Rank Math or AIOSEO title and description are created together. Scheduled posts go to WordPress as future posts.
Checks that run before a recipe is published
A recipe card that contradicts itself is the fastest way to lose a reader. The quality engine reads each generated recipe like an editor would and flags problems such as:
- 01Prep plus cook plus rest time that does not match the total time
- 02An ingredient in the list that no step ever uses, or a step that uses something not in the list
- 03Oven instructions that ask you to preheat after the dish is already prepared
- 04Storage advice that contradicts itself (3 days in one place, 5 in another)
- 05Pan sizes that cannot hold the quantity, and nutrition values outside a sane range
- 06Duplicate or too-short image alt text
When an issue is found, the recipe is repaired and checked again instead of shipped as is.
The schema WPRM outputs
Because the card is native, WPRM generates the Recipe JSON-LD itself. A shortened example of what search engines receive:
{
"@type": "Recipe",
"name": "Arakas Latheros (Greek Peas in Tomato Sauce)",
"recipeYield": ["4", "4 portions"],
"prepTime": "PT20M",
"cookTime": "PT30M",
"totalTime": "PT50M",
"recipeIngredient": ["500 g frozen peas", "2 medium potatoes, cubed", "..."],
"recipeInstructions": [{ "@type": "HowToStep", "text": "Warm the olive oil..." }],
"nutrition": { "@type": "NutritionInformation", "calories": "286 kcal" }
}Who this suits
Food bloggers who already use WPRM and want to publish more often without rebuilding cards by hand, and small publishing teams that run several recipe sites. If you prefer WP Delicious, see the WP Delicious integration. For roundups that link to your existing recipes, see recipe listicles.
Frequently asked questions
- Do I need WP Recipe Maker Premium?
- No. The free version of WP Recipe Maker is enough. Premium features such as nutrition labels display data RecipeFox already sends.
- Does RecipeFox AI overwrite my existing recipes?
- No. It only creates new posts and recipes, and it checks for an earlier copy of the same post before creating one, so a timed-out publish is not duplicated.
- Can I edit a recipe before it goes live?
- Yes. Every recipe has a preview with its schema, and you can regenerate the title, any image or the whole recipe before publishing, or publish as a draft.
- Which SEO plugins are supported?
- Yoast SEO, Rank Math and All in One SEO. The Bridge sets the SEO title, meta description and focus keyword on the post.