Every cook has hit the wall: you search for a recipe and land on nine hundred words about someone's grandmother before you reach the flour. That format came from a real belief that length and keyword density were what ranked. It has aged badly, and search has moved on faster than the format has.
What search is looking for now
Search engines have spent years getting better at recognising whether a page actually answers the query, and both Google and the AI answer layers now lean on signals of genuine experience: photos that clearly come from your own kitchen, specific detail that only someone who cooked the dish would include, a named author with a track record.
The practical translation is unromantic. Say the useful thing early, prove you cooked it, and make the page fast.
Structure for the person in the kitchen
A recipe post has two audiences at once: the person deciding whether to cook this, and the person already cooking it with sticky hands. Serve both in that order.
- A short intro. Two or three sentences on what the dish is, why this version works and what to expect. Not a memoir.
- A jump link to the recipe. Do not fight the reader who wants the ingredients now. Making them scroll increases the chance they leave, which is a worse signal than the click.
- The recipe. Ingredients by weight, clear steps, real timings, visual cues rather than only clock times.
- The useful extras after it. Substitutions, what goes wrong and why, storage and reheating, variations. This is the material that earns links and keeps people on the page, and it belongs after the recipe, not before it.
Recipe schema is not optional
Structured data tells search engines that your page is a recipe and what is in it: ingredients, times, yield, nutrition, ratings, images. It is what makes a recipe eligible for rich results, and increasingly what makes it legible to AI-generated answers.
Fill in every field you honestly can, keep it consistent with what the page actually says, and validate it with a structured data testing tool rather than assuming your plugin got it right.
Speed is a ranking factor and a courtesy
Recipe sites are notorious for being slow: enormous images, a video that autoplays, four ad units and a newsletter popup before the first paragraph. Compress images and serve modern formats, lazy-load anything below the fold, and be honest about how many scripts a page really needs.
Test on a phone on a mediocre connection, which is how most people will read it, standing in a kitchen.
Write for the query behind the search
"Chocolate chip cookies" is one query with several intents. Someone wants a reliable recipe, someone wants to know why theirs came out flat, someone wants a version without eggs. Those are separate posts, each aimed at one intent, linked to each other.
Long-tail queries are where a small site can win. Competing for "pasta" is hopeless. Answering "why is my pasta sauce watery" is achievable and brings a reader who is genuinely stuck.
What to stop doing
- The mandatory life story. Keep the personal material if it is good, and put it after the recipe.
- Keyword stuffing. Writing "easy chicken recipe" eleven times reads as spam to both readers and search engines.
- Publishing recipes you have not cooked. It shows in the missing detail, and detail is the thing that now distinguishes a page worth ranking.
- Copying a recipe and changing three words. Recipes as lists of ingredients are not copyright-protected, but the writing around them is, and duplicated method text gets treated exactly as it deserves.
The part that has not changed
A post that solves someone's problem well gets bookmarked, shared, printed and returned to. Every measurable signal search engines use is a proxy for that. Write the version you would want to find at half past six with the oven already on, and the technical work becomes maintenance rather than strategy.