Recipe schema shows the wrong ingredients or servings
Trace recipe markup mismatches to the card, serving multiplier, print view, or cached data. Verify the default recipe that a new reader actually receives.
By Crawlito · 6 min read
In short
- A recipe's visible ingredients, instructions, yield, and structured fields should describe the same preparation.
- A serving multiplier can change the screen while leaving the initial recipe data at its default quantity.
- Inspect every Recipe entity because a theme and recipe plugin can publish competing versions.
On this page
- Establish the default recipe before testing controls
- Compare all Recipe entities in the public page
- Trace the multiplier and unit conversion separately
- Repair the publishing source and its other views
- Validate the default and repeatable interactions
- Check one fractional quantity through a round trip
- Frequently asked questions
- Check the recipe page
If a recipe's structured data shows different ingredients or servings from the page, compare the default recipe card with every Recipe entity in the public response. Test the serving multiplier and print view separately. Repair the source record or component that emits the inconsistent values, then verify the recipe as a new reader with no saved preferences. Google’s Recipe structured data guidance
Establish the default recipe before testing controls
Choose one affected recipe and write down its default yield, ingredient quantities, instruction sequence, preparation time, and any nutrition basis the publisher actually provides. Get those details from the editor's maintained recipe record. A browser with a remembered serving multiplier can show a different quantity from the publication's default and make a healthy base recipe look inconsistent.
Open the page in a clean session. Record the initial setting of the serving control and the quantities shown before interacting. Then change the multiplier and observe which fields change. The ingredient list might double while the instruction text still contains a fixed quantity. A print view can use another state again. Those differences affect readers directly, regardless of how a search engine presents the page.
Use a clearly marked test recipe or copy when exercising unusual values. The diagnostic task is to trace publishing fields, so you do not need to invent new cooking advice. Keep the author's tested procedure and quantities intact while inspecting how they move through the template. Ask the recipe owner to resolve any substantive contradiction in the instructions.
Compare all Recipe entities in the public page
Inspect the initial HTML and the rendered document for JSON-LD. Search graph arrays as well as standalone blocks. A theme may create generic recipe data from article fields while a specialist plugin generates a more complete card. An old plugin can also leave markup in an embedded fragment after migration.
Match each entity to the visible recipe by its name, URL, and ingredient list. A related-recipe carousel can legitimately mention other recipes, so a different name in a separate card requires context. Concentrate on the entity that claims to describe the current page. The JSON-LD troubleshooting guide helps identify duplication and malformed output.
| Field | Public evidence to compare |
|---|---|
| recipeIngredient | Default ingredient list, including quantities and units |
| recipeInstructions | The actual ordered procedure and step text |
| recipeYield | The stated number of servings or items |
| prepTime and cookTime | The editor's definitions and visible timings |
| nutrition | The stated basis and supporting calculation |
| image | A public image of the described recipe |
Keep the fields connected. A value of eight under servings with nutrition calculated for one quarter of the recipe can be syntactically valid and factually inconsistent. Google's documentation includes requirements relating nutrition information to yield. Use the current field definitions and the author's verified data rather than filling missing values with estimates.
Trace the multiplier and unit conversion separately
A serving control and a measurement-system control perform different transformations. Doubling a recipe changes quantity. Switching between grams and ounces changes representation. If both controls exist, test them independently and in combination. A state update that multiplies an already converted value can accumulate rounding or apply the multiplier twice.
Use the default, a larger yield, and a return to default. Verify that returning to the original setting restores the exact intended quantities. Then reload the page with any public URL state used by the widget and compare the initial response with the rendered result. If the controls are purely interactive, document what the default public recipe represents.
The instruction text deserves its own pass. An ingredient quantity embedded in a sentence may not use the same structured field as the visible list. Ask whether the component can render that sentence from the same data or whether the editor needs wording that stays accurate across supported servings. Keep the procedure readable; a complicated calculation exposed inside an instruction can create more confusion.
Read how initial and rendered HTML differ when the recipe card looks correct only after the widget loads. A crawler that reads the initial response needs an accurate base recipe even if a person can adjust it later.
Repair the publishing source and its other views
If the editor's record is wrong, correct that record and regenerate the dependent views. If the record is right but the structured output uses old values, identify the serializer or cache that owns the stale copy. Avoid editing generated JSON by hand when the next save will recreate it from the same incorrect source.
Check the print page, accelerated or alternate version if present, mobile template, and any syndicated copy the publisher controls. A migration can update the main card while leaving a print endpoint attached to an older recipe ID. Match the underlying identifier as well as the human title. Two recipes with similar names may have different yields and tested procedures.
Verify image identity and accessibility. A schema block referencing a generic site logo or a different finished dish misdescribes the recipe even when its ingredient fields are accurate. Fetch the selected image anonymously and inspect what it depicts. The image alt text guide explains how surrounding labels help readers understand an image.
Validate the default and repeatable interactions
Run the public URL through Google's supported rich-result testing tool and inspect the recognized recipe fields. Fix critical syntax or property errors, then compare the accepted values with the visible card. A tool can validate a number without knowing whether it matches the author's tested recipe.
Create a small acceptance matrix with default, multiplied, converted, printed, and reloaded states. Include one unaffected recipe using the same template and one recipe with an unusual yield such as a number of items rather than servings. This catches assumptions embedded in the component. If nutrition is omitted for a recipe, verify the template leaves it omitted instead of copying another page's values.
Retain a short before-and-after record with the recipe ID, corrected field, public URL, and observed default. Search presentation can update later, but the published page and its supported views should now agree. When an editor reports the issue again, that record helps determine whether a new content edit, plugin release, or cached representation reintroduced it.
Check one fractional quantity through a round trip
Use a test recipe containing a fractional quantity and change the serving control upward, downward, and back to its default. Compare the final displayed quantity with the original editor value. A component that repeatedly rounds its current display can lose precision after several interactions.
Check the print view after the same sequence. If it uses the original record while the screen uses the altered state, document the intended behavior and make the presentation clear to the reader.
Frequently asked questions
Should structured data describe the doubled recipe after a user clicks?
Start with an accurate default recipe and test the widget's documented behavior. Ensure every published representation has an understandable yield and consistent quantities.
Can I estimate nutrition to fill a missing field?
Use verified information with a clear serving basis. Missing evidence needs editorial work, and an invented estimate should not become a published fact.
Does valid recipe markup guarantee a recipe result?
Google decides which eligible pages receive particular search features. Validation confirms supported structure and helps identify errors in what you publish.
Check the recipe page
Use the free page check on the public recipe URL. Compare its initial content and structured fields with the default card before testing the interactive controls.
Filed under Structure and schema. Topics: structured-data, google, recipes, troubleshooting