Google no longer shows HowTo rich results in search, so the visual step-by-step enhancement is effectively gone in 2026 — but structuring how-to content clearly still matters enormously for AI answer engines. If you added HowTo schema years ago expecting rich snippets, those visual results have been retired. That does not mean step-by-step content lost its value; it means the payoff moved from a search feature to how well machines can extract and reuse your instructions.

What actually changed with HowTo schema

HowTo structured data was introduced so Google could display expandable, illustrated step-by-step results for tasks like "how to tie a tie" or "how to reset a router." Over time Google narrowed where those results appeared, then removed the HowTo rich result from general search entirely. The markup is not an error to have on your pages, but it no longer earns the visual treatment it once did, and Search Console stopped reporting it as an enhancement.

This fits a broader pattern: search platforms periodically retire rich result types that see low usage or that overlap with newer answer formats. The lesson is not to chase every schema type for its snippet, but to mark up content because it genuinely describes what is on the page. Our guide to FAQ and How-To schema covers where each type still helps and where expectations have shifted.

Should you remove existing HowTo markup?

You do not need to rush to strip it out. Valid HowTo schema that accurately reflects a step-by-step process on the page is harmless and still describes your content to any system that parses structured data, including AI crawlers building a semantic understanding of your site. The one thing to avoid is invalid or mismatched markup — schema that no longer matches the visible content, references images that were removed, or was bolted onto a page that is not actually a tutorial.

If you audit your structured data and find HowTo blocks that are broken or misleading, clean them up or remove them; if they are accurate, leaving them is fine. Run them through a validator to be sure they parse without errors, as described in our structured data validation guide. The goal is honesty between your markup and your page, not chasing a rich result that no longer exists.

Where step-by-step content still wins: AI answers

The reason to keep writing excellent how-to content has shifted from Google's rich results to answer engines. When someone asks ChatGPT, Perplexity, or Google's AI overview how to do something, the system assembles the answer from clearly structured instructions it can find and trust. Content laid out as an ordered, self-contained sequence of steps — each one complete and unambiguous — is exactly what those systems lift and cite.

You get most of that benefit from good HTML rather than from the HowTo schema itself: a clear heading, a genuine ordered list of steps, concise instructions, and any required materials stated up front. This is the same principle behind passage indexing — write each step so it makes sense on its own, and an AI can extract it without needing the surrounding page.

What to do now

In practice: stop treating HowTo schema as a route to rich snippets, keep it only where it is valid and accurate, and invest your effort in the underlying content structure. Use real ordered lists, answer the "how do I" question directly in the opening lines, and make each step standalone. That structure serves human readers, featured snippets, and AI answer engines at once — a far more durable payoff than any single rich result format.

Want to know whether your structured data is valid and whether your how-to content is machine-extractable? Run the CheckMy.site scanner to validate your schema, flag mismatched markup, and see how well AI systems can read your step-by-step content.