Free HowTo Schema Generator
Generate valid HowTo JSON-LD structured data for your tutorials and step-by-step guides. Add your steps, supplies, and tools, then copy the markup. Free, no sign-up required.
Build Your HowTo Schema
How-to basicsThe core details of the guide you are marking up.
The title of the how-to. This is required for valid HowTo markup.
How long the whole task takes. We convert it to the ISO 8601 format Google expects, for example 30 becomes PT30M. Leave blank to omit it.
Supplies (optional)Consumable materials the reader needs, the things used up during the task.
Tools (optional)Reusable objects the reader needs, the things not used up during the task.
StepsThe ordered instructions. Number them in the order they appear here. Each step needs text to be included.
Enter your name and at least one step above and your JSON-LD will build here automatically.
Generated JSON-LD
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "HowTo"
}
</script>How to add it to your site
- Copy the code above.
- Paste it inside the
<head>section of the how-to page (or your guide template). - Validate it with the Google Rich Results Test or the Schema.org Validator.
- Deploy, then request indexing in Google Search Console to speed things up.
Build better guides around your schema
Structured data tells search engines what your guide is. These free widgets make the page better for readers.
Accordion
Turn a long tutorial into clean, collapsible sections so readers scan first and expand the step they need. A better reading experience backs up your structured data.
Tabs
Split a multi-part how-to into tabs so readers jump straight to the stage they came for. Clear on-page structure reinforces the signals your schema sends.
Image Hotspot
Pin clickable hotspots on a screenshot or product photo so each step points at exactly the right spot. Visual guidance that matches your marked-up steps.
Before & After Slider
Show a before-and-after slider so the outcome of your how-to is obvious at a glance. Proof of the result you just documented step by step.
Explore More Free Tools
Other free tools to help you optimize and grow.
Free Website Schema Generator
Generate Organization, WebSite, and LocalBusiness JSON-LD structured data for your whole site.
Use Tool →Free Article Schema Generator
Generate Article, BlogPosting, and NewsArticle JSON-LD structured data for your posts.
Use Tool →Free FAQ Schema Generator
Generate valid FAQ Page JSON-LD structured data to earn FAQ rich results.
Use Tool →Free Meta Tag Generator
Generate title, description, and social meta tags for any page in seconds.
Use Tool →Free Open Graph Tag Generator
Create Open Graph and Twitter Card tags so your links look great when shared.
Use Tool →How It Works
How to use this free HowTo schema generator
No account needed, no sign-up, completely free. Fill in your guide details, and valid JSON-LD structured data builds live, ready to copy into your page.
Enter your how-to basics
Add the name of the guide, a short description, and the total time it takes. Type the time in minutes and we convert it to the ISO 8601 duration Google expects, so 30 becomes PT30M automatically.
List supplies, tools, and steps
Add any supplies used up during the task and any reusable tools the reader needs. Then write each step in order, with a name, the instructions, and an optional image. Everything builds the markup live, with no empty fields left in.
Copy and validate
Copy the generated JSON-LD, paste it into the head of your how-to page, and confirm it with the Google Rich Results Test. No sign-up, completely free.
The Basics
What is HowTo schema, and why does it matter?
Search engines read your tutorials, but structured data tells them exactly what they are looking at: the task, the ordered steps, and what the reader needs to complete it.
The idea
Your steps, supplies, and tools → schema.org vocabulary → JSON-LD in your <head>
Result: search engines understand your guide as a process, not just text
HowTo schema is structured data that describes a task and the ordered steps to complete it, using the shared schema.org vocabulary. Instead of hoping Google infers the sequence and the requirements from your HTML, you state them explicitly in a format built for machines to read.
The recommended format is JSON-LD: a small block of JSON placed in the head of the page. It lives separately from your visible content, so it is easy to add without touching your design. Each step becomes a HowToStep, supplies become HowToSupply items, and tools become HowToTool items, so the whole process is spelled out.
Structured data does not guarantee rankings or rich results, but it makes your instructions unambiguous to search engines and to the AI assistants that increasingly summarize the web. Clear data means your work is easier to represent, and cite, correctly.
The Fields
The fields this generator creates
The properties that make up HowTo markup. Here is what each one describes and when to use it.
| Field | What it describes | When to use | Role |
|---|---|---|---|
| name | The title of the how-to. Required for valid HowTo markup and should match the visible page title. | Every guide you mark up. | Required |
| step | The ordered list of instructions. Each HowToStep carries a name, the instruction text, and an optional image. | Every guide. At least one step is needed. | Core |
| supply | Consumable materials the reader uses up during the task, listed as HowToSupply items. | Guides that consume materials. | Optional |
| tool | Reusable objects the reader needs but does not use up, listed as HowToTool items. | Guides that need equipment. | Optional |
| totalTime | How long the whole task takes, written as an ISO 8601 duration such as PT30M for thirty minutes. | Time-bound tasks. | Optional |
Based on the schema.org HowTo type and Google Search structured data documentation, 2026.
What It Can Unlock
What HowTo schema can do for you
Structured data helps machines understand your guide and can make it eligible for search features. Eligibility is never guaranteed, but the groundwork matters.
Step-by-step clarity
HowTo markup states each step, its order, and its instructions explicitly, so search engines read your process as structured data rather than guessing from the page.
Voice-assistant answers
Clear, ordered steps are easier for voice assistants to read back one step at a time, which helps your guide surface in hands-free and smart-display contexts.
AI citation clarity
Structured how-to data makes your instructions easier for AI answer engines to attribute and cite accurately when they summarize a task.
Richer understanding
Supplies, tools, and total time give search engines and assistants a fuller picture of what the task involves before someone starts it.
Per-step images
Adding an image URL to a step gives search engines a clear visual to associate with that specific instruction.
Time and effort signals
A total time value sets expectations up front, which helps your guide match searches where people want a quick task or a weekend project.
Avoid These
Six HowTo schema mistakes that cause problems
Structured data helps only when it is accurate and valid. Steer clear of these common errors.
Marking up steps that are not on the page
HowTo markup must describe real, visible steps that appear on the page. Do not add steps to the schema that a reader cannot see in the content.
Mark up only on-page stepsSteps out of order
HowTo steps are ordered. List them in the exact sequence a reader should follow, top to bottom, so the numbering in your markup matches the real process.
Keep steps in orderCramming actions into one step
A step that bundles several actions is hard to follow and hard to represent. Split it so each step covers one clear action.
One action per stepUsing HowTo for a recipe
Cooking and baking instructions belong in Recipe markup, which has its own ingredient and nutrition fields. HowTo is for non-recipe tasks.
Use Recipe for recipesConfusing supplies with tools
Supplies are consumed during the task, tools are reused. Mixing them up gives search engines an inaccurate picture of what the reader needs.
Split supplies and toolsNever validating
Always run your markup through the Rich Results Test and Schema.org Validator. A single syntax slip can invalidate the whole block.
Validate before you shipGet More From It
6 tips for effective how-to markup
Practical ways to make your schema work harder. All CommonNinja widgets mentioned are free to start.
Match the steps to your page
Every step in your markup should mirror a step a reader can actually see on the page. Keep the wording close so the schema and the visible content stay in sync.
Write one clear action per step
Short, single-action steps are easier for readers, voice assistants, and validators to follow. If a step has an "and" in it, consider splitting it.
Add a total time when it helps
A total time sets expectations and helps your guide match searches for quick tasks or bigger projects. Enter it in minutes and we handle the ISO 8601 formatting.
Make the steps visual on the page too
Schema describes your process; make the on-page version just as clear. Image hotspots and before-and-after sliders help readers follow along at each stage.
Try the Image Hotspot widget →Pair it with site-wide schema
HowTo markup describes one guide. Your Organization and WebSite schema describes the whole brand. Use both. Our free Website Schema Generator builds the site-wide part.
Try the Website Schema Generator →Validate after every change
Re-run the Rich Results Test whenever you edit your markup or restructure the guide. It catches errors before Google does.
Glossary
Key HowTo schema fields
A quick reference for the properties behind how-to markup.
| Field | Definition | Example | When It Matters |
|---|---|---|---|
| name | The title of the how-to guide. Required, and it should match the visible page title. | How to Tie a Tie | Every guide you mark up |
| step | A single HowToStep with a name, the instruction text, and an optional image. Steps are ordered. | HowToStep + text | Every guide |
| supply | A HowToSupply: a consumable material the reader uses up during the task. | HowToSupply + name | Tasks that consume materials |
| tool | A HowToTool: a reusable object the reader needs but does not use up. | HowToTool + name | Tasks that need equipment |
| totalTime | How long the whole task takes, as an ISO 8601 duration. Thirty minutes is written PT30M. | PT30M | Time-bound tasks |
From the Blog
Further reading on guides and structured data
Go deeper on writing tutorials and making your content easier for search engines to understand.
How to Reflect Your Brand Identity in Your Website Design
In this article, we are going to explain how to reflect your brand identity in your website design. ...
Read article →How To Build a Real Estate Website in 2026
In this article, we are going to explain how to create a Real Estate website. ...
Read article →Effective Website Navigation: A Comprehensive Guide
In this comprehensive guide, we will delve into the intricacies of effective website navigation. ...
Read article →How To Create a Photography Website in 2026
In this article, we are going to explain how to create a Photography website. ...
Read article →How To Build an Event Website in 2026
In this article, we are going to explain how to create an Event website. ...
Read article →Building a Compelling ‘About Us’ Page: A Comprehensive Guide
In this article, we are going to explain how to build a compelling About Us page. ...
Read article →