How-To Schema Generator — Free JSON-LD for Tutorials

What is HowTo Schema?

HowTo is the Schema.org type for step-by-step instructional content — anything that teaches a reader to accomplish a specific task. Common applications include DIY home improvement tutorials, software setup guides, repair walkthroughs, fitness routines, craft projects, and gardening instructions. It is distinct from Recipe (cooking-specific) and Article (general editorial).

HowTo schema conveys the ordered sequence of steps, optional time estimates, materials needed, tools required, and estimated cost. Each step can include its own image, text description, and optional sub-step links. This structure lets Google, Bing, voice assistants, and AI Overviews understand procedural content far more effectively than plain prose.

Why HowTo Schema Still Matters in 2026

• AI Overview citations: Google's generative search experiences increasingly pull from structured HowTo data when answering "how do I..." queries. Pages with valid schema are easier to extract and more likely to be cited.
• Voice search and assistants: Google Assistant, Bing Chat, and Siri use HowTo schema to deliver step-by-step audio responses. Without schema, voice search ignores instructional content.
• Mobile rich results: While desktop HowTo rich results were deprecated in late 2023, mobile still shows expandable step cards for some categories (especially home improvement and consumer electronics).
• Improved click-through: Even without rich results, search engines understand your page is instructional, which improves match for action-intent queries ("how to remove" / "how to install" / "how to fix").
• Schema as a structural discipline: Building HowTo schema forces you to clarify your steps. Pages with cleaner step structure perform better in SEO regardless of rich result status.

HowTo Schema Properties Explained

Required Properties

• name: The task being taught. Should match your H1. Format: "How to [verb] [object]" — e.g., "How to Install a Faucet" or "How to Format a USB Drive".
• step: An ordered array of HowToStep objects. Each must have at least a name or text. Order matters — Google uses array position as the step sequence.

Strongly Recommended Properties

• description: A one-sentence summary of the goal — what the reader will accomplish.
• image: Primary cover image for the tutorial (1200px+ wide).
• totalTime: Total time in ISO 8601 duration format (e.g., PT45M = 45 minutes, PT2H30M = 2 hours 30 minutes).
• estimatedCost: Nested MonetaryAmount with currency and value. Critical for DIY/repair content.
• supply: Array of HowToSupply objects — consumable materials needed.
• tool: Array of HowToTool objects — reusable tools needed.

Per-Step Properties

• name: Short step title (e.g., "Disconnect the water supply").
• text: Detailed instruction for the step.
• image: Step-specific image URL (optional but increases rich result eligibility).
• url: Anchor link to the step on your page (e.g., https://example.com/install#step-3).

Step-by-Step Implementation

Step 1: Verify Your Content Is Instructional

HowTo schema is for content that teaches a procedure with discrete ordered steps. A recipe is not HowTo — use Recipe. A product comparison is not HowTo — use Article. A FAQ section is not HowTo — use FAQPage. Only use HowTo for true step-by-step tutorials.

Step 2: Restructure Your Content Into Atomic Steps

If your tutorial is currently written as flowing prose, break it into discrete steps before generating schema. Each step should be one logical action a reader can complete and then move on from. If a step has more than 3-4 sentences, consider splitting it.

Step 3: Generate the JSON-LD

Use the generator above. Fill in the goal name, optional totalTime in ISO 8601 format (most common: PT15M, PT30M, PT1H, PT2H), and add each step with a short name and detailed text. Step images are optional but highly recommended.

Step 4: Match the Schema to Visible Page Content

Google requires HowTo schema to match what is visibly rendered on the page. Do not include steps in schema that are not shown to users. Do not embellish times or costs — both must be accurate. Mismatches can trigger structured data warnings.

Step 5: Add Anchor IDs to Step Headings

For best UX, give each step heading an anchor ID like id="step-1". The HowTo schema URL pointing to #step-1 creates jumpable deep links from rich results.

HowTo Schema Best Practices

• Use ISO 8601 durations: PT30M not "30 minutes", PT1H30M not "1.5 hours".
• For estimated cost, use the currency code (USD, EUR) and a numeric string value: "value{"""}: "45.00{"""}.
• Keep step name short (3-7 words). Save detail for the text field.
• List supply (consumables: bolts, glue, paint) and tool (reusable: drill, hammer) separately.
• Order steps logically — Google trusts your array order and renders accordingly.
• Add step images when possible. Each image should clearly show that specific step's action.
• Make sure step text is descriptive enough to stand alone (a user reading just one step should still understand the action).

Common Mistakes to Avoid

• Adding HowTo schema to recipe pages instead of Recipe schema.
• Using free-text time formats ("about 30 minutes") instead of ISO 8601.
• Including steps in schema that don't appear on the rendered page.
• Combining multiple unrelated tasks under one HowTo (e.g., "How to install AND maintain"). Split into separate guides.
• Marking up commercial content as HowTo when it's actually promotional ("How to choose our product") — Google considers this a policy violation.
• Forgetting estimatedCost on DIY/repair content where cost is a primary search intent.
• Skipping per-step images on visual tasks (assembly, repair, crafts).

Frequently Asked Questions

Related Schema Generators

• Recipe Schema Generator — for cooking-specific instructional content with ingredients and nutrition.
• FAQ Schema Generator — for the Q&A section often paired with tutorials.
• Article Schema Generator — for general editorial content that isn't strictly procedural.