Structured data describes your content to a machine, not to a reader
A page can read perfectly clearly to a human — numbered steps, clear instructions — while remaining completely opaque to a search engine trying to programmatically identify 'this is a sequence of ordered steps.' HowTo schema, expressed as JSON-LD, closes that gap: it's a separate block of structured data embedded in your page that explicitly labels the name of the task, each step's name and instruction text, and optionally the total time required, in a format search engines can parse without guessing.
This distinction — visible content versus machine-readable structured data — is exactly why the schema exists as separate JSON-LD rather than being inferred automatically from your page's HTML structure, even if your HTML already has a clean, numbered list.
What HowTo schema can unlock in search results
Marking up step-by-step instructions with HowTo schema gives search engines the option to render a rich result — an enhanced search listing that can show estimated total time, a preview of individual steps, and sometimes step images, directly in the search results rather than requiring a click-through just to see the outline. This is a visibility advantage specifically for instructional content, distinct from ordinary blue-link search listings.
Generating your schema
Give your how-to a name, such as 'How to brew pour-over coffee.'
Add each step with a short name and the detailed instruction text.
Optionally enter a total time in ISO 8601 duration format, like PT30M.
Copy or download the generated JSON-LD script tag to embed in your page.
Writing ISO 8601 durations without guessing at the syntax
| Duration | ISO 8601 format | Meaning |
|---|---|---|
| 30 minutes | PT30M | 30 minutes |
| 1 hour 30 minutes | PT1H30M | 1 hour, 30 minutes |
| 2 hours 30 minutes 15 seconds | PT2H30M15S | 2 hours, 30 minutes, 15 seconds |
| 45 seconds | PT45S | 45 seconds |
Decoding the format: why 'PT' and why the order matters
Whether your guide actually qualifies for HowTo schema
Not every piece of instructional content is a good fit for this schema type. HowTo is specifically meant for guides that teach a task with a clear sequence of steps — not every list-formatted page qualifies just because it has numbered items. Recipes have their own dedicated schema type rather than using HowTo, and it's worth noting that eligibility for HowTo rich results in some categories has tightened over time on Google's end, meaning markup alone doesn't guarantee a rich result will actually render, even when it's technically valid and correctly applied.
Choosing between HowTo and FAQ schema
These two schema types are easy to conflate because both structure content into discrete labeled chunks, but they answer fundamentally different content shapes. FAQ schema marks up question-and-answer pairs — content structured around answering discrete questions a reader might have. HowTo schema marks up an ordered sequence of steps that walk through completing a task, where order genuinely matters and skipping a step would break the process. A page that answers 'What is X' style questions belongs under FAQ schema; a page that walks through 'Step 1, then step 2, then step 3' to accomplish something belongs under HowTo.
Validating before you deploy
Since a malformed or ineligible schema block provides no benefit and can even trigger a search console warning, it's worth checking your generated JSON-LD before publishing rather than assuming correctness. Paste the output into Google's Rich Results Test or Schema.org's own validator, both of which will flag structural or syntax problems — including a malformed ISO 8601 duration — before the markup ever goes live on your page.
Common mistakes
Writing duration in plain language ('30 minutes') instead of the required ISO 8601 format (PT30M), which validators will reject.
Applying HowTo schema to a recipe page instead of using the dedicated recipe schema type it's meant for.
Assuming valid markup guarantees a rich result — eligibility for the enhanced search display has tightened over time and isn't solely determined by correct syntax.
Reaching for HowTo schema on a page that's actually structured as questions and answers, when FAQ schema is the correct fit for that content shape.
Real use cases
Marking up a tutorial or DIY guide with step-by-step instructions to make it eligible for an enhanced search listing.
Adding structured data to an existing numbered-list guide without changing its visible content or layout.
Documenting a process page (setup instructions, troubleshooting steps) with time estimates included.
Preparing multiple instructional pages consistently formatted with valid JSON-LD before a content audit or SEO push.
Frequently asked questions
Q: What is HowTo schema for?
A: It marks up step-by-step instructions so search engines can render them as a rich result — sometimes with images, estimated time, and per-step previews.
Q: Does every guide qualify?
A: No. HowTo schema is meant for instructions that teach a task. Recipes have their own schema, and Google has tightened eligibility for some categories over time.
Q: What is ISO 8601 duration?
A: A standard way to write durations. PT30M means 30 minutes; PT1H30M means 1 hour 30 minutes; PT2H30M15S adds 15 seconds.
Q: Do I need images for each step?
A: No, they're optional. Adding a HowToStep.image can improve the rich result, but the text fields are the only required data.
Q: How is this different from FAQ schema?
A: FAQ schema marks up Q&A pairs; HowTo marks up ordered instructions. Use FAQ when the page answers questions, HowTo when it walks through a process.
Q: Can I validate the result?
A: Yes — paste the JSON into Google's Rich Results Test or Schema.org's validator before deploying.
Generate your HowTo schema now
Build yours with the HowTo Schema Generator. Structuring questions and answers instead? Try the FAQ Schema Generator. Also check your page's meta tags with the Meta Tag Generator, or preview how it'll appear in search with SERP Preview.
