HowTo schema
Structured data that labels a set of instructions as ordered steps, so a machine reads step one, step two, and step three as a sequence instead of guessing from headings.
A recipe and a refund policy can look identical to a machine: blocks of text under headings. HowTo schema is how you tell an engine that one of them is a sequence of steps to follow.
What HowTo schema is
HowTo schema is structured data that labels a set of instructions as ordered steps. It states the sequence outright: this is step one, this is step two, here is what each step requires.
It is usually written in JSON-LD, a small block in the page code. The reader is not a person following along. It is a machine that wants to reuse your process without scrambling the order.
Why engines lean on it
Steps only work in sequence. Hand an engine three paragraphs and it has to decide which comes first and whether they are even steps at all. Label them and the order is no longer a guess.
That matters most when an engine reuses your instructions in an answer. If it reorders your steps or drops one, the result is wrong in a way that reflects on you. Explicit labeling lowers that risk.
The old way and the new way
The old way added HowTo schema to chase a step-by-step rich result in Google. Google has since dialed those displays back, and many people abandoned the markup.
The new way treats HowTo schema as a way to hand an engine a clean, ordered procedure in your own words. The payoff is not a search decoration. It is being read in the right sequence by systems that now assemble answers.
The damaging admission
HowTo schema misleads the moment your process changes. You revise a step in the visible text, leave the markup behind, and now a machine is teaching people a version you no longer recommend.
It is also easy to mark up steps that do not match the page, or to label a marketing list as instructions. Present is not the same as correct, and confidently wrong steps are worse than no steps. This markup also does not fit every page: a plain definition or a pricing table is not a HowTo, and forcing it there does more harm than good.
How to check yours
Take a page with instructions and ask three things. Is there HowTo schema. Is it valid. Do the labeled steps match, in order, the steps a reader sees.
Run a free scan on any URL to see whether an engine finds your HowTo schema, whether it validates, and where it drifts from the page. For the broader pattern, read how to structure a page for AI answers.