HowTo Schema

What is HowTo Schema?

HowTo¹ is the schema.org JSON-LD type for marking up step-by-step instructional content. Each HowTo entity contains a step array of HowToStep objects, each with a name, text, and optional image or url. The structure mirrors how a reader actually executes the procedure: discrete numbered actions, each independently parseable.

Minimum viable HowTo JSON-LD

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to validate JSON-LD before deploy",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Paste into the validator",
      "text": "Copy the rendered JSON-LD output and paste into Google's Rich Results Tester."
    },
    {
      "@type": "HowToStep",
      "name": "Check both validators",
      "text": "Repeat the paste in Schema.org's validator — they flag different issues."
    }
  ]
}

Status in 2026

Demoted in SERPs, still useful for AI. Google restricted HowTo rich results from mobile SERPs on August 8, 2023 (limited to desktop only) and fully deprecated them on desktop around September 13–14, 2023² — the same wave that restricted FAQ rich snippets. The schema type is still valid and still parsed by AI engines, but no longer drives in-SERP visual treatment for most categories. The reasonable practice in 2026: ship HowTo on genuinely procedural content because AI Overview and ChatGPT cite step-by-step content disproportionately — not because of SERP rich-result hopes.

How to apply

HowTo is straightforward when you have genuinely step-ordered content. Three concrete moves:

• Only mark up pages with real procedural content: a page like "5 things to do when X happens" is informational, not procedural — use Article schema. HowTo is for "do A, then B, then C" where order matters. Mismarking risks being flagged as misused markup.
• Give each step a meaningful name: AI engines often quote just the step name when condensing a HowTo. "Step 1" is unhelpful; "Paste into the validator" carries information and embeds cleanly.
• Validate via the Rich Results Tester: Google's validator still works for HowTo even after rich results were demoted — it confirms the markup parses, just doesn't promise SERP treatment.

What to skip: HowTo on FAQ-shaped content (use FAQPage). Mismatched schema-type-to-content-type pairings can trigger Google's "Spammy structured markup" manual action and tend to be ignored or down-weighted by AI engines.

How it relates to other concepts

• Sibling JSON-LD type to FAQ schema and DefinedTerm schema.
• Direct expression of procedural answer blocks — each HowToStep is one extractable unit.
• Common pairing with Article schema on long-form how-to guides — Article for the wrapper, HowTo for the embedded procedure.
• Underlies AEO for "how do I X" queries — voice assistants and AI Overview lean heavily on HowTo when answering procedure questions.