What the HowTo Schema Generator does
This tool builds valid HowTo structured data in JSON-LD format for tutorial and step-by-step instruction pages. You enter the overall task name, an optional total time, any tools or supplies needed, and then each step in order with its text and an optional image, and the generator produces a spec-compliant script block describing the whole procedure. HowTo markup is for content that teaches a reader to accomplish a specific physical or digital task through a defined sequence of steps, such as how to tie a tie, how to reset a router, or how to install a shelf. It describes the process as structured, ordered data rather than leaving it as plain prose.
Before you invest in HowTo markup, it is essential to understand how its role has changed. HowTo rich results, which once showed expandable step-by-step previews directly in search, have been deprecated by Google as a visible search feature for the general web. That means adding HowTo markup today is unlikely to produce the old step-carousel snippet in standard Google results. The markup is still valid schema.org vocabulary and still useful for describing a procedure to machines, but anyone adding it expecting the classic HowTo rich result is working from outdated guidance. This generator produces correct HowTo markup; just set your expectations about where it pays off.
Required and recommended properties for HowTo
The required core of a HowTo is a name describing the overall task and a step property that is an ordered array of HowToStep objects. Each HowToStep needs, at minimum, content describing what to do in that step, supplied through its text or through nested HowToDirection items. The steps are inherently ordered, and the sequence in the array is the sequence the reader should follow, so the order is meaningful and must match the order on the page. A HowTo with a name but no steps, or steps with no instructional content, is not a valid procedure and will be rejected.
Several recommended properties make a HowTo richer and more useful. totalTime, expressed as an ISO 8601 duration, tells how long the whole task takes. tool describes the implements needed, and supply describes the consumable materials used up during the task; these map to HowToTool and HowToSupply objects. Each step can carry an image, a url that anchors to that step on the page, and a name for the step heading. estimatedCost can describe how much the materials cost. An image on each step is particularly valuable, because it makes the procedure clearer to both humans and any system parsing it. The key rule throughout is that everything in the markup must correspond to content visibly present on the page.
Where HowTo schema still helps in 2026
With the search-results rich result gone, the value of HowTo markup has shifted toward machine comprehension. A clean HowTo block hands an AI Overview, a chatbot, or a voice assistant a fully structured, ordered procedure that is trivial to extract and present. When a user asks an assistant how to do the exact task your page covers, content that is already chunked into discrete, ordered steps with clear text is far easier to lift faithfully than a wall of prose with steps buried in paragraphs. So while you should not expect a visual snippet in classic search, well-formed HowTo data can still improve how cleanly AI answer engines understand and reproduce your instructions.
That said, the strongest investment for how-to content in 2026 is the on-page structure itself: clear numbered headings, one action per step, supporting images, and a concise summary near the top. Structured, scannable instructions help both readers and machines regardless of whether you add the JSON-LD. HowTo markup is a complement that formalizes that structure for parsers; it is not a substitute for writing the procedure clearly. Use the generator to add a correct machine-readable layer on top of content that is already genuinely well organized for a human following along.
How to read the generated output
The output is a single script block with an at-type of HowTo. At the top you will see the task name and any totalTime, tool, and supply values, followed by the step array of HowToStep objects in order. Walk through the step array and confirm the count and the order exactly match the steps shown on the page, and that each step's text is the same instruction a reader sees. If you supplied per-step images, check that each image URL is correct and points to the illustration for that specific step. The ordering is the most important thing to verify, because a procedure with steps out of sequence is worse than no markup at all.
Confirm the tool and supply distinction is right: a tool is something reusable like a screwdriver, while a supply is something consumed like screws or paint. Getting these mixed up does not break validation but it misrepresents the task. The totalTime should be a realistic estimate of the full task, formatted as an ISO 8601 duration. When you copy the block out, place it on the same page that visibly contains the numbered steps, never on an overview page that only links to the instructions, because the steps in the markup must be present in the rendered content for users.
Common HowTo schema mistakes
The most fundamental mistake now is choosing HowTo for content that is not actually a step-by-step procedure, such as a listicle, a buying guide, or a general explainer. HowTo is specifically for completing a task through ordered steps; applying it to non-procedural content is incorrect. The second common mistake is marking up steps that are not visibly present on the page, or adding steps to the markup that do not exist in the content, which violates the rule that structured data must reflect visible content. A third is putting the entire procedure into a single step instead of breaking it into the discrete steps the reader actually follows.
Other frequent errors include using HowTo where the page is really a recipe, which has its own dedicated Recipe type with ingredient and nutrition properties that HowTo lacks; getting the tool and supply properties backwards; omitting the step content so a step has a heading but no instruction; and formatting totalTime as plain text instead of an ISO 8601 duration. Some authors also try to revive the old rich result by over-marking, adding images and metadata to chase a snippet that no longer exists for the general web, which is wasted effort. Keep the markup accurate to the page and let it serve machine comprehension rather than a deprecated visual feature.
HowTo versus Recipe versus FAQPage
HowTo is most often confused with Recipe and with FAQPage. Recipe is the correct, and still rich-result-eligible, type for cooking instructions; it extends the step concept with food-specific properties like recipeIngredient, recipeYield, cookTime, and nutrition, and it still earns visible recipe enhancements in search, so food content should use Recipe rather than HowTo. FAQPage is for a set of independent questions and answers, not an ordered task, so a page of common questions is FAQPage, while a page that walks through doing one thing in sequence is HowTo. Choosing the type that matches the true shape of the content is what keeps the markup meaningful.
On a tutorial page, HowTo markup can coexist with Article markup describing the page as editorial content and BreadcrumbList describing its place in the site. Keep each type in its own script tag. Given that the HowTo rich result is gone for the general web, weigh whether the markup is worth maintaining for your case; for instructional content that you want AI assistants to reproduce accurately, the structured steps can be worthwhile, while for content that is borderline procedural, the clearer win is simply writing well-structured, numbered instructions on the page itself.
What to do after you generate it
Paste the block into the page that visibly contains the numbered steps, then run the URL through Google's Rich Results Test and the Schema Markup Validator. The Rich Results Test will confirm the HowTo is syntactically valid even though it no longer drives a visible search feature for the general web, and the validator will give you an independent syntax pass. Verify that the steps, tools, supplies, and timing in the markup all match what a reader sees on the page, since that correspondence is the rule that keeps the markup trustworthy.
Set realistic expectations and prioritize accordingly. Do not add HowTo markup hoping to win back the old step carousel; instead, treat it as a way to hand clean, ordered instructions to AI answer engines and to formalize the structure of genuinely procedural content. Invest first in making the on-page steps clear, single-action, and well illustrated, then layer the HowTo markup on top so machines can read the procedure as easily as a human can follow it. For cooking content, reach for Recipe instead, and reserve HowTo for true task-completion tutorials where ordered steps are the heart of the page.