HowTo Schema

Element Code: RI-011

What HowTo schema is

HowTo is a schema.org type for content that walks a reader through completing a task. The core structure is a HowTo item with a name, an ordered array of step items (each a HowToStep with its own name, text, image, and URL anchor), plus optional properties like tool, supply, totalTime, and estimatedCost. It is the instructional cousin of Recipe schema, and the boundary matters: food preparation instructions should use Recipe, not HowTo.

For a few years this markup powered a genuinely nice Google SERP feature: expandable step lists, sometimes with images per step, and it fed Google Assistant's guided how-to experiences. That era is over, and any guide that does not say so up front is wasting your time.

The blunt truth: Google killed the HowTo rich result

The timeline, per Google Search Central announcements: in August 2023 Google restricted HowTo rich results to desktop only. In mid September 2023 it deprecated them entirely, on all devices, for all sites. The HowTo search appearance report was subsequently pulled from Search Console. Unlike FAQ rich results, which survive for a small set of government and health sites, HowTo got the full sunset. Nobody gets HowTo rich results from Google anymore.

So when an audit tool flags "instructions lack HowTo schema," you need calibrated expectations before you burn dev hours on it:

• There is no Google rich result to win. Zero. Adding HowTo markup will not change how your listing renders in Google.
• It is not harmful either. Valid HowTo markup is still legal schema.org vocabulary. Google simply ignores it for display purposes.
• Residual value is real but modest. Structured steps are unambiguous for any parser that cares, including answer engines and internal search tooling. Some teams also drive their own front-end step components from the same JSON, which keeps content and markup in sync for free.

My honest practitioner take: I stopped recommending net-new HowTo markup projects in late 2023. If your CMS template already emits it correctly, keep it, it costs nothing. If a contractor is quoting you billable hours to add HowTo schema across a content library in 2026 because "rich results," that is a damn refund waiting to happen.

Where the effort should actually go

HowTo property reference

If you do maintain HowTo markup, here is the grid that matters. Everything else is optional garnish.

How to check what your pages currently emit

1. Schema Markup Validator (validator.schema.org): the right tool now that this type has no Google feature; it validates pure schema.org correctness.
2. Rich Results Test: still parses the page, but do not expect a HowTo entry in the eligible results list; the feature is gone. Use it mainly to confirm your JSON-LD parses at all.
3. Screaming Frog: enable structured data extraction and validation under Configuration, then Spider, then Extraction, crawl the site, and review the Structured Data tab. This surfaces every page emitting HowTo, including template-driven markup nobody remembers adding.
4. Grep your templates: if markup comes from a plugin or theme, search the codebase for "HowTo" and confirm what is generated versus what the docs claim.

DO and DON'T

What good looks like

For this check, "good" in 2026 is mostly editorial: a how-to page whose steps are numbered, atomic, and honestly ordered, with headings a scanner can follow and a screenshot wherever a step gets fiddly. If HowTo JSON-LD is present it validates cleanly on validator.schema.org, mirrors the visible steps exactly, and nobody on the team believes it is buying Google SERP features. The structured data box is ticked with correct expectations attached, and the real investment went into the content itself. That is the version of this check I sign off on.

FAQ