Ankore
Schema · Free

How-To Schema Generator

Generate Google-ready How-To structured data with steps, time estimates, supplies, tools, and per-step images. Smart duration parsing accepts ISO 8601 or plain English.

  • No signup, no email required
  • Works entirely in your browser
  • Output you can copy and paste directly
  • Built by a working SEO team, not gated by upsells

How-To details

Supplies (consumables)

None added.

Tools (reusable)

None added.

Steps

0 valid · 2 total
Step 01
Step 02

Output

JSON-LD
// Add a name plus at least one step with non-empty fields to generate JSON-LD.
Validate
Open Rich Results Test

What it does

This tool builds HowTo schemain JSON-LD — the structured data format schema.org defines for procedural, step-by-step content. Recipes, tutorials, repair guides, setup walkthroughs, and any "how to do X" content fits this schema type.

The generator produces a complete HowTo object with the optional fields most other tools skip: per-step images, total time, supplies (consumables), tools (reusables), and proper ISO 8601 duration formatting. Smart duration parsing means you can type "30 minutes" and the tool converts it to PT30M.

Why How-To schema matters in 2026

Google deprecated the dedicated How-To rich result for most queries in 2023, similar to what happened with FAQ. Like FAQ schema, How-To markup is still worth implementing — for slightly different reasons:

  • AI Overview citations.Google's AI Overview heavily extracts from How-To structured data when answering procedural queries. A page with HowTo schema is significantly more likely to be cited as a source than a comparable page without it.
  • Voice assistant procedural queries. "Hey Google, how do I reset my router?" — voice assistants prefer pages with explicit step structure. HowTo schema is the cleanest signal for that structure.
  • Featured snippet eligibility for procedural queries. Step-format featured snippets pull primarily from pages with either explicit numbered HTML lists or HowTo schema. The schema is the more reliable extraction signal.
  • YouTube / video integration. If your How-To has an accompanying video, HowTo schema with linked VideoObject metadata helps the video appear in search alongside the article.

How to use this generator

  1. Add the name.Phrase it like a real search query — "How to add FAQ schema to a web page," not "FAQ Schema Implementation Guide."
  2. Add a description. One sentence describing the outcome. Optional but recommended.
  3. Set total time.Type "30 minutes", "1 hour 30 min", or use the ISO 8601 format directly (PT1H30M). The tool converts shorthand to ISO automatically.
  4. Add supplies and tools. Supplies are consumables (ingredients, materials); tools are reusables (a wrench, a code editor, a browser). Both are optional.
  5. Add steps. Each step needs a name (short label) and text (a sentence or two of detail). Per-step image URLs are optional but improve AI Overview extraction.
  6. Copy the JSON-LDand paste into the <head> of your page. Validate with the Rich Results Test link in the output panel.

How-To schema best practices

  • The schema must match visible page content. Same rule as FAQ. Steps in your JSON-LD must appear visibly on the rendered page. Hidden steps are a documented Google guideline violation.
  • Each step needs a name and text.Schema.org allows steps with just text, but Google's guidelines strongly prefer a name (short label) plus text (the instruction). The validator may still pass, but extraction performance suffers without both.
  • Step count: 3 to 12. Below 3 and the content is not really a how-to. Above 12 and AI Overview / voice extraction quality degrades — split into multiple HowTo pages if the procedure is genuinely longer.
  • Use per-step images. They are optional in schema.org but the highest-leverage optional field for extraction quality. If you have screenshots or photos, link them per step.
  • Total time matters for voice / AI extraction. Voice assistants will tell users "this takes about 30 minutes" based on totalTime. Set it accurately.
  • Use ISO 8601 duration format. PT5M = 5 minutes, PT1H = 1 hour, PT1H30M = 1 hour 30 minutes. This tool accepts plain English and converts.
  • One HowTo per page. Same constraint as FAQ. Multiple HowTo objects on one URL fails validation.
  • Supplies vs Tools is a meaningful distinction. Consumables (gone after use) are supplies; reusables (still there after) are tools. Recipe ingredients are supplies; the mixing bowl is a tool. AI Overview surfaces these distinctly in some cooking-related queries.

Common How-To schema mistakes

  • Using HowTo for non-procedural content. HowTo is specifically for step-by-step procedures with a defined outcome. A list of tips, a comparison post, or a general explainer is not a HowTo. Use Article schema instead.
  • HowTo on product setup pages without actual steps. "Plug in. Done." is not a how-to. Google's extractors detect minimal-content HowTo as low-quality and ignore it.
  • Free-text duration formats. totalTime: "about half an hour" fails validation. Must be ISO 8601 (PT30M). This tool converts plain English for you.
  • Nested HowTo inside Article. Pick one. If the page is a tutorial article, Article schema is sometimes a better fit than HowTo. If the page is purely procedural with minimal narrative, HowTo wins.
  • Promotional language in steps. "Step 3: visit our website to see the best link building agency in 2026!" — same demotion pattern as FAQ. Keep steps factual.
  • Missing image references for visual steps. If your page shows a screenshot for each step but the schema has no image property per step, you are leaving extraction performance on the table.

How to validate your How-To schema

  1. Google Rich Results Test. The authoritative check. Confirms Google can parse the schema and shows any structural errors.
  2. Schema.org validator. Stricter on schema.org spec compliance, less Google-specific.
  3. Search Console Enhancements report.After re-crawl, the "HowTo" entry shows valid, warning, and error counts. Fix any errors that show up.

Frequently asked questions

Is HowTo schema deprecated?

The dedicated How-To rich result was deprecated for most queries in 2023, similar to FAQ. The HowTo schema type is still officially supported and parsed by Google for AI Overview, voice assistants, and long-tail featured snippet extraction. It is still worth implementing.

What kinds of content should use HowTo?

Any content with a defined procedural outcome — recipes, repair guides, setup walkthroughs, tutorials, configuration steps, art techniques, troubleshooting flows. If the user can perform the steps and reach a measurable end state, HowTo fits.

How is HowTo different from Article schema?

HowTo is procedural — it explicitly marks steps with a defined output. Article is for general editorial content. A blog post 'How I built my SaaS' is Article (a story); a blog post 'How to set up Tailwind in 5 steps' is HowTo (a procedure). When in doubt, ask: can the reader perform the steps and complete a task? Yes = HowTo.

Do per-step images help?

Yes, materially. Per-step image URLs are the highest-leverage optional field for AI Overview and visual SERP extraction. If your visible page shows step images, link them in the schema.

What's the right number of steps?

Three to twelve. Below three, it is not really a procedure. Above twelve, extraction performance drops and the content is usually better split into multiple HowTo pages or restructured as an Article with HowTo subsections.

Can I include code blocks in step text?

Yes, as plain text inside the step. Schema.org accepts arbitrary content in the text field. Avoid HTML markup — when AI Overview extracts the step, the markup gets stripped and may garble code snippets. Plain text reads back cleanly.

What does the totalTime field actually do?

It tells voice assistants and AI extractors roughly how long the procedure takes — they will surface this to users as 'this takes about 30 minutes.' Set it accurately. The format is ISO 8601 duration (PT30M for 30 minutes); this tool converts plain English for you.

Will this tool log my data?

No. Everything runs in your browser. The fields you fill never leave your device. There is no server endpoint and nothing to log.