SEO

HowTo Schema

Also called How-to markup, step-by-step schema

Structured data describing a procedure as ordered steps, with the tools, materials and time it requires.

Quick facts: HowTo Schema

Category
SEO
Also called
How-to markup, step-by-step schema
Level
Intermediate
Affects
How machines read instructional pages, AI summaries, developer time
Where to see it
Schema Markup Validator, Rich Results Test, Google Search Console
In this article4
  1. How HowTo schema works
  2. Why HowTo schema matters less than it used to
  3. Where HowTo schema goes wrong
  4. What to do about it

How HowTo schema works

HowTo describes a task that is completed by following instructions in order. The markup breaks the page into named steps, each with its own text and optionally its own image or anchor link, and can also list the supplies the reader needs, the tools they will use, and how long the whole thing takes.

Written properly it turns a wall of prose into a structure a machine can follow: this is the goal, these are the prerequisites, these are the steps and this is their order. That is a genuinely accurate description of an instructional page, and it is why the type exists in the vocabulary.

Why HowTo schema matters less than it used to

For a period, marking up instructions could win a distinctive search result that showed the steps directly in the listing. Google has since retired that rich result and no longer shows HowTo enhancements in search. The markup is not banned and it is not a penalty, but it will not produce a special result, and anyone offering to add it as a way of standing out in search is selling something that no longer exists.

What it still does is describe the page honestly to anything reading it: other search engines, assistants, and the systems that generate written answers. Those systems benefit from knowing where one step ends and the next begins, particularly on a long page where the boundaries are not obvious from the prose alone.

Where HowTo schema goes wrong

The commonest problem now is budget rather than syntax. Sites spend developer time retrofitting HowTo markup across an archive of guides on the promise of a search feature that has gone. That time buys a more accurate description of the page and nothing visible, which may still be worth it, but only if the decision is made with the facts.

The older technical mistakes have not disappeared. Steps marked up but not visible on the page break the basic rule that markup describes what the reader sees. Marking up something that is not really a procedure — a list of tips, a set of options, a features comparison — describes the page inaccurately. And applying HowTo to a page whose real purpose is selling a service, with a token set of steps bolted on, misrepresents what the page is.

What to do about it

If the markup already exists and validates, leave it. It costs nothing to keep, it still describes the page correctly, and removing it is developer time spent for no gain.

If you are deciding whether to add it, put the effort into the instructions themselves instead. Clear numbered steps, honest prerequisites, a note of what can go wrong at each stage and screenshots that match the current interface will serve a reader — and any system summarising the page — better than markup around vague prose ever could. Structure the guide well, publish it as part of the content plan for the site, and add the markup only if it is cheap to generate from a template you already maintain.

For pages that answer questions rather than teach a procedure, FAQPage markup is the more accurate type, though its rich result has been narrowed too.

Do and do not

Do

  • Keep valid markup you already have in place
  • Mark up only genuine procedures with an order
  • Invest in the clarity of the steps first

Do not

  • Budget for a rich result that has been retired
  • Mark up steps a visitor cannot see
  • Bolt fake steps onto a sales page

Questions people ask about this

Does HowTo schema still produce a rich result?

No. Google retired the HowTo rich result and no longer shows step-by-step enhancements in its search results. The markup remains valid structured data and carries no penalty, so existing implementations can stay in place, but nobody should plan work or budget around winning that particular search feature.

Should I remove HowTo markup from my old guides?

There is no need. Valid markup that accurately describes an instructional page is harmless, still readable by other systems, and costs nothing to leave alone. Removing it means paying a developer to touch every guide for no measurable benefit. Spend that time improving the instructions or fixing markup that is genuinely wrong.

What is the difference between HowTo and FAQPage schema?

HowTo describes a procedure completed in order, where the steps only make sense in sequence. FAQPage describes independent questions with independent answers, where a reader can take any one of them and ignore the rest. Choose based on how the content actually works, not on which one you hope will look better in search.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.