HowTo Schema Generator: Create Valid HowTo JSON-LD in Seconds
Understand with AI
Discuss with your preferred AI assistant
Only "name" and "step" are mandatory — everything else is recommended polish that improves how your guide is understood.
A valid HowTo needs at least two ordered steps; one-step "tasks" are not how-tos and should not use the markup.
Fill in your steps, tools, and supplies and copy valid JSON-LD in under a minute — no code, no signup.
HowTo schema is structured data that tells search engines a page contains a set of steps for completing a task. When you mark up a tutorial with valid schema.org/HowTo JSON-LD, you give Google, Bing, and AI answer engines a clean, machine-readable version of your instructions — which improves how your guide is understood, surfaced, and quoted.
This guide explains what HowTo schema is, when to use it, exactly which fields matter, and how to generate valid JSON-LD in seconds with the free SemlyPro HowTo Schema Generator above.
What Is HowTo Schema?
HowTo schema is a vocabulary from schema.org that describes a task and the ordered steps required to complete it. It is expressed as JSON-LD — a small block of structured data you drop into the <head> or body of your page inside a <script type="application/ld+json"> tag.
A complete HowTo object can describe the task name, a description, an image, the total time required, the estimated cost, the tools and supplies needed, and — most importantly — an ordered list of HowToStep items. Each step can carry its own name, instruction text, and image.
Search engines use this markup to understand your content with far less guesswork than parsing raw HTML. Even where dedicated HowTo rich results are limited, structured data still strengthens topical clarity and helps AI Overviews and assistants extract accurate, attributable steps.
When Should You Use HowTo Schema?
Use HowTo markup when your page genuinely teaches a reader to accomplish a single, concrete task through a sequence of steps. Good candidates include:
- Repair and assembly guides — "How to replace a bike tube", "How to assemble a desk".
- Software and setup tutorials — "How to set up two-factor authentication".
- Craft, DIY, and home projects — "How to tile a backsplash".
- Process walkthroughs — "How to file a tax return", "How to register a company".
Do not use HowTo schema for recipes (use Recipe schema instead), for marketing copy with no real steps, or for content that is just a list of tips rather than an ordered procedure. The markup must accurately reflect the visible content on the page.
The Fields That Matter
A best-practice HowTo object covers the following. The first two are required; the rest are strongly recommended and make your markup more useful.
| Field | What it is | Status |
|---|---|---|
| name | The title of the task, e.g. "How to Tie a Windsor Knot". | Required |
| step | An ordered list of HowToStep items, each with text (and ideally a name and image). | Required |
| description | A short summary of what the reader will accomplish. | Recommended |
| image | A representative image of the finished result; per-step images are even better. | Recommended |
| totalTime | How long the task takes, encoded as an ISO-8601 duration (e.g. PT15M). | Recommended |
| tool | HowToTool items — equipment you keep and reuse (a drill, a mirror). | Recommended |
| supply | HowToSupply items — materials consumed during the task (screws, paint). | Recommended |
| estimatedCost | A MonetaryAmount with a currency and value. | Optional |
How to Generate HowTo Schema, Step by Step
1. Name the task clearly
Start with a precise, action-oriented title that matches your page heading. "How to..." phrasing works well because it mirrors how people search and how the markup is understood.
2. Break the task into real, ordered steps
Give each step a short name and a clear instruction sentence. A HowTo should have at least two steps; the steps must appear in the same order as on the page. Adding a per-step image is one of the highest-value upgrades you can make.
3. List tools and supplies separately
Tools are reusable equipment; supplies are consumed during the task. Separating them correctly helps assistants summarise what a reader needs to gather before starting.
4. Add time and cost
Enter a total time in plain language ("15 mins", "1 hr 30") — the generator converts it to a valid ISO-8601 duration automatically. Add an estimated cost when the task involves a purchase.
5. Validate, then publish
Copy the generated <script> tag into your page, then confirm it with Google's Rich Results Test and Schema Markup Validator. The generator above runs the same required-field and best-practice checks live as you type.
HowTo Schema Best Practices
- Mark up only what is visible on the page — never hide steps that only exist in the markup.
- Keep step order identical between the markup and the on-page content.
- Add an image to every step where you can; visual steps are more useful to humans and machines alike.
- Use HowToTool for equipment and HowToSupply for consumables — do not mix them.
- Place exactly one HowTo block per page and keep it in sync whenever you edit the tutorial.
Common HowTo Schema Mistakes
- Using HowTo for a recipe — Google expects Recipe schema for food.
- Writing a single giant step instead of an ordered sequence.
- Free-typing the total time in a format that is not valid ISO-8601 (the generator fixes this for you).
- Marking up promotional or advertising content as instructional steps.
Expert Tips
Add an image to every step
Per-step images are the single highest-value upgrade. They make your guide more useful to readers and give search and AI engines a visual anchor for each instruction.
Always validate before you ship
Paste the generated script into Google’s Rich Results Test and the Schema Markup Validator. The tool above runs the same required-field checks live, but a final validation catches page-level issues too.
Frequently Asked Questions
What is HowTo schema used for?
HowTo schema gives search engines a structured, ordered description of the steps needed to complete a task. It helps Google, Bing, and AI answer engines understand, surface, and accurately quote your tutorial, and it strengthens the topical clarity of instructional pages.
Is HowTo schema still worth adding?
Yes. Even though dedicated HowTo rich results have been scaled back in some regions, valid structured data still improves machine understanding of your content, supports AI Overviews and assistants, and future-proofs your guides against ranking and presentation changes.
What's the difference between a tool and a supply?
A tool (HowToTool) is reusable equipment you keep after the task — a drill, a wrench, a mirror. A supply (HowToSupply) is a material consumed during the task — screws, paint, a length of fabric. Listing them in the correct property makes your markup clearer.
Where do I put the generated JSON-LD?
Paste the generated <script type="application/ld+json"> tag anywhere in the page's HTML — the <head> or body both work. Add one HowTo block per page, keep it in sync with the visible steps, and validate it with Google's Rich Results Test.