HowTo Schema Specification for AI Search

TL;DR

HowTo schema still exists at schema.org but Google no longer renders HowTo rich results. Implementing the markup will not produce a step carousel in classic SERP. It does, however, reinforce content structure for AI Overviews, AI Mode, Perplexity, and ChatGPT, which retrieve and parse structured data alongside visible text. Keep HowTo markup on genuine step-by-step pages, drop it from supplementary sections, and prioritize on-page step structure (numbered headings, image per step, validation steps) over schema padding.

Status in 2026

Google announced in August 2023 that HowTo rich results would no longer appear on desktop as of September 13, 2023, and the format was effectively deprecated (Google Search Central blog — Changes to HowTo and FAQ rich results). The March 2026 Google update further narrowed structured-data eligibility so that schema describing supplementary or off-topic page sections no longer qualifies for rich results, ending widespread HowTo padding (Digital Applied schema markup after March 2026). Multiple practitioner reports note Google scaled back support across several structured-data types during the same window (WebFX summary of Google schema deprecations).

HowTo therefore is not a path to rich results in 2026. Use it for entity signaling and AI extraction quality, not for SERP enhancements.

Required and Recommended Fields

schema.org HowTo inherits from CreativeWork. The minimum useful spec for AI search:

For each HowToStep:

Note: schema.org marks steps (plural) as superseded; use step.

Minimum Compliant Example (JSON-LD)

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Reset a Yale Smart Lock",
  "description": "Reset procedure for a Yale Smart Lock when you have lost the master code.",
  "totalTime": "PT5M",
  "image": "https://example.com/yale-reset-hero.jpg",
  "step": [
    { "@type": "HowToStep", "name": "Locate the reset button", "text": "Open the back panel and locate the small reset button." },
    { "@type": "HowToStep", "name": "Hold for 10 seconds", "text": "Press and hold the reset button for 10 seconds until the keypad beeps." },
    { "@type": "HowToStep", "name": "Re-pair with app", "text": "Open the Yale Access app and follow the pairing flow." }
  ]
}

Complete Example with Images, Supplies, and Tools

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Replace a Standard Light Switch",
  "description": "Step-by-step replacement of a single-pole light switch. Read all safety steps before starting.",
  "totalTime": "PT30M",
  "estimatedCost": { "@type": "MonetaryAmount", "currency": "USD", "value": "6" },
  "image": "https://example.com/light-switch-hero.jpg",
  "supply": [
    { "@type": "HowToSupply", "name": "Single-pole switch" },
    { "@type": "HowToSupply", "name": "Wire nuts" }
  ],
  "tool": [
    { "@type": "HowToTool", "name": "Insulated screwdriver" },
    { "@type": "HowToTool", "name": "Voltage tester" }
  ],
  "step": [
    { "@type": "HowToStep", "position": 1, "name": "Turn off power", "text": "Switch off the breaker. Verify with a voltage tester.", "image": "https://example.com/step-1.jpg" },
    { "@type": "HowToStep", "position": 2, "name": "Remove faceplate", "text": "Unscrew the cover and pull the switch out gently.", "image": "https://example.com/step-2.jpg" },
    { "@type": "HowToStep", "position": 3, "name": "Disconnect wires", "text": "Loosen terminal screws and disconnect the line, load, and ground.", "image": "https://example.com/step-3.jpg" },
    { "@type": "HowToStep", "position": 4, "name": "Connect new switch", "text": "Match line to brass, neutral to silver, ground to green.", "image": "https://example.com/step-4.jpg" },
    { "@type": "HowToStep", "position": 5, "name": "Test and re-mount", "text": "Restore power, test, then re-mount the faceplate.", "image": "https://example.com/step-5.jpg" }
  ]
}

Image Patterns

• Hero image at the HowTo level should depict the finished result.
• Each HowToStep.image should depict that specific action, not the result.
• Use a stable absolute URL on a domain you control. Avoid hot-linking.
• Recommended dimensions: 1200x800 minimum, 4:3 aspect ratio for best AI extraction; AI engines that build multimodal answers prefer high-resolution sources.
• Provide alt text on the on-page element matching HowToStep.text.

Validator Quirks

• Rich Results Test will warn but not fail. Since the rich result is deprecated, the Rich Results Test no longer reports HowTo enhancements. The Schema Markup Validator at validator.schema.org still validates structure.
• steps vs step. Use step. The plural steps is superseded; some validators still accept it but it is discouraged.
• Missing image on steps. Validators do not error, but AI engines extract step content less reliably without an associated image.
• Nested HowToSection. Allowed but rarely useful for short tutorials. Use only for long multi-phase tutorials.
• HTML inside text. Plain text is safest. Some validators tolerate inline HTML; AI extractors generally strip it.

Five Real-World Examples

1. Smart-home reset tutorials — short 3-5 step pages with one image per step are the textbook fit.
2. DIY electrical and plumbing — include supply, tool, and an explicit safety step at position 1.
3. Software setup walkthroughs — each step includes a screenshot; tool lists "web browser" or specific app names.
4. Cooking tutorials that are not full recipes — use HowTo for technique posts (e.g. "how to fold dumplings"); use Recipe schema for full recipes.
5. Onboarding for SaaS tools — in-product walkthroughs published as public tutorials benefit from totalTime so AI assistants can quote duration.

Common Mistakes

• Using HowTo for content that is not actually step-by-step. Listicles or articles styled as numbered points should not be marked as HowTo.
• Schema padding. Adding HowTo markup to a supplementary section of an unrelated page is now treated as low quality and excluded from rich results entirely.
• Mismatch between schema text and on-page text. Schema must mirror what the user sees. AI engines treat structured data largely as text on the page (Search Engine Roundtable test on ChatGPT and Perplexity reading invalid schema as text), so mismatch produces extraction confusion.
• Skipping the description. AI engines often quote the description; omit and you give up an easy citation surface.
• Stale totalTime. If the page text changes the procedure, update the duration.
• Treating HowTo as a replacement for clear on-page steps. AI extractors prefer numbered H2/H3 headings, an image per step, and a verification section. Schema reinforces; it does not replace.

FAQ

Q: Should I still use HowTo schema in 2026?

Yes for genuine step-by-step pages. No for off-topic supplementary sections. The rich result is gone but the structured data still reinforces content for AI extraction.

Q: Will HowTo schema show a step carousel in Google?

No on desktop since September 2023, and effectively no on mobile. Treat it as an entity-context signal, not a SERP enhancement.

Q: Does Perplexity or ChatGPT use HowTo schema?

They parse structured data alongside visible HTML and treat it largely as text. Valid HowTo markup on a step-by-step page reinforces extraction; invalid or padded markup is read as ordinary text and may dilute extraction quality.

Q: Can I keep HowTo on existing pages without harm?

Yes if the page genuinely is step-by-step and the schema mirrors the visible content. Remove it from pages where the schema described supplementary content, since post-March-2026 Google treats that as schema abuse.

Q: What is the difference between HowTo and Recipe?

Use Recipe for cooking content with ingredients, nutrition, and timings. Use HowTo for non-recipe step-by-step procedures including cooking techniques that are not full recipes.

Q: Does HowTo work for video tutorials?

Yes when the video is hosted on the same page; combine with VideoObject and reference HowToStep image or use a separate HowToStep text per chapter. The video should still have a transcript.

Q: How long should step.text be?

2-4 sentences. Short enough that AI assistants can quote a single step inline; long enough to include the verification or expected result.