XooCode(){

HowToItem

HowToItem is a ListItem subtype for an item used in a how-to or recipe. Property: requiredQuantity (Number / QuantitativeValue / Text). Parents HowToSupply and HowToTool.

Full example of schema.org/HowToItem json-ld markup

The markup is verified as valid with Rich Results Test from Google.

schema.org/HowToItem
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HowToItem",
  "name": "Rye flour",
  "requiredQuantity": { "@type": "QuantitativeValue", "value": 500, "unitCode": "GRM" }
}
</script>

Minimal valid version

The smallest markup that still produces a valid HowToItem entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/HowToItem (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HowToItem",
  "name": "Flour",
  "requiredQuantity": "500 g"
}
</script>

Google rich results this unlocks

HowToItem is a structural type. It does not produce a rich result on its own.

Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). HowToItem becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

Common HowToItem mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

  1. 01

    HowToItem where HowToSupply / HowToTool fits

    Wrong
    HowToItem for a kitchen knife
    Right
    HowToTool for tools, HowToSupply for consumables

    Subtypes exist to distinguish consumables from tools; use them for clarity.

Also mentioned in 2 other examples

HowToItem also appears in HowToSupply, and HowToTool. See the full HowToItem schema page for every reference.

About the example data

Flour measurement in the Xoo family smørrebrød recipe.

Comments

Loading comments...

Leave a comment