Skip to content
Searchpedia SEO field notes Callum Bennett Callum

Writing desk

Recipe SEO

I used to think recipe SEO was all about schema, but the biggest wins came from fixing keyword selection and page structure first.

Beginner3 min readUpdated 2026-07-27Notes by Callum Bennett

What I’d do first

  • Target long-tail queries like '15-minute sheet pan chicken' instead of broad terms like 'dinner recipes'.
  • Place the recipe card near the top of the page with a short intro, structured ingredients list, and numbered instructions.
  • Add complete recipe schema with all required fields and validate it using Google's Rich Results Test before publishing.
  • Optimise images with descriptive file names, alt text, and compression to keep load times under 2 seconds.
  • Link related recipes and category pages internally to improve crawl depth and user retention.

The path I'd take

I start with keyword research, not schema. I open a keyword tool and filter for long-tail queries with moderate search volume and low difficulty. For example, 'quick vegetarian pasta recipe' has clearer intent and a less saturated SERP than 'pasta recipe'. I then optimise the page title and meta description around that phrase. Next comes page structure. I put the recipe card as close to the top as possible, with an engaging intro of 100–150 words that uses the target keyword naturally. Ingredients go in a clear, scannable list; instructions are numbered steps. I also add a 'why this works' bullet point to keep readers engaged. Then I implement recipe schema. I include all required fields from Google's documentation: name, description, image, prepTime, cookTime, recipeIngredient, and recipeInstructions. I add aggregateRating and nutrition only if I have verified values. Decision rule: if I cannot provide accurate nutrition per serving, I skip the nutrition property to avoid validation errors. I run the Rich Results Test before publishing and fix any errors immediately. Finally, I add internal links to related recipes and category pages. I use a plugin to suggest relevant recipes contextually. For a lemon chicken post, I link to garlic chicken and lemon fish. This kept users on my site longer and increased pageviews per session by roughly 15%. You can apply the same approach to your [On Page SEO](/on-page-seo/) and [SEO Copywriting](/seo-copywriting/) across your site. I also ensure the intro hooks the reader without burying the recipe – a common mistake I made early on.

Watch-outs

Publishing without validating recipe schema is a common trap. I once pushed a recipe post with a missing image property, and Google ignored the rich result entirely. Now I always run the Rich Results Test before hitting publish. Targeting broad keywords like 'chicken recipe' wastes effort – you are competing against major publishers with thousands of backlinks. Instead, focus on specific dishes that people search for with modifiers like 'sheet pan' or '15-minute'. Skipping step-by-step instructions also hurts. Some recipe posts list only ingredients, assuming users know the process. That leads to high bounce rates and poor signals to search engines. Write out each step clearly. Mobile performance is critical. Large, uncompressed recipe images kill load speed. I compress every image to under 100 KB and serve WebP where supported. For more on this, read about [Image SEO](/image-seo/). Avoid copying text from other sites. Google's duplicate content filter can demote your page even if you change a few words. Write original descriptions and instructions. Edge case: if your recipe includes a long personal story, consider collapsing it or adding a 'jump to recipe' button. Some established food blogs rank with lengthy stories, but that is often due to domain authority. For a new site, place the recipe early. Also watch out for missing alt text. I now write alt text that describes the dish and includes the keyword naturally, such as 'Lemon grilled chicken with garlic and herbs'. Generic alt text like 'image1' does nothing for search or accessibility. See [Alt Text](/alt-text/) best practices. Finally, ignore meta descriptions at your own risk – they influence click-through rates from search results.

What I got wrong

I used to believe that more schema fields always meant better ranking. I added every property I could find: recipeCuisine, recipeCategory, recipeYield, even nutritional values I estimated poorly. Google’s Rich Results Test flagged errors, but I ignored them because I thought the extra data helped. Eventually my recipe pages stopped showing any rich results. I had to strip back to only required fields and re-submit my sitemap. Now I stick to the core properties and add optional ones only when I can verify the values. Another mistake: I copied meta descriptions directly from competitor recipes. Google detected duplicate meta descriptions and issued a manual action for thin content. I rewrote unique descriptions that summarised each recipe with a compelling angle. Learn from my error and craft original [Meta Description](/meta-description/) text. I also used generic alt text like 'recipe image' or skipped it entirely. After fixing alt text on each image with descriptive phrases, I noticed a steady trickle of traffic from Google Images. That was a lesson in the importance of [Internal Links SEO](/internal-links-seo/) too – I used to have hundreds of recipes with no connections between them. Crawlers had trouble finding all my pages. I added contextual links and saw indexation improve. Finally, I once believed that long, personal intros before the recipe were essential for Google. I moved the recipe card to the top of the page and placed the story at the bottom. Time on page increased because users found what they wanted immediately. Admit your mistakes early and adjust.

Next step

Quick answers

What is the most important recipe schema field for ranking?

No single field guarantees ranking, but the recipe name and image fields are crucial because they appear in the rich snippet. Without them, Google may not display the recipe card. Focus on getting the required fields correct before adding optional ones.

How long should a recipe page be for SEO?

There is no ideal word count, but aim for at least 500 words including ingredients and instructions. Longer pages that thoroughly explain steps and include tips tend to perform better, but do not add fluff. Keep the recipe itself concise and scannable.

Can I publish the same recipe on multiple pages without duplicate content issues?

You can, but avoid duplicate content by using canonical tags to point search engines to the preferred URL. Alternatively, use a single page with a recipe card plugin that displays all versions. Index only one version to avoid confusion.

Sources

Primary documentation is linked directly. Anything commercial is marked nofollow.

Notes from Callum Bennett.