Google's recipe rich result pulls directly from Recipe structured data — the ingredients list, the numbered steps, prep and cook time, yield, and an optional rating badge all come from the same JSON-LD block a crawler reads on the page. Getting the shape right matters more than filling in every optional field: a missing image or an empty ingredient list can keep the rich result from appearing at all, while a missing cuisine or keyword just means one less filter a user could have matched on.
Keep the markup honest and in sync with what's visible on the page. If the visible recipe changes — a different yield, an added step, updated nutrition — update the schema at the same time so the two never drift apart.