7 min read · AI Visibility · Last updated July 2026
Quick answer: HowTo schema marks up step-by-step content with structured steps, tools, supplies, and time estimates in JSON-LD. It enables How-to rich results in Google, helps AI systems extract procedure steps cleanly, and is particularly effective for voice search and AI Mode responses to process queries.
Introduction
How-to content is one of the highest-citation content types in AI responses. When someone asks ChatGPT “how do I set up Google Business Profile” or asks Gemini “how to implement LocalBusiness schema,” the AI synthesizes a step-by-step response from available sources.
The sources that provide the cleanest, most extractable steps get cited. HowTo schema makes your steps explicitly machine-readable — not dependent on AI inference from prose, but directly accessible as structured data.
What you’ll learn:
– The complete HowTo schema property set
– How to structure individual steps with HowToStep
– Tools, supplies, and time estimate properties
– HowTo schema for voice search and AI Mode
– Complete JSON-LD template and live generator
Table of Contents
- When to Use HowTo Schema
- The HowTo Schema Structure
- HowToStep Properties
- Tools, Supplies, and Time
- HowTo for AI Extraction
- Implementation Best Practices
- HowTo Schema Generator
- Frequently Asked Questions
When to Use HowTo Schema
HowTo schema is appropriate for content that describes a sequential process to achieve a specific goal:
Well-suited for HowTo schema:
– Technical tutorials (“How to install WordPress”)
– DIY and crafting guides (“How to build a raised garden bed”)
– Cooking and recipe-adjacent content (“How to make cold brew coffee”)
– Business process guides (“How to write a client brief”)
– Configuration and setup guides (“How to configure caching in WordPress”)
– Marketing and SEO processes (“How to conduct a technical SEO audit”)
Not well-suited for HowTo schema:
– Listicles without sequential steps
– Opinion and analysis content
– General category pages
– Content where steps are not sequential (can be done in any order)
The core test: if following the steps out of order would produce a different (or failed) result, the content is sequential enough for HowTo schema.
The HowTo Schema Structure
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Implement FAQPage Schema in WordPress",
"description": "Step-by-step guide to adding FAQPage JSON-LD schema to WordPress pages to enable FAQ rich results and improve AI citation.",
"image": {
"@type": "ImageObject",
"url": "https://ignitednepal.com/images/faqpage-schema-wordpress.jpg"
},
"totalTime": "PT30M",
"estimatedCost": {
"@type": "MonetaryAmount",
"currency": "AUD",
"value": "0"
},
"supply": [
{"@type": "HowToSupply", "name": "WordPress admin access"},
{"@type": "HowToSupply", "name": "Text editor or schema plugin"}
],
"tool": [
{"@type": "HowToTool", "name": "Google Rich Results Test"},
{"@type": "HowToTool", "name": "Schema Markup Validator"}
],
"step": []
}
Key properties:
– name — the title of the how-to guide
– description — summary of what the guide achieves
– totalTime — ISO 8601 duration format (PT30M = 30 minutes, PT2H = 2 hours)
– estimatedCost — total cost for the process (use “0” for free)
– supply — materials or accounts needed
– tool — tools or software used
– step — array of HowToStep objects (see below)
HowToStep Properties
Each step is a HowToStep object:
{
"@type": "HowToStep",
"name": "Generate your FAQPage JSON-LD code",
"text": "Open the FAQPage schema generator at ignitednepal.com/tools/faqpage-generator. Enter your questions and answers. Click Generate Schema to produce the JSON-LD code block.",
"image": "https://ignitednepal.com/images/step1-generator.jpg",
"url": "https://ignitednepal.com/blog/faqpage-schema-guide/#step-1"
}
HowToStep properties:
– name — short step title (appears in rich result heading)
– text — full step description (2-4 sentences)
– image — step screenshot or illustration (highly recommended for rich results)
– url — anchor link to the step on the page
For grouped steps (using sections), wrap steps in HowToSection objects:
{
"@type": "HowToSection",
"name": "Phase 1: Preparation",
"step": [
{"@type": "HowToStep", "name": "Step 1", "text": "..."},
{"@type": "HowToStep", "name": "Step 2", "text": "..."}
]
}
Tools, Supplies, and Time
ISO 8601 Duration format for totalTime:
– PT15M = 15 minutes
– PT1H = 1 hour
– PT1H30M = 1 hour 30 minutes
– P1D = 1 day
– P1W = 1 week
For multi-stage processes, you can also use prepTime and performTime:
"prepTime": "PT10M",
"performTime": "PT20M",
"totalTime": "PT30M"
Supply vs. Tool distinction:
– HowToSupply = things that are consumed or required as materials
– HowToTool = instruments or software used in the process
For digital guides: accounts and access credentials are typically supply; software, platforms, and validators are typically tool.
HowTo for AI Extraction
HowTo schema is particularly valuable for AI systems because it transforms prose instructions into structured step data.
Without HowTo schema, an AI reading your guide must:
1. Parse the prose to identify where steps begin and end
2. Infer the step count and sequence
3. Extract step text with potential errors or merges
With HowTo schema, the AI reads:
1. Step 1: [name, text, image URL]
2. Step 2: [name, text, image URL]
3. Step N: …
This eliminates extraction error and makes your guide the cleanest source for the query. When Perplexity or Gemini answers “how to do X,” it preferentially cites sources with extractable structured steps.
Voice search is particularly HowTo-dependent. Google Assistant and Siri extract steps from HowTo schema for step-by-step voice responses. If your content targets “how to” queries and you have a significant mobile/voice audience, HowTo schema is a direct voice search optimization.
Implementation Best Practices
Match schema steps to on-page steps: Every step in your JSON-LD should correspond to a visible step on the page. Do not include schema steps without visible on-page content.
Use step images: Images in HowToStep significantly increase rich result display quality and click-through rates. Even simple annotated screenshots qualify.
Keep step text concise: 2-4 sentences per step. The text property appears in rich results and voice responses. Long step descriptions do not display fully.
Add anchor links: Use url in each step to link to the anchor on the page (e.g., #step-3). This allows rich results to deep-link to specific steps.
Validate before publishing: Use Google’s Rich Results Test and Schema Markup Validator. HowTo rich results require at least 2 steps.
HowTo Schema Generator
HowTo Schema Generator
Add your steps and generate JSON-LD
Frequently Asked Questions
Q: How many steps are required for HowTo rich results?
A: Google requires at least 2 steps for HowTo rich results eligibility. There is no stated maximum, but very long guides (20+ steps) may benefit from HowToSection grouping.
Q: Can I use HowTo schema alongside Article schema on the same page?
A: Yes. A how-to guide can have both HowTo schema (for the steps) and Article schema (for the content type and author). Include them as separate JSON-LD blocks or use nested schemas.
Q: Does HowTo schema work for recipe content?
A: For food recipes specifically, use Recipe schema instead — it has dedicated properties (ingredients, nutrition, cookTime) that HowTo does not. For non-food step-by-step processes, HowTo is the correct type.
Conclusion
HowTo schema is a high-impact, underutilized structured data type that directly improves how AI systems extract and cite your step-by-step content. If your site publishes how-to guides, tutorials, or process content, implementing HowTo schema should be a top technical SEO priority.
Get AI-Ready with Ignited Nepal
We implement HowTo, FAQPage, Article, and LocalBusiness schema as part of a complete structured data audit and implementation.
→ Request an AI Visibility Audit
Written by the Ignited Nepal AI Visibility team. ignitednepal.com