HowTo is a Schema.org type used to markup instructional content that describes a sequence of steps to achieve a specific task, qualifying the content for a rich visual result that shows the steps directly in search. It communicates the procedural structure of a guide—including its supply list, tool requirements, and totalTime—to search engines via JSON-LD.
Glossary
HowTo
A Schema.org type used to markup instructional content that describes a sequence of steps to achieve a specific task, qualifying the content for a rich visual result that shows the steps directly in search.
SCHEMA MARKUP ENGINEERING
What is HowTo?
A structured data vocabulary for defining instructional step-by-step content to qualify for rich visual results in search engine results pages.
Implementing HowTo schema requires nesting HowToStep or HowToSection types within the parent entity, with each step containing explicit text and optional image properties. This markup enables Google Assistant to read instructions aloud and surfaces the content in a dedicated rich result, driving higher click-through rates for DIY, recipe, and technical documentation sites.
STRUCTURED DATA
Key Properties of HowTo Schema
The HowTo schema type relies on a specific set of properties to define instructional content for search engines. These properties structure the steps, tools, and supplies needed to complete a task, enabling rich visual results.
01
name
The title of the instructional guide. This property defines the task or project the user will complete.
- Must be a concise, descriptive string (e.g., "How to Replace a Bicycle Tire").
- This text typically appears as the main heading in the rich result.
- It is a required property for the
HowTotype.
Required
Property Status
02
step
An array of HowToStep objects that define the sequential actions required to complete the task.
- Each step must contain a
textproperty with the actual instruction. - Steps can also include
imageandvideoproperties for visual guidance. - The order of items in the array determines the displayed sequence.
Required
Property Status
03
tool
An array of HowToTool objects listing the equipment required before starting the task.
- Each tool requires a
nameproperty (e.g., "Tire lever"). - Helps search engines understand the complexity and preparation needed.
- Displayed in a distinct "Tools" section within the rich result.
Recommended
Property Status
04
supply
An array of HowToSupply objects listing the consumable materials needed for the task.
- Each supply requires a
nameproperty (e.g., "Wood glue"). - Distinct from
toolas supplies are depleted during the process. - Helps users prepare all necessary items before beginning step 1.
Recommended
Property Status
05
totalTime
The total duration required to complete the entire task, formatted as an ISO 8601 duration string.
- Example: "PT1H30M" represents 1 hour and 30 minutes.
- Provides a clear expectation for the user before they engage with the content.
- Displayed prominently in the rich result header.
Recommended
Property Status
06
description
A brief summary of the guide's objective. This text provides context beyond the title.
- Should clearly state the end goal of the instructions.
- Used by search engines to understand the scope of the content.
- Appears as supporting text in the rich result snippet.
Optional
Property Status
SCHEMA IMPLEMENTATION
Frequently Asked Questions
Clear, technical answers to the most common questions about implementing HowTo structured data for step-by-step instructional content.
HowTo is a Schema.org structured data type specifically designed to markup instructional content that achieves a specific task through a defined sequence of steps. When implemented correctly using JSON-LD, it signals to search engines like Google that your page contains a procedural guide, qualifying it for a How-to rich result—a visually enhanced search listing that displays steps, images, and estimated time directly in the SERP. The schema works by defining a HowTo object containing a list of HowToStep items, each with explicit HowToDirection text and optional HowToTip annotations. This structured representation allows search engine parsers to extract the procedural logic without relying on heuristic HTML scraping, ensuring your instructional content is machine-readable and eligible for voice assistant responses via the speakable property.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.
Enterprise searchRAGPermissions
Read more
Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.
AI agentsWorkflow automationGovernance
Read more
Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
AI integrationDecision supportModel routing
Read more
About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
LinkedIn
Limited slotsGet a Free AI Consultation
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us