HowTo Schema
HowTo schema marks up step-by-step instructions for machines. Learn the properties, what changed with Google rich results, and when it is still worth adding.
TL;DR
HowTo schema is the structured data type for step-by-step instructions, describing a task and the ordered steps that complete it. Google retired HowTo rich results for most surfaces, which changed the reason to use it rather than removing the reason entirely.
Why HowTo schema still has a use
The search feature it was built for largely went away. What remains is a machine-readable description of a procedure, which is what AI engines reproduce when someone asks how to do something.
- Procedure clarity: Marked-up steps state their order and boundaries explicitly, so an engine reproducing them keeps the sequence intact.
- Extraction quality: A step with its own name and text is easier to lift correctly than a numbered paragraph in prose.
- Tools and materials: Prerequisites are stated as data rather than buried in an intro nobody reads.
- Assistant surfaces: Spoken and conversational responses handle procedures well when the structure is explicit.
How to implement HowTo schema
Confirm it is genuinely a procedure
One outcome reached through ordered steps. A list of tips is not a HowTo, however numbered it looks.
Name the task plainly
The name property should state the outcome the way someone would search for it.
Break steps into HowToStep items
Each step gets its own name and text. Resist merging two actions into one step for tidiness.
Declare tools and supplies
HowToTool and HowToSupply cover what the reader needs before starting.
Add totalTime where meaningful
An ISO 8601 duration, useful for tasks where time is a real consideration.
Mirror the visible steps
The marked-up sequence must match what the page shows, in the same order.
HowTo schema vs. FAQ schema
HowTo schema: An ordered sequence toward a single outcome. Steps depend on each other and make little sense reordered.
FAQ schema: Independent question and answer pairs. Each stands alone and order carries no meaning.
The test is whether reordering breaks the content. If step three only works after step two, it is a HowTo. If any entry could open the list, it is an FAQ.
Structured procedures are only useful if engines can reach and read them. Findrix checks structured data, crawler access and rendering in a 31-point technical audit, then tracks how often seven AI engines cite you against named competitors. Every gap comes with the fix already written: technical, content and off-site. The audit is free, takes about a minute, and requires no signup.
HowTo schema properties
- name: The task being completed, phrased as an outcome.
- step: An ordered array of HowToStep items, each with name and text.
- tool: Items the reader uses and keeps.
- supply: Items consumed during the task.
- totalTime: Expected duration as an ISO 8601 value.
- image: Illustrations per step where they genuinely help.
Whether it is worth your time now
Honestly, for most sites this is low priority. The rich result that justified the implementation effort is gone from general search, and the remaining benefit is a modest improvement in how cleanly AI engines extract a procedure they would likely reproduce anyway.
Add it if you already publish real how-to content and the markup is cheap to generate from your existing templates. Skip it if implementing means hand-writing JSON-LD for a handful of pages.
The higher-leverage version of the same work is clear steps in the HTML: numbered headings, one action per step, no prerequisites buried in prose.
Frequently asked questions
Did Google remove HowTo rich results?
Google deprecated HowTo rich results for most search surfaces, so typical sites no longer see the visual step display they were implementing for. The markup is still valid and still parsed; it just no longer earns that feature.
Is HowTo schema still worth adding?
Only where the cost is near zero. If your templates can generate it automatically for genuine procedural content, it makes steps cleaner for AI extraction. If it requires manual work per page, spend that effort on clearer on-page structure instead.
What is the difference between HowTo and Recipe schema?
Recipe is a specialised type for food, with properties for ingredients, nutrition, cooking time and yield. It still supports rich results in ways HowTo no longer does. Use Recipe for cooking content and HowTo for everything else procedural.