SchemaForAI
Ad

Free HowTo Schema Generator for AI Search

Generate JSON-LD HowTo schema with step-by-step instructions, supplies, and tools. Optimized for ChatGPT tutorials, Google AI Overviews, and voice assistants. No sign-up.

HowTo Details

HowTo Schema

Clear title describing what the user will accomplish.

Lead with 'How to' — AI engines pattern-match on this phrasing when matching user queries.

Minimum 50 characters.

0 / 500

Tell the AI what the reader will have accomplished by step N. This is what gets surfaced as the snippet.

ISO 8601 duration. PT15M = 15 min, PT1H30M = 1h 30m, P1D = 1 day.

Total time is a high-value filter signal — 'how to fix a leaking faucet in under 30 minutes' queries filter by this.

Numeric cost estimate (optional).

Supplies Needed

Consumables/materials the user needs (optional but recommended).

0 items

Voice assistants read supplies before starting — listing them up front improves AI voice-result matching.

Tools Needed

Reusable tools or equipment (optional).

0 items

Steps*

At least 2 steps. Each step needs a clear action.

2 items

Numbered steps are the core unit AI engines surface in 'step-by-step' queries. Keep each step one discrete action.

Step 1

Short, imperative headline.

Minimum 20 characters. Be precise about quantities and timing.

0 / 1000

Optional photo for this step.

Step 2

Short, imperative headline.

Minimum 20 characters. Be precise about quantities and timing.

0 / 1000

Optional photo for this step.

JSON-LD
{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to …",
  "description": "Summary of what you will do…",
  "totalTime": "PT15M",
  "step": [
    {
      "@type": "HowToStep",
      "position": 1,
      "name": "First step name",
      "text": "Detailed instructions…"
    }
  ]
}

AI Readiness Score

Get a 0–100 score showing how likely AI search engines are to parse and cite content from your page.

How to use this code:

  1. Copy the JSON-LD code above
  2. Paste inside <script type="application/ld+json">
  3. Add the script tag to your tutorial page <head>
  4. Validate with Google Rich Results Test ↗
AI Simulator

See how ChatGPT answers — with and without your schema

Side-by-side comparison of what an AI assistant would return for a typical howto query, with vs. without the structured data you generated above.

3 of 3 remaining today

Sample user query

How do I do this step by step?

Without Schema
Generic answer

Click Simulate to see the AI response without schema.

With Schema
Detailed citation

Click Simulate to see the AI response with schema.

Install Guide

How to install this schema on your site

Pick your platform. Every step includes a copy-paste-ready code block where it applies.

  1. 1

    Install and activate a schema plugin: "Rank Math SEO", "Yoast SEO Premium", or "Schema Pro". For straight JSON-LD injection without a full SEO plugin, "WPCode" (formerly Insert Headers and Footers) is the simplest option.

  2. 2

    In Rank Math: go to the post edit screen → Rank Math sidebar → Schema tab → Schema Builder → paste your JSON-LD. In Yoast Premium: the Schema tab auto-generates standard types; use the Custom Schema plugin add-on to inject custom types.

  3. 3

    For WPCode: Code Snippets → Add Snippet → Custom Code (HTML/PHP) → paste the full <script type='application/ld+json'> tag. Set Location to 'Site Wide Header' or 'Specific Post/Page' depending on scope.

    html
    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "FAQPage",
      "mainEntity": [ /* your Q&A pairs */ ]
    }
    </script>
  4. 4

    Publish the post. Open the live URL, view source, confirm the <script type="application/ld+json"> tag appears in the <head>.

  5. 5

    Validate at search.google.com/test/rich-results.

What is HowTo Schema Markup?

HowTo is the Schema.org type for step-by-step instructional content. It decomposes a procedure into structured sub-entities an AI engine can reason about independently: the overall name and description, an estimated total time, lists of required supplies and tools, and — most importantly — an ordered array of HowToStep objects, each with its own name, text, and optional image.

This structured decomposition is what makes HowTo the most valuable schema type for voice assistants and AI tutorial surfaces. When Alexa or Google Assistant reads a HowTo, it doesn't parse the text — it reads step 1, speaks it, waits for "next," reads step 2. When ChatGPT is asked "how do I replace a bathroom faucet," it doesn't summarize a prose article — it reconstructs the step list directly from HowTo schema on the source page.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Brew Pour-Over Coffee",
  "totalTime": "PT4M",
  "supply": [
    { "@type": "HowToSupply", "name": "20g coffee beans" }
  ],
  "tool": [
    { "@type": "HowToTool", "name": "Gooseneck kettle" }
  ],
  "step": [
    {
      "@type": "HowToStep",
      "position": 1,
      "name": "Heat the water",
      "text": "Boil 300g of filtered water and let it rest 30s off boil."
    }
  ]
}
</script>
Ad

Why HowTo Schema Matters for AI Search

Tutorials are a category where AI search has massively disrupted traditional blue-links SEO. Users who once typed "how to change a car battery" into Google and clicked the top article now ask ChatGPT and get a synthesized step-by-step response — often without clicking through. The content author's leverage in that world is not ranking first on Google; it's being the source the AI cites. HowTo schema is the single strongest signal available for that outcome.

AI engines specifically reward:

  • Discretely parseable steps: Each HowToStep is an addressable unit. AI engines can quote step 3 without the rest of the article — this is how they assemble responses to follow-up questions like "wait, can you repeat step 3?"
  • Time-filtered eligibility: totalTime lets AI engines filter tutorials for time-scoped queries ("a 10-minute dinner," "a quick fix"). Tutorials without it aren't excluded — they just can't qualify for time-specific rankings.
  • Pre-execution validation via supply/tool: Voice assistants read supplies and tools before starting. Users confirm they have everything, then proceed. Tutorials with listed supplies convert into actual voice-guided walkthroughs; ones without get dropped at "do you have everything?"
  • Step images for vision-enabled AI: GPT-4V, Gemini, and other vision-capable systems use step images to verify content matches the description. They also display these images inline in AI tutorial responses, which is a strong driver of click-through back to your site.
  • Ordered position property: Explicit position values on each HowToStep prevent order-sensitive procedures from being reordered when AI engines deduplicate or merge with other sources.

The compounding advantage for tutorial publishers is significant: a site with consistent HowTo schema across its tutorial library becomes the default source for an entire procedural category. AI engines learn to trust it, and that trust transfers to new tutorials in the same series.

HowTo Schema Best Practices

One action per step

If a step contains two verbs that could be executed at different times ("preheat the oven AND chop the vegetables"), split them.

Include precise quantities and times

"Bake 25 minutes at 375°F" not "bake until done." AI engines quote exact numbers more readily than vague instructions.

Use imperative step names

"Heat the water," not "You will now heat the water." Imperative names are what voice assistants read aloud.

Set totalTime in ISO 8601

PT15M, PT1H30M, P1D. Voice filtering depends on this being exact and parseable.

List supplies with quantities

"20g coffee beans," not just "coffee beans." Quantified supply lists are what voice assistants use to confirm readiness.

Add step images for spatial steps

Assembly, alignment, identification — any step where "what does this look like" matters benefits from an image.

Keep each step text focused

20–250 words. Short steps feel incomplete; long steps usually contain hidden sub-steps.

Don't duplicate the same text in FAQ

If you also have FAQ schema on the page, answer different questions — don't re-state your HowTo as an FAQ.

How to Install HowTo Schema

WordPress

  1. 1Generate JSON-LD with SchemaForAI and copy it.
  2. 2Use WPCode or Rank Math's custom schema feature, scoped to the specific tutorial post.
  3. 3Alternatively, install a block-editor HowTo plugin that generates schema from visual step blocks.
  4. 4Make sure image URLs in step entries point to absolute URLs, not relative paths.
  5. 5Validate each published tutorial via Rich Results Test.

Next.js / React

  1. 1Define tutorials as structured data files (JSON or MDX frontmatter).
  2. 2At build time, transform each tutorial's steps into HowToStep objects and emit JSON-LD.
  3. 3Use dangerouslySetInnerHTML with </script> replacement for safety.
  4. 4For long tutorials, consider splitting into multiple HowTos if logical stopping points exist.
  5. 5Add an automated CI check that validates each page with the Rich Results Test API.

Plain HTML

  1. 1Copy the JSON-LD from this tool.
  2. 2Paste inside a <script type="application/ld+json"> tag in the <head>.
  3. 3Ensure step image URLs are absolute (with full protocol and domain).
  4. 4Avoid linking to blog-service-generated image URLs that expire (e.g. some social-media CDNs).
  5. 5Test on the Google Rich Results tool and iterate.

Frequently Asked Questions

Is HowTo schema still eligible for Google rich results?+
Google announced in 2023 that HowTo rich results would be deprecated on desktop and restricted on mobile. That change reduced the visible rich-snippet footprint, but HowTo schema is still heavily used by Google AI Overviews, voice assistants, and third-party AI engines. The deprecation applied to one narrow Google surface; the schema itself is still valid, still parsed, and still weighted by AI systems as a strong signal that the content is structured step-by-step instructions. So while you shouldn't add HowTo schema with the expectation of a Google rich result in 2026, you should still add it because ChatGPT, Perplexity, Alexa, Google Assistant, and Google's own AI Overviews all use it.
What format does totalTime use?+
totalTime uses ISO 8601 duration format: a P prefix followed by time components. PT15M means 15 minutes. PT1H30M means 1 hour 30 minutes. P1D means 1 day. PT8H means 8 hours. The P is required; everything else is optional. The format is unintuitive but strictly validated — PT1h30m (lowercase) or 1h30m (no prefix) will fail. Voice assistants specifically use totalTime to filter query results: a user asking "a quick 15-minute dinner recipe" gets filtered to HowTos under PT15M. Getting this field right is the difference between appearing and not appearing in time-scoped queries.
How detailed should each step be?+
Each step should capture one discrete action a user can perform in one sitting. "Brew the coffee" is too vague; "Pour 200 grams of 205°F water in a slow circle over the grounds" is about right. AI engines quote steps verbatim in their responses, so the reader of your step should be able to execute it without referring back to the prose on your page. Keep step text between 20 and 250 words. Under 20 words usually means you've combined what should be two steps; over 250 words usually means the step is actually two or three steps masquerading as one.
Do I need to include supply and tool?+
They're optional, but voice assistants lean on them heavily. A user asking "what do I need to make sourdough" gets a better answer from a HowTo with listed supplies than from one without — because the AI can extract the list directly from schema rather than parsing it from prose. Supply is for consumables (20g coffee, 2 eggs, a screw); tool is for reusable equipment (a kettle, a screwdriver, a skillet). Listing them is the difference between an AI assistant confidently answering the pre-cooking "do I have everything" question and hedging.
Should I include images for each step?+
Yes, when they add value — and always when the step involves spatial reasoning (assembling something, identifying a part, navigating a UI). AI engines with vision capabilities (GPT-4V, Gemini) use step images to verify the instructions are correct. They can also be surfaced directly in AI-generated tutorial responses, which makes your content much more clickable. Use consistent aspect ratios across steps (3:2 or 16:9 works best) and host them on the same domain as the HowTo page for crawler reliability.
What's the minimum number of steps?+
The Schema.org spec doesn't enforce a minimum, but Google's historical HowTo rich result documentation and most AI engines expect at least 2 steps. If you have only one step, it's probably not a HowTo — use Article schema instead. Most genuinely helpful HowTos have 4–8 steps; tutorials under 4 steps often feel thin and perform worse in AI citations because there isn't enough content for the AI to synthesize a complete response. Over 15 steps usually means the procedure should be split into multiple HowTos with sub-topics.
Can I add video to HowTo?+
Yes, and you should if you have one. Add a VideoObject as a nested property in your HowTo. Each step can also have its own video field pointing to a timestamped section of the full video. AI engines use the video/step linkage to deep-link users to specific moments — the user asks "how do I fix step 3" and the AI returns a video cued to the relevant timestamp. For tutorials where the video is the primary medium, mark up the video as VideoObject with HowToSection entities embedded in its description.
Should HowTo schema and FAQ schema coexist on the same page?+
Yes, and they often should. A great tutorial page has HowTo schema for the steps and FAQ schema for common questions people ask about the procedure. Both appear in different AI query types: "how do I make X" triggers HowTo retrieval, while "what if X doesn't work" triggers FAQ retrieval. Pages that mark up both capture both traffic types. Just don't duplicate content — don't put the same text in a HowToStep and a Question/Answer.

Related Schema Generators

Ad