recipeCuisine

recipeCuisine · Recommended

Appears in

Recipe

What is it?

recipeCuisine identifies the regional or cultural origin of a recipe. Values like "Italian," "Mexican," or "Japanese" help search engines classify recipes by cuisine type.

Why this matters for AEO

When a user asks "give me a good Italian pasta recipe," AI answer engines filter by recipeCuisine to match the cuisine request. This field is the direct signal for cuisine-based queries, which are among the most common recipe search patterns. Without it, engines must infer cuisine from ingredients or recipe names, which fails for cross-cultural dishes.

What the specs say

Schema.org:Text. The cuisine of the recipe (for example, French or Ethiopian). Source

Google: Recommended. "The region associated with your recipe." Source

How to find your value

• American — Classic US dishes, BBQ, comfort food
• Chinese — Cantonese, Sichuan, Hunan styles
• French — Classic French and bistro cooking
• Indian — Regional Indian cuisines
• Italian — Pasta, pizza, risotto, Italian baking
• Japanese — Sushi, ramen, Japanese home cooking
• Korean — Korean BBQ, stews, fermented dishes
• Mexican — Tacos, mole, Mexican baking
• Mediterranean — Broadly Mediterranean styles
• Thai — Thai curries, stir-fries, salads

Use the broadest accurate term. "Italian" is better than "Tuscan" for search visibility unless regional specificity is the point of the recipe.

Format and code

Type: Text

{
  "@type": "Recipe",
  "name": "Pad Thai",
  "recipeCuisine": "Thai"
}

For fusion dishes, use the primary cuisine or an array:

{
  "@type": "Recipe",
  "name": "Korean BBQ Tacos",
  "recipeCuisine": ["Korean", "Mexican"]
}

Webflow implementation

Static pages

Add to Page Settings > Custom Code (Before ):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Recipe",
  "name": "Banana Bread",
  "recipeCuisine": "American"
}
</script>

CMS template pages

Create a plain text CMS field called "Recipe Cuisine" (e.g., "American"). Reference it:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Recipe",
  "name": "{{wf {"path":"name","type":"PlainText"} }}",
  "recipeCuisine": "{{wf {"path":"recipe-cuisine","type":"PlainText"} }}"
}
</script>

In Schema HQ

Field mapping pulls Webflow CMS cuisine field directly to the recipeCuisine property. It supports both single text values and option fields.

Real examples

Love and Lemons (source):

{
  "recipeCuisine": "American"
}

Sally's Baking Addiction (source):

{
  "recipeCuisine": "American"
}

Related fields

• recipeCategory classifies the meal type (dessert, main course)
• recipeIngredient lists the ingredients used
• recipeInstructions details the cooking steps
• recipeYield states how much the recipe produces

FAQ

Should I use "American" or "United States" for recipeCuisine?

Use the common cuisine name: "American," "Italian," "Thai." These match what users search for and what Google expects. Avoid country codes or formal country names.

Can a recipe have multiple cuisines?

Yes. Use a JSON array for fusion or cross-cultural recipes: ["Korean", "Mexican"]. However, for most recipes, a single cuisine value is sufficient and clearer.

Is recipeCuisine required for rich results?

No. Google lists it as Recommended. It helps with filtering and categorization, especially for cuisine-specific searches and AI answer engine queries.