HowTo Schema Generator: Free JSON-LD Markup

A HowTo schema generator turns your tutorial's title, total time, cost and steps into ready-to-paste JSON-LD structured data. This free tool is for publishers, developers and SEOs who want clean Schema.org markup for step-by-step guides. Fill in the form, click Generate Schema, and copy the finished code.

What Is HowTo Schema Markup?

HowTo schema is a Schema.org vocabulary type that describes the instructions for completing a task. It tells machines that a page contains an ordered procedure, and it lists each action as a separate step.

The markup is written as JSON-LD, a block of structured data placed in a script tag that sits apart from your visible content. A basic HowTo item has a name (the task), an optional description, and a list of HowToStep items. Each step carries a short name and the full instruction text.

Two optional properties add context. totalTime uses an ISO 8601 duration, such as PT30M for 30 minutes. estimatedCost holds a currency code and a numeric amount, such as 10 USD. This generator supports all of these fields.

Does Google Still Show HowTo Rich Results?

No. Google has retired the HowTo rich result, so marked-up pages no longer get expandable step lists in search results. The tool itself carries the same notice: Google no longer offers this rich-result feature.

That changes what you should expect. HowTo markup will not give you a special search appearance, and it is not a ranking shortcut. What it still offers is a precise, standards-based description of your procedure that other parsers, crawlers and data consumers can read. If your goal is a rich result, look at schema types Google still supports, such as FAQ markup, recipe markup or breadcrumb markup, and check Google's Search Central documentation for current eligibility.

How to Use the HowTo Schema Generator

You can create HowTo markup in about two minutes by filling in the form from top to bottom. Only the title and one step are required.

1. Type the task into How-To Title, for example "How to bake a chocolate cake". This field is required.
2. Add a one or two sentence summary in Description. It is optional but helps describe the outcome.
3. Enter the duration in Total Time (ISO 8601), such as PT30M or PT1H20M. Leave it empty if you do not want to state a time.
4. Enter a number in the Estimated Cost box (for example 10) and a currency code in the box beside it. If you leave the currency blank, USD is used.
5. Fill in the Steps. Three empty step cards are ready for you. Give each one a short step name and the full instructions. Click Add Step for more cards, or Remove to delete one.
6. Click Generate Schema. The code appears under "HowTo Schema Generated". Click Copy Code and paste the complete snippet once into your page's head section.

Click Clear All to empty every field and start again with three fresh step cards. If you change any field after generating, the old output is cleared, so generate again before copying.

Worked Example: A Bike Tire Tutorial

Say you published a guide on replacing a bike inner tube. Here is what you would enter and what the generator returns.

• How-To Title: How to replace a bike inner tube
• Description: Fix a flat tire at home with basic hand tools.
• Total Time: PT25M
• Estimated Cost: 8 with currency USD
• Step 1: "Remove the wheel" with the instruction "Release the brake, open the quick-release lever and take the wheel off the frame."
• Step 2: "Take out the old tube" with the instruction "Pry one tire bead off the rim with a tire lever and pull the tube out."
• Step 3: "Fit the new tube" with the instruction "Add a little air, tuck the tube inside the tire and press the bead back onto the rim."
• Step 4: "Inflate and refit" with the instruction "Pump to the pressure printed on the tire sidewall and reinstall the wheel."

After you click Generate Schema, you get one script block of type application/ld+json. It declares the item as a HowTo, repeats your title and description, sets the total time to 25 minutes, records an estimated cost of 8 in US dollars, and lists four HowToStep entries in the order you typed them. Each step keeps its name and its instruction text.

Notice what the markup does not add. It does not invent steps, images or tools. It contains only what you typed, so the quality of the output depends on the quality of your input.

How to Read and Act on the Results

The output is a single copy-ready snippet, and a good one mirrors your visible page exactly. Compare each step in the code with the steps a reader sees on the page before you publish.

Getting the time format right

The Total Time field accepts only ISO 8601 durations, which always begin with the letter P. Use these patterns:

The letter T separates the date part from the time part, so minutes and hours need it. Writing "30 minutes" or "30m" will trigger an error asking for an ISO 8601 duration.

What good steps look like

Good steps each describe one action, start with a verb and make sense on their own. A widely used guideline is three to ten steps for a typical tutorial. If you have twenty, group related actions or split the guide into two pages. A weak step reads "Do the next part". A strong one reads "Pry one tire bead off the rim with a tire lever."

Step names left blank

If you enter instructions but no step name, the generator labels that step "Step 1", "Step 2" and so on. That works, but a descriptive name is more useful. A card with both fields empty is skipped entirely, so stray blank cards will not break your output.

Who Should Use This Tool and When

This generator suits anyone who publishes a procedure and wants it described in standard structured data without writing JSON by hand.

• Bloggers and content teams documenting tutorials, DIY projects or software walkthroughs.
• Developers who need a valid starting snippet to paste into a template or a CMS field.
• SEO specialists auditing a site that already uses HowTo markup and rebuilding it in a clean format.
• Documentation writers who want help articles to carry consistent, machine-readable steps.

It is not the right choice for recipes, which have their own type with ingredients and nutrition. Use the Recipe Schema Generator for those. For blog posts and news, the Article Schema Generator fits better.

Best Practices and Troubleshooting

Most problems come from markup that does not match the page, or from a malformed value. These habits prevent both.

• Match the page. Every step in the markup should appear as visible text on the page, in the same order. Do not mark up content users cannot see.
• Paste once. Put the full snippet in the head section a single time. Duplicates on one page create conflicting data.
• Use one HowTo per procedure. If a page covers two separate tasks, generate two separate snippets, and make sure each one describes a task on that page.
• Validate before publishing. Paste the result into the Schema Markup Validator to confirm the syntax and key properties.
• Keep it current. If you change the steps on the page, regenerate the code so the two stay in sync.

If you see "Please enter the How-To title", the title box is empty. If you see "Please add at least one step", every step card is blank. A message about the duration means Total Time is not in ISO 8601 form. A message about cost means the amount must be a plain nonnegative number, so enter 10 rather than $10 or "ten", and put the currency code in the second box.

Limitations to Know About

The generator covers the core HowTo properties: title, description, total time, estimated cost and steps. It does not include fields for step images, videos, required supplies or tools. If you need those, you can edit the copied code by hand, then recheck it in a validator.

Because Google no longer displays HowTo rich results, the markup will not change how your listing looks. Treat it as an accurate description of your content, not a ranking lever. If you want to produce other types in the same session, the Schema Markup Generator covers articles, products, events and local businesses, and the On-Page SEO and Meta Tags category lists related tools.

Ready to describe your tutorial in structured data? Enter your title and steps in the form on this page, generate the schema, and copy it straight into your page.