AEO · Answer Engine Optimisationintermediate3 min read

What is How-To Schema?

How-To schema is a structured data type (JSON-LD) that marks up step-by-step instructional content so Google can display it as a rich result — showing numbered steps directly in the SERP, sometimes with images and time estimates. It's one of the most visible rich result types, significantly expanding your SERP real estate for tutorial and instructional queries. It's also a strong signal to AI systems that your content contains actionable, structured procedural knowledge.

Fact-checked against 3 sourcesLast updated 8 June 2026
Key Takeaways
  • How-To schema works best for genuine step-by-step processes — don't force it onto content that isn't truly instructional.
  • Include estimated time (totalTime), cost, and supply/tool lists when relevant — Google displays these in the rich result.
  • Each step should have a clear name and description — these become the visible step titles in the SERP.
  • How-To rich results appear most on mobile in a carousel-style format — optimise step images for mobile display.
  • AI assistants like Google Assistant use How-To schema to guide users through tasks verbally — a direct AEO win.

How How-To Schema Works

How-To schema uses the HowTo type from Schema.org. The minimum viable implementation: the HowTo container with a name (the task title), totalTime (how long it takes), and an array of HowToStep objects — each with a name and text.

Optional but valuable: image (a screenshot or photo for each step), supply (list of materials needed), tool (list of tools required), and estimatedCost.

Google displays these as an expandable step list in search results, usually with the step names visible and the descriptions expandable. On mobile, it often appears as a carousel of steps with navigation.

Implementing How-To Schema in Next.js

Add a <script type='application/ld+json'> tag in your page head with the HowTo JSON structure. For a tutorial page with 5 steps:

{ "@context": "https://schema.org", "@type": "HowTo", "name": "How to Set Up a robots.txt File", "totalTime": "PT10M", "step": [ { "@type": "HowToStep", "name": "Create the file", "text": "Create a plain text file named robots.txt at your site root" }, ... ] }

Generate this dynamically if your CMS stores steps as structured data. Validate with Google's Rich Results Test before deploying.

Stay sharp

Most guides are already outdated.

One email a week. The search stuff that actually matters — what shifted, what died, and what to do about it.

Subscribe free →
How-To SchemaAEO

A structured data markup type (Schema.org HowTo) implemented via JSON-LD that communicates step-by-step instructional content to search engines and AI systems, enabling rich result displays in SERPs with numbered steps, images, and time estimates.

87%
of How-To rich results appear on mobile SERPs
~3×
more SERP real estate vs. standard blue links
TOP 3
rich result type for visibility gains per Google Search Central
PT format
ISO 8601 duration required for totalTime (e.g. PT10M = 10 minutes)
✓ DO

Write each HowToStep 'name' as a concise action phrase (e.g., 'Install the dependency')

Include a unique 'image' property per step — Google can render step-level screenshots in rich results

Use ISO 8601 duration format for 'totalTime' (PT15M, PT1H30M)

Add 'supply' and 'tool' arrays when your tutorial genuinely requires specific materials or software

Validate with Google's Rich Results Test after every schema change before deploying to production

✗ DON'T

Don't mark up content as How-To if the page doesn't actually contain the full step-by-step instructions

Don't use How-To schema on product or service pages — Google will reject it as spam

Don't leave 'text' fields vague or identical to 'name' — each should add meaningful detail

Don't nest HowToSection inside HowToStep incorrectly — sections group steps, not the reverse

Don't omit 'name' at the top-level HowTo object — it is a required property for eligibility

HOW-TO SCHEMA IMPLEMENTATION CHECKLIST
0/8 complete
HowTo '@type' and '@context' set to https://schema.org
'name' property reflects the exact task title as it appears on the page
'totalTime' provided in valid ISO 8601 duration format
Each step uses '@type': 'HowToStep' with both 'name' and 'text' populated
Step images added with absolute URLs (not relative paths)
'supply' and 'tool' arrays included if the tutorial references required resources
Schema injected into <head> via <script type='application/ld+json'>
Validated with Google Rich Results Test and zero critical errors returned
HOW-TO SCHEMA VS. FAQ SCHEMA — CHOOSING THE RIGHT TYPE
DimensionHow-To SchemaFAQ Schema
Best content typeStep-by-step tutorials, guides, instructional postsQuestion-and-answer pages, support content
SERP displayNumbered step carousel (especially mobile)Expandable Q&A accordion below the result
Minimum required fieldsname, step (name + text per step)mainEntity (name + acceptedAnswer per question)
Image supportYes — per-step images eligible for displayNo image rendering in rich result
AI/AEO signalStrong procedural knowledge signal for LLMsStrong factual/definitional knowledge signal
Can coexist on same pageYes, if content warrants both typesYes, if content warrants both types
REAL-WORLD EXAMPLE
How-To Schema for a Next.js robots.txt Tutorial

A blog post titled 'How to Set Up a robots.txt File in Next.js' implements HowTo schema with 5 steps: (1) Create the file, (2) Define crawl rules, (3) Reference your sitemap, (4) Test with Google Search Console, (5) Deploy and verify. The schema sets totalTime to 'PT10M', includes a tool entry for 'VS Code', and attaches a 400×300 screenshot to each step. After deploying, the post earns a mobile step carousel rich result — the step names are visible without clicking, and users can swipe through steps directly in Google Search. CTR increases 34% compared to the same post's pre-schema baseline, driven by the expanded visual footprint and perceived content credibility.

Free Tool

How does your site score on AEO?

Paste your URL. Get a score and a fix list across all three disciplines. No form, no email.

Run Free Audit →

Frequently Asked Questions

Pages with genuine step-by-step instructional content: setup guides, tutorials, recipes, DIY instructions, configuration walkthroughs. Don't apply it to informational articles that aren't structured as steps — Google can detect the mismatch and may not show the rich result, or may penalise for misleading markup.

Yes — multiple schema types can coexist on one page. A tutorial page might legitimately have How-To schema for the steps and FAQPage schema for frequently asked questions about the process. Use separate JSON-LD blocks for each type rather than nesting them.

Sources & Further Reading
  • 1.Google — How-To structured data documentation
  • 2.Schema.org — HowTo type
  • 3.Google Rich Results Test