Food Blog SEO: 2026 Recipe Ranking Guide
Every recipe page serves two readers at the same time, and one of them is a cook standing in a kitchen with flour on their hands, trying to find the next instruction before the butter burns. The other is Google, trying to understand what the dish is, how long it takes and whether the page deserves a richer result. Good recipe pages serve both readers without making either one wait.
This guide is for anyone who runs a food blog or a recipe site, plus the developers who help them, in the United States, Europe and South Korea. It covers what Google requires in Recipe markup and where that markup goes wrong, then moves to ratings, photos, video, the story above the recipe and ads. It ends with cooks in different countries and what to watch in Search Console. Every rule here comes from Google's own pages or schema.org, read on October 15, 2026, and every opinion is labeled as one.
Why do recipe pages win or lose in Google Search?
In our view, recipe pages win when Google can match the Recipe markup to a real dish on the page. Google's Recipe guide says ratings, times and nutrition information help it understand a recipe, which can then show in Google Search and Google Images. Pages that break the rules can lose the rich result but still appear as plain results.
Google's Recipe guide says to use the markup "for content about preparing a particular dish", and the general structured data guidelines add a line that every food blog should read twice. They state that "Google does not guarantee that your structured data will show up in search results".
Our take: rich results are earned by matching the markup to what the cook sees on the page, not by filling every field. The work of recipe SEO is accurate markup, original photos and genuine ratings, and notes that only someone who cooked the dish could write. Our guide to schema markup and JSON-LD covers the basics.
Which Recipe structured data properties does Google require?
Google's Recipe guide lists only two required properties, image and name, and everything else, from ingredients and steps to ratings and video, is recommended. The general guidelines add that items missing a required property are not eligible for rich results. The recommended fields add useful information, but only when they match what the page shows to the cook.
Google's guide also sets rules for photos, whose URLs must be crawlable and indexable, and each photo must show the dish that is marked up. For best results, the guide suggests several high resolution photos of at least 50,000 pixels, counting width times height, in the 16x9, 4x3 and 1x1 ratios. It also notes that the image property in Recipe markup "has no impact on the image chosen for a text result image". The middle column follows Google's Recipe guide, and the last column is our own view.
| Property | What Google says | Our view |
|---|---|---|
| image | Required, a photo of the finished dish | Use your own photos in all three ratios |
| name | Required, the name of the dish | Use the name a cook would search for |
| recipeIngredient | Recommended, only the text needed to make it | Match the list on the page word for word |
| recipeInstructions | Recommended, with HowToStep as the preferred form | One step per action, with no step numbers |
| aggregateRating | Recommended, following the review snippet rules | Only real ratings from real readers |
| video | Recommended, showing the steps to make the dish | Add one only when it shows the cooking |
The general guidelines say the markup must be a true picture of the page content. In our view, a short, accurate block beats a long block that disagrees with the page.
How should you mark up ingredients and steps?
Google's Recipe guide says to mark up only the ingredient text a cook needs, with no definitions. It prefers one HowToStep per step over one block of text, and words like "Directions" and "Watch the video" stay out of the step text. Use sections only when a dish has parts, and give each separate method its own Recipe object.
The guide says "We recommend using HowToStep" for the steps, and for times it asks for totalTime or for cookTime and prepTime together, written in ISO 8601 format. Most recipes have no sections, and Google's own example of a dish that can use HowToSection is a pizza, with steps for the crust, the toppings and the baking. Google's guide adds that several ways to make one apple pie are several Recipe objects, not sections of one.
Can you trust what your recipe card plugin outputs?
A recipe card plugin is a convenience, not a guarantee. Google's Recipe guide says a plugin may be easier when you use a content management system. In our view, a plugin only writes what you type and what its settings allow, and theme changes, updates and missing fields can all break the output.
Google's Recipe guide warns that spammy markup may not be a syntax issue, and then the Rich Results Test will not catch it. A structured data manual action makes Google ignore the markup, though the page can still appear in Search. In our view, run the Rich Results Test on a few recipe pages after every theme or plugin update, and check these points before you trust a recipe card.
- The markup uses JSON-LD, the format Google recommends, or another supported format
- No robots.txt rule or noindex tag blocks the recipe pages from Googlebot
- Every ingredient and step in the Recipe markup also appears on the page
- The dish name in the markup matches the title the cook sees
- Ratings come only from real readers, with nothing added by hand
- The page is about a dish, not a craft
The general guidelines flag "A woodworking site labeling instructions as recipes." as irrelevant markup. When errors do show up, our guide to debugging structured data errors walks through the fixes.
Are star ratings worth adding to recipes?
Star ratings are worth adding only when real readers leave them. The general guidelines say "users prefer recipes with actual user reviews and genuine star ratings" and warn that ratings not left by real users may lead to a manual action. If your page shows several reviews, the markup should include all of them, not a chosen few.
Google's Recipe guide adds that if the Recipe markup holds a single review, the reviewer must be a real person or organization, not a sales line. A structured data manual action costs the page its rich result eligibility, but the general guidelines note that it does not change how the page ranks in web search. In our view, let visitors rate the dish and never seed the first ratings yourself.
How do food photos help in Search and Google Images?
Good food photography helps Google and the cook in the same way. Google's image SEO guide says sharp, high quality photos draw users more than blurry ones. It also warns that images are often the largest part of page size. Your own clear photos, kept light, serve both needs.
Google's image guide says Google reads captions and nearby text to understand a photo, and short, descriptive file names give it light clues. It calls alt text the most important image attribute, one that helps screen reader users and should not be stuffed with keywords. Our guide to writing alt text covers the wording, and our guide to image optimization covers file size, with WebP and AVIF both on Google's supported list. For example, a sourdough baker in Austin, Texas who shoots step photos on a phone should keep the shaping and crumb shots, because they show the work behind the loaf. The same photos can also earn attention in visual search, and our Pinterest guide shows how Recipe markup on the page can feed Recipe Rich Pins.
Should every recipe come with a video?
No, not every recipe needs one, and Google's Recipe guide lists video as a recommended property for the whole dish while also allowing a video or clip for a single step. In our view, add a video only when it shows the dish being made, because a clip that hides the method adds weight without helping anyone.
A short clip of the difficult part, such as folding dough or checking a sauce, can be marked up for that one step. Keep the step text clean, because Google's guide says phrases like "Watch the video" belong outside the step markup. Our guide to video SEO on YouTube and Google covers video markup in more depth.
How long should the story above the recipe be?
The story should be as long as it is useful, and no longer. Google's helpful content guide asks whether you write to a word count because Google prefers one, and the answer is "No, we don't." Keep the notes that show you cooked the dish, such as what you changed and what failed, and cut the rest.
The same guide asks if content shows "first-hand expertise", such as from having used a product or visited a place, and our guide to E-E-A-T and helpful content goes deeper. The helpful content guide also asks for bylines where readers expect them, with links to more about the writer, and it calls made-up names and fake headshots a form of deception. Google's Recipe guide lists author as the person or organization that wrote the recipe, and our guide to author pages and bylines shows how to set them up.
Do ads and pop-ups on recipe pages hurt you?
They can, when they get in the way of the recipe. Google's page experience guide asks whether a page avoids an excessive amount of ads that distract from the main content, and whether it avoids intrusive interstitials. In our view, the cook must find the ingredients without fighting the page.
The same guide states that "Core Web Vitals are used by our ranking systems." It adds that other parts of page experience do not directly help ranking but can make a site more satisfying to use. Our guide to Core Web Vitals shows how to reserve space for ad slots that would push the steps around, and our lazy loading guide explains which food blog photos should load late.
How should a food blog plan keywords and seasons?
Plan one strong page per dish and let the season decide when you refresh it. Google's Recipe guide treats keywords as extra terms such as a season, a holiday or words like quick and easy. Those terms should not repeat the recipeCategory, which is the meal or course, or the recipeCuisine, which is the region.
A summer salad can carry summer in its keywords, and a pumpkin bread can carry Halloween. In our view, five near copies of one dish hurt recipe SEO more than they help, and the better move is to keep the version you would cook again. Our keyword research guide helps you find the names cooks search for, our seasonal SEO guide covers timing, and our guide to keyword cannibalization shows how to merge pages that compete.
How do you write recipes for cooks in the US, Europe and Korea?
Write for the cook in front of you and give both kinds of measurements. In our view, US readers expect cups and ounces while most European readers expect grams, and a recipe that gives both serves cooks in the US and in Europe. Translate each page with care, and treat each language version as its own page.
Google's image guide says that if you localize images, you should translate the file names too. A pasta blog in Bologna, Italy, for example, might publish in Italian and English. It should name its photos in both languages and link the two versions with hreflang tags, as our hreflang guide explains. For example, a home cook in Busan, South Korea writing about kimchi stew in Korean should check Naver too, and in our view Naver keeps its own index, which our Naver SEO guide covers. Schema.org also offers suitableForDiet for diet labels, but Google's Recipe guide does not list it.
What should you watch in Search Console after you add Recipe markup?
Watch the rich result status report and the Performance report. Google's Recipe guide says to check Search Console after you first add markup and after any template or code change. A rise in invalid items can point to a broken template, while a fall in valid items with no rise in invalid ones can mean the markup has left the page.
The same guide says the Performance report shows how often a page appears as a rich result, how often people click and the average position. It also says it may take several days after publishing for Google to find and crawl a page. After you fix invalid items, the guide says to inspect a live URL to check if the issue persists. When valid items fall, it points to the URL Inspection tool to find the cause.
None of this replaces the cook in the kitchen with flour on their hands. Markup helps Google read the page, but the cook decides whether your food blog was worth the visit. Give that cook clear instructions, honest photography and real ratings, and let the markup describe exactly that.
Frequently asked questions about food blog SEO
Is Google dropping recipe rich results?
Not as of October 15, 2026. Google's June 12, 2025 post on simplifying the results page named seven structured data features it was phasing out, namely Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement and Vehicle Listing. Recipe was not on that list, and the post said the change would not affect ranking. In our view, no one can promise the future, and the safe plan is a recipe page that also works as a plain result.
Should I use JSON-LD or Microdata for recipes?
Google's general structured data guidelines list three supported formats, JSON-LD, Microdata and RDFa, and they mark JSON-LD as the recommended one. All three can make a page eligible. In our view, the choice comes down to upkeep, and JSON-LD is easier to keep in step with the page, because it sits in one block that a recipe card or a developer can update. Whatever you pick, check the output after each update and make sure it matches what the cook sees.
Can a roundup post of several recipes use Recipe markup?
A roundup post on a food blog that only links to your recipe pages is a list, not a recipe. Google's Recipe guide says a carousel or grid needs ItemList markup plus a summary page that lists all the recipes in the collection. For a host carousel, each list item needs a position and its own unique canonical URL. In our view, put the full Recipe markup on each recipe page and use the roundup to point to them.
Should I add calories to my recipes?
Only add calories if you can stand behind the number. Google's Recipe guide lists nutrition calories as a recommended property, and if you give calories per serving, recipeYield must state the number of servings. In our view, a calorie figure that you guessed does more harm than leaving the field out, because readers may plan meals around it. If you do add it, show the same figure on the page that the markup carries.
Can I mark up a cocktail or a smoothie as a recipe?
Google's Recipe guide says to use the markup "for content about preparing a particular dish". It gives "facial scrub" and "party ideas" as names that do not count as a dish. In our view, a cocktail or a smoothie you make from ingredients with clear steps fits that idea. Each has a name, a list of ingredients and a method, which is what the markup describes. Keep the markup honest about what the page is.
Why did the stars vanish from my recipe results?
Several things can cause it, and the general structured data guidelines say Google tailors results by search history, location and device type, and sometimes a plain text result is judged best. Markup that no longer matches the page, or ratings that did not come from real users, can also cost you. Check the Manual Actions report in Search Console first. If you find a manual action, our guide to manual action recovery walks through the next steps.
Does a jump-to-recipe button matter for recipe SEO?
Google's guides cited here do not mention a jump button, and this answer is opinion. In our view, the button helps the cook more than it helps any crawler, because a reader who wants only the ingredients can skip the story while a reader who wants the notes can stay. The catch is that a button is no excuse for a page that hides the recipe under ads and pop-ups. Fix the page first, then add the shortcut.
Is a meta description worth writing for recipe pages?
In our view, yes, at least for your most important recipes, because Google's image guide says snippets draw on several sources, including the meta tags of a page. A clear summary of the dish, its time and what makes your version different gives Google good material. Keep it true to the page and avoid stuffing it with keywords. Our meta description guide explains when Google uses the tag and when it picks page text instead. For a large food blog, start with the recipe pages that already get search traffic.