Skip to content
Chalk Labs / AI SEO
How-to guide

How to Add HowTo Structured Data (and Whether You Should)

By Rahil Jain, founder of Chalk LabsUpdated How we research

The short answer

To add HowTo structured data, write numbered steps on the page, then describe them in JSON-LD with the HowTo type, a name, and a list of HowToStep items. Google no longer shows HowTo rich results, so add it only if it is cheap and the steps are visible on the page.

  • Google removed its How-to structured data documentation on 14 September 2023 because the rich result no longer shows on desktop or mobile.
  • Schema.org still defines HowTo as instructions that explain how to achieve a result by performing a sequence of steps.
  • Google's AI guide says no special schema is needed for generative AI search. We found no study showing HowTo markup lifts citations.
  • The steps in the code must match the steps readers can see. Real, clear steps on the page matter far more than the code.

What is HowTo structured data?

HowTo structured data is code that labels a page of instructions so software can see the steps, the time and the tools without reading the whole page. Schema.org defines HowTo as instructions that explain how to achieve a result by performing a sequence of steps 1.

The main parts are a name, a list of steps and optional details. Schema.org lists step, totalTime in ISO 8601 duration format such as PT30M, tool for items used but not consumed, supply for items consumed and estimatedCost 1. Each step is a HowToStep, defined as a step in the instructions for how to achieve a result 2.

Do it step by step

0 of 8 done0%

  1. Confirm the page teaches one task with a start and an end. If it explains an idea or compares options, do not use HowTo.

  2. Use one action per step, beginning with a verb. Add a short result to each step if useful, such as 'the light turns green'.

    Tip: Aim for five to ten steps. Fewer is vague; more suggests the task needs splitting.

  3. Estimate the total time in minutes, list what is used but not consumed (tools) and what is consumed (supplies). Show them on the page too.

  4. Copy the template below. Set the name to the task, convert the time to ISO 8601 (30 minutes is PT30M), and add one HowToStep per page step.

  5. Use single quotes inside text values, and make sure the last item in each list has no trailing comma.

    Tip: A JSON formatter in your editor will flag syntax slips immediately.

  6. Put the block in a script tag of type application/ld+json on the page that shows the steps.

  7. Run the validator, then read each coded step against its page step for wording and order.

  8. If a step changes, change the code in the same edit, or generate both from one list.

Your ticks are saved in this browser only.

Copy-ready templates

HowTo JSON-LD with time, tool, supply and three steps

json
{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to replace a bike inner tube",
  "totalTime": "PT20M",
  "tool": [
    { "@type": "HowToTool", "name": "Tyre levers" },
    { "@type": "HowToTool", "name": "Bike pump" }
  ],
  "supply": [
    { "@type": "HowToSupply", "name": "Spare inner tube" }
  ],
  "step": [
    {
      "@type": "HowToStep",
      "position": 1,
      "name": "Remove the wheel",
      "text": "Release the brake, open the quick-release and lift the wheel out of the frame."
    },
    {
      "@type": "HowToStep",
      "position": 2,
      "name": "Take out the old tube",
      "text": "Let the air out, lever one side of the tyre off the rim and pull the tube out."
    },
    {
      "@type": "HowToStep",
      "position": 3,
      "name": "Fit the new tube",
      "text": "Put in a little air, tuck the tube inside the tyre, press the tyre back onto the rim and pump to the pressure printed on the sidewall."
    }
  ]
}

Sample task only. Replace every value with your own task and keep the steps identical to the visible page. The structure follows the HowTo, HowToTool, HowToSupply and HowToStep types on schema.org.

Matching visible HTML

html
<h1>How to replace a bike inner tube</h1>
<p>Time: about 20 minutes. Tools: tyre levers, bike pump. You need: a spare inner tube.</p>
<ol>
  <li><strong>Remove the wheel.</strong> Release the brake, open the quick-release and lift the wheel out of the frame.</li>
  <li><strong>Take out the old tube.</strong> Let the air out, lever one side of the tyre off the rim and pull the tube out.</li>
  <li><strong>Fit the new tube.</strong> Put in a little air, tuck the tube inside the tyre, press the tyre back onto the rim and pump to the pressure printed on the sidewall.</li>
</ol>

Each list item mirrors one HowToStep, in the same order.

Pre-publish checklist

markdown
- [ ] Page teaches one task from start to finish
- [ ] Every step in the code is visible on the page
- [ ] Step order matches
- [ ] totalTime is in ISO 8601 format (PT30M)
- [ ] Validated at validator.schema.org with no errors
- [ ] Someone else followed the steps successfully

Run through it on every guide.

What happened to HowTo rich results in Google?

They are gone. Google's changelog records that on 14 September 2023 it removed the How-to structured data documentation, because the rich result is no longer shown in search results, on both desktop and mobile 3.

Google's supported-features gallery does not list How-to 4; the FAQ schema guide gives the gallery details. If a guide told you that HowTo markup earns step lists in results, it is out of date. The documentation removal is the dated event; do not read it as the day every display ended.

Does HowTo markup help you appear in AI answers?

We found no evidence that it does. Google's AI optimization guide, updated 10 July 2026, says structured data is not required for generative AI search and that there is no special schema.org markup you need to add 5. Google's AI features page adds that there are no additional requirements to appear in AI Overviews or AI Mode 6.

We found no published study measuring a HowTo citation effect in ChatGPT, Perplexity or Copilot. Treat any claim of one as unproven until you see the method.

What does matter is the page itself. A clear numbered list with one action per step, a time estimate and a stated outcome is easy for people and for AI to quote. See how to write how-to pages that get cited.

Should you still add it?

Add it when it is nearly free, skip it when it is not. A reasonable rule: if your content system can generate the code from the same step list as the page, keep it. If you would hand-write code for each guide, spend that time improving the steps.

The case for keeping it is our own judgement, not a published finding. Writing the markup forces you to define steps, time and tools clearly, and valid schema.org data is readable by any tool that supports the vocabulary. The case against is upkeep: markup that drifts from the page causes problems.

A quick decision rule
Your situationAdd HowTo markup?Why
Platform generates it from your step listYesNo extra work, stays in sync
Few guides, developer on handOptionalCheap, mainly a clarity exercise
Hundreds of guides, hand-codedNoUpkeep outweighs any known benefit
Page steps are vague or hiddenNoFix the page first
Content is a recipe or videoDifferent typeUse the recipe or video type instead

How should you split the steps?

One action per step is the rule. Schema.org lets a HowToStep hold HowToDirection and HowToTip items, so a step can carry a short tip without becoming two steps 2. Keep the tip on the page too.

Weak versus strong step list
  • Weak: '1. Sort out the tyre and tube and get everything back on.'
  • Strong: '1. Remove the wheel. 2. Take out the old tube. 3. Fit the new tube.'
  • Why it is better: each step is one action a person can tick off, and each maps to one HowToStep. (Illustrative example.)

What do you need, and how long does it take?

You need a page with numbered, visible steps, edit access to add a script tag, and the free Schema Markup Validator. Allow about 30 minutes for your first guide, which is our estimate.

The free Schema Generator can output HowTo JSON-LD from your steps if you prefer not to write it by hand.

Why must the steps in the code match the page?

The policy rule is the same as for FAQ markup: the code must describe what readers can see 7. See the FAQ schema guide for the wording.

For HowTo, that means one HowToStep per page step, in the same order. Do not add steps to look more complete, and do not stuff keywords into step names.

Which HowTo mistakes come up most?

Marking up a page that is not instructions is the first mistake. A product page, a sales page or an opinion piece is not a HowTo. The second is using it for a list of tips with no real sequence.

Others: steps that bundle three actions together, no time or tools when they matter, and a name that is a marketing line instead of the task. Name it as the task: 'How to replace a bike inner tube'.

How do you check it worked?

Paste the code into validator.schema.org and look at the parsed tree: the HowTo type should be recognised and the steps should list in order. Names and text can be plain strings, so a clean result is not proof the steps are good.

There is no Google result to look for, so success means valid code and a page people can follow. Ask a colleague to do the task from your steps alone and note where they stop.

When should you skip HowTo markup?

Hold off while bigger gaps remain, such as blocked crawlers, script-only text or thin steps. Start with how to check that AI bots can crawl your site.

If you do plan schema work, put the identity pieces first. Organization and Person schema says who is behind the content, and FAQ schema covers the sister type that Google also stopped showing.

Frequently asked questions

Does Google still support HowTo structured data?

Google removed its How-to structured data documentation on 14 September 2023, saying the rich result no longer shows on desktop or mobile 3. Its current gallery does not list How-to 4. The markup is still valid schema.org, but Google will not show a step-list result for it.

Will HowTo schema get me cited by ChatGPT?

We found no evidence it does. Google says no special schema is needed for its AI features 5, and we found no published study measuring a HowTo citation effect in ChatGPT, Perplexity or Copilot. Clear, numbered steps on the page matter more than the code.

What is the difference between HowTo and FAQ schema?

HowTo describes a sequence of steps to reach a result 1. FAQ describes separate questions with answers on one page. Use HowTo for tasks and FAQ for question lists. Google stopped showing rich results for both.

Do I need images in HowTo markup?

No. Schema.org allows images on steps and directions but does not require them 2. Add them only if the page shows them to readers, so the markup stays a true match of the page.

How do I test HowTo markup?

Paste the code or page URL into the Schema Markup Validator at validator.schema.org. It checks structured data against the schema.org vocabulary. Then compare the code to the visible steps by eye, because a validator cannot judge whether they match.

About the author

Rahil Jain

Rahil Jain is an AI SEO (answer engine and generative engine optimisation) consultant and co-founder of Chalk Labs.

LinkedIn · Method and credentials

Sources

  1. HowTo · Schema.orgOpened October 20, 2026. Supports: HowTo is instructions that explain how to achieve a result by performing a sequence of steps; properties step, totalTime (ISO 8601 duration), tool, supply and estimatedCost.
  2. HowToStep · Schema.orgOpened October 20, 2026. Supports: HowToStep is a step in the instructions; it can contain HowToDirection and HowToTip items; images, name, url and position are inherited, not required.
  3. Search Central documentation updates · Google Search CentralOpened October 20, 2026. Supports: 14 September 2023 entry: How-to structured data documentation removed because the rich result is no longer shown on desktop or mobile.
  4. Structured data markup that Google Search supports · Google Search CentralOpened October 20, 2026. Supports: Gallery last updated 2026-10-16 lists 25 features and does not list How-to or FAQ.
  5. Optimizing your website for generative AI features on Google Search · Google Search CentralOpened October 20, 2026. Supports: Structured data is not required for generative AI search; no special schema.org markup needed; page updated 2026-07-10.
  6. AI features and your website · Google Search CentralOpened October 20, 2026. Supports: No additional requirements to appear in AI Overviews or AI Mode; last updated 2025-12-10.
  7. General structured data guidelines · Google Search CentralOpened October 20, 2026. Supports: Markup must be a true representation of the page content; do not mark up content not visible to readers; JSON-LD recommended.
How this page was made. Built on Rahil Jain's AI SEO method and drafted with AI research assistance. Every statistic links to the page we read it on (opened October 20, 2026 or nearby). Published October 20, 2026; last updated October 20, 2026. Chalk Labs sells AI SEO services, so we have a commercial interest in this topic. Spotted an error? Tell us and we will fix it.