How to add HowTo schema
A step by step way to add HowTo schema to a procedure page so an AI engine reads your steps in order instead of guessing them from formatting.
You wrote a clean step-by-step guide, numbered it, formatted it nicely, and a machine still might read it as one long blob of prose. Numbered formatting is a visual cue, not a labeled fact. HowTo schema turns your steps into something an engine reads as steps, in order.
This guide does that, and it is a short job on a page that is genuinely a procedure.
What HowTo schema does
HowTo schema is structured data that says: this page is a procedure, here are its steps, in this order. Without it, an engine sees headings and paragraphs and has to infer that they form a sequence. With it, the sequence is explicit.
HowTo schema matters when getting the order right matters, which is the whole point of a procedure. Step three before step one is not a small error.
Do the task
Step 1: Confirm it is really a procedure
This is the most-skipped step and the most important. HowTo describes ordered steps toward a result: a setup, a repair, an install. If your page is an opinion piece, a list of unrelated tips, or an FAQ, HowTo is the wrong label. Use the schema that matches what the page is.
Step 2: Break the task into clean steps
Each step should be one distinct action, with its own heading or clearly delimited block in the visible text, in the order a reader follows. If your steps are tangled into paragraphs, untangle them on the page first. The page should be cleanly stepped before the markup describes it that way.
Step 3: Write the HowTo JSON-LD
Build a HowTo object with a name and a list of HowToStep entries. Each HowToStep carries its name and text, copied from the page. The markup mirrors the visible steps, it does not invent new ones.
Step 4: Place it in the page
Wrap it in a <script type="application/ld+json"> tag and add it through a custom HTML block, a snippet plugin, or the template header. It lives in the source.
Step 5: Validate and keep it in sync
Run the page through a structured data validator. Then, when you reorder or reword a step on the page, do the same in the markup. A HowTo block describing steps the page no longer has is a machine confidently reading a stale recipe.
The old way and the new way
The old way relied on numbered lists and bold step headings, visual signals meant for a human eye, and trusted an engine to recognize the pattern.
The new way labels the steps as steps, so the order and the boundaries are facts rather than inferences. The reader sees the same tidy list. The machine finally reads it as the sequence you meant. The risk you remove is an engine relaying your procedure with the steps shuffled.
The honest part
HowTo is the most over-applied schema there is. People bolt it onto pages that are not procedures because it looks thorough, and the result is a machine being told a page is something it is not. That hurts more than a missing label. If in doubt, look at the page and ask whether a person would actually follow it step by step. If not, skip it.
And adding HowTo does not make an engine quote your guide. It makes the steps parseable in order. Whether ChatGPT, Perplexity, Gemini, or Claude then uses it is something we measure, not something we promise. The automated apply, with a preview and a per-fix approval, runs only through the connected Citedon plugin on WordPress. Elsewhere the scan diagnoses it and you paste the block.
Where to start
Run a free scan on your most important how-to page and see whether an engine reads it as ordered steps or as one undifferentiated block. If the structure is the problem, structure the page for AI answers first, then add the HowTo label on top.