The complaint, and why it is the wrong one
The standard reaction to an online recipe is that the story before it is unnecessary. That reaction is reasonable and slightly misdirected, because the story is not there for the reader who already knows what they want. It is there because of how the page is found and paid for.
Understanding the mechanism is more useful than the complaint, because it also tells you how to get past it, which is generally a jump link the page itself provides.
This article describes a set of incentives. It names no site, criticises no publisher and makes no claim about anyone's traffic or revenue, since this publication does not report figures it cannot verify.
Structured data, the invisible half of the page
Search engines identify recipes through structured data: machine-readable markup embedded in the page that declares the ingredients, the method steps, the times, the yield and other defined fields.
Once a page carries valid recipe markup, it becomes eligible to appear in richer result formats, which occupy more space and attract more attention than a plain link. That eligibility is worth a great deal, and it is granted for correctly structured data rather than for good cooking.
This produces the first structural consequence: every recipe page is written to fill a defined set of fields. The visible layout mirrors a schema, which is why recipe pages across entirely unconnected sites have the same anatomy. They are all filling in the same form.
| Element | Serves the reader | Serves distribution or revenue |
|---|---|---|
| Structured recipe markup | Indirectly, by making the page findable | Yes, it is the eligibility condition for rich results |
| Narrative preamble | Sometimes, as food writing | Yes, length, ad slots and query coverage |
| Jump to recipe link | Yes, directly | It reduces the effect of the preamble |
| Ingredients block | Yes | Yes, it is a required structured field |
| Step by step method | Yes | Yes, it is a required structured field |
| Question and answer block | Sometimes | Yes, query coverage and additional result formats |
| Related recipes | Sometimes | Yes, internal linking and time on site |
Structure set out by this newsroom from the published rules named in the sources below. It is not a survey, a measurement or a market study.
The preamble
The narrative section before the recipe does several jobs at once.
It gives the page substantive text, which historically has helped pages be treated as more than a bare list of ingredients that also appears on thousands of other pages.
It creates space for advertising. A page monetised by display advertising earns in proportion to the number of ad slots viewed, and slots require length.
It provides material for a search engine to match against a wide range of queries, since a recipe page competes for many different phrasings.
And it establishes a personal voice, which is a genuine editorial value in food writing and not merely a device. The unfortunate result is that a real tradition of food writing and a monetisation requirement point in the same direction, which makes the two impossible to distinguish from the outside.
The FAQ at the bottom
The question and answer block at the foot of a recipe page is doing the same job as the preamble, at the other end, with a different mechanism.
Questions capture the long tail of queries a reader might type. Structured markup for question and answer content can produce additional result formats. And the block adds length without interrupting the recipe itself, which is a better solution than a longer preamble.
It is worth noting that this publication uses the same device, for the same reason, on every article. That is not a contradiction to be hidden. It is an illustration of how strong the incentive is, and it is disclosed here rather than left for a reader to notice.
Why every page looks the same
The convergence of recipe pages onto one format is a textbook case of an environment selecting a form.
Every publisher faces the same distribution channel, the same structured data specification, the same advertising economics and the same competitors. Pages that deviate are found less often and earn less, so deviation does not persist. What survives is a format optimised for the channel rather than for the cook.
The same process explains the jump to recipe button, which exists because publishers know the preamble is unwanted by a large share of readers and have found a way to serve both the reader and the channel at once. That button is the most user-centred element on most recipe pages, and it is a direct concession.
What this does and does not tell you about the recipe
Nothing about page structure indicates whether a recipe works. Format is a distribution artefact and carries no information about testing, accuracy or quality.
Some signals in the text are more informative than the layout. Specific quantities and temperatures rather than approximations, stated tin or pan sizes, indications of what the mixture should look like at each stage, and stated yields all suggest a recipe that has been made more than once. Their absence suggests less.
Where a recipe touches food safety, particularly cooking temperatures and the handling of certain foods, the Food Standards Agency is the source rather than any recipe page. Where it touches diet or health, that is a matter for the NHS or a registered dietitian.
What changes when answers are generated
The economics described above depend on a reader arriving at a page. Where an assistant or a search interface answers the question directly, the visit does not happen and the advertising does not load.
That is a significant shift for anyone publishing recipes, and it is likely to change the format again, because the format was always a response to the channel. What replaces it will be shaped by whatever the new channel rewards.
It is too early to describe the outcome, and this publication does not speculate about numbers. What can be said is that the structure of a recipe page has never been about cooking, so there is no reason to expect the next structure to be either.
Where this stops
This article describes publishing incentives. It names no publisher and no platform, quotes no traffic or revenue figures, and makes no claim about any site. It gives no cooking, food safety or dietary advice.
Elsewhere on Feedworthy. How to read a UK food label, and the order to read it in. Allergen information on UK packaging: what the law requires. Green claims on food: the code, the Act and what changed.