Last updated:
HowTo Schema Generator
This HowTo schema generator turns written instructions into HowTo JSON-LD: a title, the steps in order, and the tools, supplies, time and cost they need. Google no longer shows how-to rich results, so read what the markup still does before you add it to every tutorial.
Reference: HowTo schema
How-To: Use for tutorial or how-to content with clear steps. Google no longer shows how-to rich results, so this describes the steps for other tools; it doesn't change your Google result.
What Google shows for HowTo markup
- How-to: retired: Google stopped showing it on September 13, 2023.
Google stopped showing how-to rich results on September 13, 2023, first on mobile and then on desktop, and dropped HowTo from the Rich Results Test and from Search Console's rich result reports. Valid HowTo code now leaves your search result exactly as it would be without it, and no field in the form brings the steps back.
Google also said that structured data it doesn't use causes no problems for Search, so there's no harm in leaving HowTo on pages that already have it. Writing it new pays off when something other than Google Search reads your steps: your own site's templates or search, an app that imports instructions, or a service whose documentation names HowTo. For cooking, use the Recipe form instead: Google still shows recipe results, and Recipe takes the same kind of steps.
How to fill in each field
Title, description and image
The title says what the reader will achieve, usually the page's own heading, such as How to re-caulk a bathtub. Keep the description to a sentence or two about the result and the effort involved. Page URL is the tutorial's address, and Image URL a photo of the finished job rather than a stock picture.
Time, cost, tools and supplies
Total Time is an ISO 8601 duration: PT20M for 20 minutes, PT1H30M for an hour and a half, P1D for a job that waits overnight. Estimated Cost is a plain number such as 18, with the currency picked beside it; count what the reader buys, not tools they probably own.
Supplies and tools are comma-separated lists, and the generator writes each item as its own HowToSupply or HowToTool. Supplies get used up (caulk, painter's tape); tools are kept (a caulk gun, a utility knife).
Steps
Add one step per action the reader takes, in the order the page gives them; the generator numbers them with position. The step title is a short label such as Remove the old caulk, and the description is the instruction itself, worded as the page words it. A step image shows that step. The form writes a flat list of HowToStep items: if your page groups steps under headings, edit the copied code into HowToSection groups.
The form marks 2 fields as required and 3 as recommended:
- Title (required): What this how-to teaches.
- Steps (required): Add the steps to complete this task. Each step needs at minimum a name and description.
- Description (recommended): A brief summary of what the reader will learn.
- Total Time (recommended): How long it takes in ISO 8601 duration (e.g. PT30M for 30 minutes).
- Image URL (recommended): A URL to an image representing this item. Google recommends images be at least 1200px wide.
Example: A bathroom repair in four steps
A HowTo with a total time, an estimated cost, its supplies and tools as typed items, and four numbered steps, two of them with images.
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to re-caulk a bathtub",
"description": "Replace cracked or moldy caulk around a bathtub in about an hour, plus a day for the new caulk to cure.",
"url": "https://homefix.example/guides/recaulk-bathtub/",
"image": "https://homefix.example/images/recaulk-finished-1200.jpg",
"totalTime": "P1DT1H",
"estimatedCost": {
"@type": "MonetaryAmount",
"currency": "USD",
"value": 18
},
"supply": [
{
"@type": "HowToSupply",
"name": "Silicone bathroom caulk"
},
{
"@type": "HowToSupply",
"name": "Painter's tape"
},
{
"@type": "HowToSupply",
"name": "Rubbing alcohol"
}
],
"tool": [
{
"@type": "HowToTool",
"name": "Caulk gun"
},
{
"@type": "HowToTool",
"name": "Utility knife"
},
{
"@type": "HowToTool",
"name": "Caulk removal tool"
}
],
"step": [
{
"@type": "HowToStep",
"position": 1,
"name": "Remove the old caulk",
"text": "Cut along both edges of the old bead with the utility knife, then pull it out and scrape away what's left with the removal tool.",
"image": "https://homefix.example/images/recaulk-step-1.jpg"
},
{
"@type": "HowToStep",
"position": 2,
"name": "Clean and dry the joint",
"text": "Wipe the joint with rubbing alcohol to lift soap residue and mold, then let it dry completely."
},
{
"@type": "HowToStep",
"position": 3,
"name": "Tape and apply the new bead",
"text": "Run painter's tape along both sides of the joint, about 3 mm from it, and squeeze one steady bead of caulk into the gap.",
"image": "https://homefix.example/images/recaulk-step-3.jpg"
},
{
"@type": "HowToStep",
"position": 4,
"name": "Smooth it and let it cure",
"text": "Smooth the bead with a wet fingertip, pull the tape off at an angle, and keep the tub dry for 24 hours."
}
]
} 5 common mistakes
- Counting on a rich result. An audit or plugin that lists HowTo as a rich result opportunity is out of date. Google hasn't shown one since September 13, 2023.
- Steps the page doesn't show. The markup should repeat the instructions readers see, in the same order, not a shortened or reworded version.
- A recipe typed as HowTo. Cooking instructions belong in Recipe markup, which has a Google feature that's still live and uses the same step type.
- Times written in words. "About an hour" isn't a duration. Write
PT1H; the Validator flags durations that aren't ISO 8601. - The whole job in one step. One step holding every instruction tells a reader nothing about the sequence. Split it at each action.
How to test your HowTo markup
Check the code in the Schema Validator, which tests it against schema.org, durations included, and notes that Google retired the how-to result. Google's Rich Results Test no longer supports HowTo, so a page with only this markup shows no rich result there; that's expected, not an error to fix.
- Open the example in the Schema Validator, which checks it against schema.org and Google's requirements.
- Preview the example in the SERP Simulator to see which search enhancements it can earn.
- Read the howto schema reference for the type's other properties and more examples.
Frequently Asked Questions
Should I remove HowTo markup from my pages?
There's no need. Google has said that structured data it doesn't use causes no problems for Search. Remove it if it no longer matches the page, or if keeping it in step with edited instructions costs more time than it's worth to you.
Does HowTo markup help with Google's AI features?
Google's documentation for AI Overviews and AI Mode says there's no special schema.org structured data you need to add to appear in them. It doesn't name HowTo, so don't add the markup expecting that.
Can the generator write sections and tips?
No. It writes one flat list of HowToStep items, each with a title, the instruction and an optional image. For HowToSection or HowToTip, edit the copied code, then paste it into the Schema Validator to check it.
Other schema generators
- Local Business Schema Generator
- FAQ Schema Generator
- Product Schema Generator
- Organization Schema Generator
- Article Schema Generator
- Video Schema Generator
- Review Schema Generator
- Person Schema Generator
- Event Schema Generator
- Recipe Schema Generator
- Job Posting Schema Generator
- Course Schema Generator
- Software Application Schema Generator
- Breadcrumb Schema Generator
- Profile Page Schema Generator
- QAPage Schema Generator
- Discussion Forum Schema Generator
- Course List Schema Generator
- JSON-LD Generator, with every form and the templates