What Is HowTo Schema?
HowTo schema is structured data, using schema.org's HowTo type, that describes a set of steps for completing a task, breaking a tutorial into ordered steps with optional tools, materials, images, and time estimates. It once powered step-by-step HowTo rich results in Google Search, but Google deprecated those rich results in 2023, so the markup no longer produces that visual feature. It remains a valid way to structure instructional content for other systems, AI parsers, and clarity, though it no longer earns a dedicated Google search enhancement.
- Schema type
- HowTo (schema.org)
- Google rich result status
- deprecated in 2023, no longer displayed (Google Search Central)
- Core sub-types
- HowToStep, HowToTool, HowToSupply, HowToSection (schema.org)
- Still useful for
- AI and non-Google parsing, on-page clarity, other search engines (industry-typical)
What is HowTo schema, exactly? #
HowTo schema is a way to describe a task and the ordered steps needed to complete it in a machine-readable format. Using schema.org's HowTo type, you name the overall task, then list each step as a HowToStep with its own text and optional image. You can also specify the tools required with HowToTool, the materials or supplies with HowToSupply, an estimated total time, and even an estimated cost. The result is a fully structured tutorial that a computer can read and understand, not just render as text. HowTo was designed for genuinely instructional content: replacing a part, assembling furniture, configuring a setting. It is distinct from a recipe, which has its own dedicated Recipe type. Before adopting HowTo, though, it is essential to understand its current standing in Google Search, covered in the next section, because its practical value has changed significantly since it was introduced and widely recommended a few years ago.
Is HowTo schema still worth using? #
This is the crucial question, and the honest answer is nuanced. Google deprecated HowTo rich results in 2023, meaning the step-by-step visual feature this markup once produced in search no longer appears for anyone. If your only goal was that Google rich result, adding HowTo schema today will not achieve it. That said, the markup itself is not forbidden or broken; it is simply no longer rewarded with a Google feature. HowTo remains a valid schema.org type, and structured instructional content can still help other consumers of your data, including non-Google search engines, AI systems that parse and summarize content, and internal tools. For most local businesses, the pragmatic takeaway is not to invest development time chasing a HowTo rich result that will never show. Instead, focus structured-data effort on currently supported types described in our /wiki/schema-markup-guide, and treat HowTo as optional semantic enrichment rather than an SEO win.
How is HowTo schema structured? #
A HowTo block starts with a name describing the task, then contains a step property holding an ordered list of HowToStep items. Each HowToStep has text describing the action and can include a name, an image, and a url pointing to that step's anchor on the page. For longer tutorials, you can group steps into HowToSection blocks. Supporting properties add depth: tool lists the required tools as HowToTool items, supply lists consumable materials as HowToSupply, totalTime gives an ISO 8601 duration, and estimatedCost provides a MonetaryAmount. The example below shows a compact HowTo with two steps and a required tool. Even though Google no longer renders this as a rich result, keeping the structure clean and matched to visible page content is good practice, and you can confirm it parses with /tools/schema-validator. Well-formed markup is easier for any future or non-Google system to interpret correctly.
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Reset a Tripped Circuit Breaker",
"totalTime": "PT5M",
"tool": [{ "@type": "HowToTool", "name": "Flashlight" }],
"step": [
{
"@type": "HowToStep",
"name": "Locate the panel",
"text": "Open your electrical panel and find the breaker in the OFF or middle position."
},
{
"@type": "HowToStep",
"name": "Reset the breaker",
"text": "Push the breaker fully OFF, then firmly back to ON."
}
]
}What replaced HowTo rich results? #
Nothing directly replaced the deprecated HowTo rich result, but the underlying user need, quick step-by-step answers, is now met in other ways. Google increasingly surfaces instructional answers through featured snippets drawn from well-organized page content, and through AI-generated summaries covered in our /wiki/what-are-ai-overviews. Both of these reward clear, well-structured writing on the page itself rather than HowTo markup. For video tutorials, the key moments feature tied to /wiki/what-is-video-schema fills a similar role, splitting a how-to video into labeled, jumpable chapters. The practical lesson is to shift effort from the retired markup toward genuinely well-organized content: clear numbered steps, descriptive headings, and helpful images. That structure helps you qualify for featured snippets and be cited by AI answers, which is where instructional visibility now lives. In other words, write the tutorial well and structure the page thoughtfully, rather than relying on a schema feature Google no longer displays. Clear numbered headings, a short summary of steps near the top, and images that match each step give both human readers and answer engines the structure they reward, which is exactly what the deprecated markup used to signal in code.
Should local businesses use HowTo markup? #
For most local service businesses, HowTo markup is now a low priority. If you publish genuinely helpful how-to content, and many should, the real value comes from writing it clearly, not from the schema. A plumber's guide to shutting off a home water main, or an electrician's walkthrough of resetting a breaker, earns trust and can rank on the strength of the content itself. Adding HowTo markup on top will not produce a Google rich result, so do not let a developer bill hours for it under that promise. There is minimal harm in including valid HowTo markup as semantic enrichment if it comes free with your /wiki/what-is-a-cms, but it should never be the reason you build a page. Spend structured-data budget instead on supported, high-value types and on a strong /services/local-seo foundation. The content, not the deprecated markup, is what wins visibility for instructional pages today.
What are common HowTo schema mistakes? #
The biggest mistake now is investing time in HowTo markup expecting a Google rich result that no longer exists; that expectation is simply outdated. Beyond that, the classic technical errors still apply if you do use it. The markup must match visible on-page content, so do not describe steps that are not actually shown to users. Do not use HowTo for content that belongs in a different type, such as a recipe, which has its own Recipe markup, or a general article. Avoid using HowTo purely to stuff keywords or to describe promotional rather than instructional content, which violates guidelines. Keep step order and numbering consistent between the markup and the page. If you retain legacy HowTo markup from before the deprecation, it will not hurt you as long as it is valid and honest, but do not add more under the assumption it earns a feature. Validate anything you keep with /tools/schema-validator to ensure it remains well-formed.
How does HowTo compare to FAQ and other deprecated markup? #
HowTo is not the only structured-data type Google has scaled back. FAQ rich results were also narrowed in 2023 and now appear only for a limited set of authoritative sites, and the sitelinks searchbox was deprecated in late 2024. This pattern reflects Google's broader move to reduce clutter and shift toward AI-driven answers. The lesson for site owners is to treat rich result features as changeable rather than permanent, and to verify a type is currently supported before building around it. Types tied to genuine commerce and content, such as Product, Recipe, Event, and Breadcrumb, remain well supported, while promotional or easily-abused features have been trimmed. Staying current matters because chasing a retired feature wastes effort. Our /wiki/schema-markup-guide focuses on the types that still earn results, and pairing it with /wiki/ai-search-optimization helps you invest in structured data that supports both classic and emerging forms of search visibility.
How do you handle existing HowTo markup on a site? #
If your site already carries HowTo markup from a few years ago, you do not need to rush to remove it, but you should reassess it. First, confirm it is still valid and honest with /tools/schema-validator, since broken markup helps no one. Second, recognize it will not produce a Google rich result, so update any internal reporting or client expectations that still assume it does. Third, make sure the effort behind that page is now directed at strong content and supported markup rather than maintaining a feature that no longer exists. During any /services/website-redesign or /services/website-migrations project, decide deliberately whether to keep, replace, or drop legacy HowTo blocks rather than carrying them forward by accident. For ongoing sites, a /services/care-plans arrangement can audit structured data periodically, retire deprecated types, and reallocate attention to schema that still delivers value in current search results.
FAQ
Did Google really remove HowTo rich results?
Yes. Google deprecated HowTo rich results in 2023, so the step-by-step visual feature this markup once produced no longer appears in search for anyone. The HowTo schema.org type still exists and remains valid to use, but it no longer earns a dedicated Google search enhancement. Plan your structured-data work around currently supported types instead.
Should I delete my existing HowTo markup?
You do not have to. Valid, honest HowTo markup that matches your page content causes no harm, even though it no longer produces a rich result. Just update your expectations, and confirm the markup is still well-formed with a validator. During a redesign or migration, decide deliberately whether to keep, replace, or remove it rather than carrying it forward unintentionally.
What is the difference between HowTo and Recipe schema?
Both describe steps, but Recipe is a dedicated type for cooking with ingredients, nutrition, and cook time, and it still earns rich results. HowTo covers general tasks like repairs or setup and no longer produces a Google feature. Use Recipe for food content and reserve HowTo, if at all, for non-cooking instructions as optional enrichment.
How do instructional pages get visibility now?
Through well-written, clearly structured content rather than HowTo markup. Google surfaces step-by-step answers via featured snippets and AI Overviews, both drawn from organized page content with clear headings and numbered steps. For video tutorials, key moments from video schema split content into jumpable chapters. Write the tutorial clearly and the page will compete on its own merit.
Is HowTo schema useless now?
Not entirely, but its SEO value is minimal. It no longer earns a Google rich result, yet it remains a valid way to structure instructions for AI systems, non-Google engines, and semantic clarity. Do not pay to add it expecting a search feature. If it comes free with your CMS and is accurate, keeping it is harmless enrichment.
Which schema types still earn rich results?
Types tied to genuine commerce and content remain well supported, including Product, Recipe, Event, Breadcrumb, and Video. Google has trimmed easily-abused or promotional features like HowTo and much of FAQ. Our /wiki/schema-markup-guide focuses on the currently supported types, and validating with /tools/schema-validator confirms your markup targets features that actually appear in search today.
Was this helpful?