HowTo Schema: Does It Still Do Anything?

HowTo schema followed almost the same trajectory as FAQ schema: a genuinely useful rich result — a numbered step-by-step card in the SERP, sometimes with images per step — that Google significantly scaled back in 2023 alongside the FAQ restriction. If you implemented HowTo schema expecting that visual result today, the honest answer is it's unlikely to appear for most sites. This article covers what actually changed, what HowTo schema still does, and when it's genuinely worth implementing in 2026.

Google's 2023 changes narrowed HowTo rich result eligibility significantly, in the same update cycle that restricted FAQ. The step-by-step visual card that used to appear for a wide range of tutorial and instructional content is no longer reliably available outside a narrow set of eligible cases. Guidance published before this change still circulates widely and still promises the old outcome — the same gap between expectation and current reality covered in the FAQ schema article in this series applies here.

Worth noting a detail specific to HowTo: part of the original rich-result value was tied to voice and smart-display surfaces (Google Assistant reading out or displaying steps), not just the traditional desktop or mobile search result. That surface-specific value has narrowed along with the core web rich result.

Yes, for the same underlying reason FAQ schema still has value after losing its rich-result guarantee: the structured data still hands a search engine or AI system a cleanly segmented, explicitly ordered set of steps, rather than making it infer a procedure's structure from unstructured paragraphs. For genuinely instructional content — a real step-by-step guide, not content retrofitted with artificial "steps" — that structure is a useful input for the retrieval-and-citation mechanics covered in the AI Overviews article in this series. An AI system answering "how do I do X" benefits from content that states the steps explicitly and in order, which is exactly what HowTo schema markup provides regardless of whether Google renders a visual card for it.

name is the overall procedure's title. step is the core property: an ordered array of HowToStep items, each with its own name and text describing that specific step. image at the step level, where genuinely available, gives a retrieval system a visual reference tied to a specific instruction rather than one generic image for the whole procedure. totalTime, using ISO 8601 duration format, communicates how long the full procedure takes. supply and tool list the materials or tools required, structured as HowToSupply and HowToTool respectively rather than folded into plain-text instructions.

The most common implementation error: writing genuinely sequential, step-dependent content in prose, then reverse-engineering a HowTo schema block from it after the fact, often losing precision in the process. The schema should ideally be generated from the same structured data that drives the visible step-by-step content on the page — a numbered list in your CMS content model, for instance — not manually reconstructed as an afterthought.

The calculation now: implement HowTo schema when the content is genuinely procedural — a real sequence of ordered steps someone follows to accomplish something — and you want that structure available to retrieval systems and AI Overviews, not because you expect the rich-result visual. Content that isn't genuinely step-by-step (a general explainer that happens to use a numbered list for readability, for instance) shouldn't be forced into HowTo schema just because numbered content is present on the page — the same misuse concern covered for FAQ schema applies: schema should reflect genuine content structure, not be manufactured to qualify for a format.

If your content is a technical setup guide, an assembly or installation procedure, a recipe (which has its own more specific Recipe type worth using instead where it applies), or any other genuinely sequential how-to, HowTo schema remains a reasonable implementation choice for the retrieval-layer value alone.

On WordPress specifically, plugins like Yoast SEO can generate HowTo schema markup automatically from a properly formatted step-by-step block in the content editor, which is a reasonable approach for sites already using that plugin ecosystem — it keeps the schema in sync with the visible content by construction, since both are generated from the same structured block rather than maintained separately. The same caution from the generator discussion elsewhere in this series still applies: verify the plugin-generated output actually includes accurate step counts, correctly formatted totalTime, and genuine step text rather than placeholder content left over from a template. A generic HowTo schema generator outside a CMS plugin ecosystem carries the same disconnect risk as any other schema generator — it produces valid structure without verifying the content is genuinely procedural.

Checking current rich snippet eligibility for HowTo structured data specifically is worth doing per-site rather than assuming either way based on general guidance (including this article) — narrow categories of sites may still qualify under Google's current criteria, and criteria can shift again. The Rich Results Test remains the authoritative per-page check; treat any written guidance, including guides published after the 2023 change, as a starting point for what to verify rather than a final answer for your specific site and content category.

Instructional content is one of the categories where pairing structured data types compounds value: HowTo schema alongside VideoObject schema, where a step-by-step guide has an accompanying video, gives a retrieval system both the explicit step sequence and the video metadata (duration, thumbnail) as separate, cross-referenced structured signals rather than one undifferentiated piece of content. This combination is worth the extra implementation effort specifically for tutorial content where video is a natural companion format.

Run pages carrying HowTo schema through Google's Rich Results Test to confirm current eligibility status for your specific site, and the Schema.org validator for broader compliance. Given the narrowed rich-result eligibility, don't be surprised if a technically valid HowTo block shows no rich-result eligibility in the test — that's the expected outcome for most sites now, not an error to debug. Focus validation effort on structural correctness (properly ordered steps, accurate totalTime, correctly typed supply and tool entries) rather than chasing rich-result eligibility that may simply not be available for your site under current criteria.

Treat HowTo schema the same way this series treats FAQ schema: implement it for genuine procedural content because it hands retrieval systems and AI Overviews a cleaner, more citable structure, not because of an expectation of the old visual rich result. The rich-result use case has narrowed substantially since 2023; the underlying structured-data value for how AI systems parse and cite step-by-step content has, if anything, become more relevant as more search traffic shifts toward AI-generated answers to procedural questions.