HowTo schema is still valid markup, but Google removed HowTo rich results from search in 2023 — so the step-by-step visual enhancement it used to earn no longer appears. The markup won't hurt you and can still help AI systems parse procedural content, but it's no longer worth adding for SEO alone. The bigger win now is well-structured steps on the page itself, which any system can extract with or without the schema.
What changed
For years, HowTo schema earned a distinctive search enhancement: Google would show your numbered steps, sometimes with images, expanded right in the results. It was a real reason to add the markup.
In 2023, Google deprecated HowTo rich results entirely — first limiting them, then removing the search appearance across desktop and mobile. The schema.org HowTo type still exists and is still valid; what disappeared is the reward — the special Google result. Adding HowTo markup today produces no visual change in Google search.
This was part of a broader Google pullback on rich-result types (FAQ rich results were similarly restricted to authoritative sites around the same time — covered in does FAQ schema still matter). The pattern: Google simplified its results and retired enhancements that were being gamed.
So should you keep or remove it?
If you already have HowTo schema: leave it. It's valid, causes no harm, and remains machine-readable metadata that AI systems and non-Google consumers can still use to recognize step-by-step content. There's no penalty and a small residual benefit.
If you're deciding whether to add it: don't bother for SEO — there's no Google reward anymore. Add it only if you specifically want to label content as procedural for AI/other consumers, and even then, the on-page structure below matters more.
What actually helps now: structure the steps well
Here's the reframe. The value HowTo schema used to add — telling machines "this is a sequence of steps" — is now better delivered by how you write the page, because AI systems extract structure directly from content:
- Number your steps with clear headings ("Step 1: …", or an ordered list).
- One action per step. A step that bundles three actions can't be lifted cleanly.
- Make each step self-contained — understandable without re-reading the previous one.
- Front-load the action verb. "Open Settings → …" beats "You'll want to navigate to…".
Content structured this way gets extracted into AI answers and Google's own snippets regardless of markup — which is exactly why the markup became less necessary. You can score how extractable your steps are with the GEO Content Structure Analyzer.
What to use instead
For instructional pages, the durable choice is:
- Article or BlogPosting schema on the page (see how to add Article schema) for correct attribution and dates.
- Genuinely well-structured steps in the body for extractability.
That combination does more today than HowTo schema does — it's legible to Google, to AI, and to humans.
If you do want HowTo markup anyway
Maybe you're publishing to a platform or ecosystem that still consumes it, or you want the semantic labeling. Our free Article & HowTo Schema Generator produces valid HowTo JSON-LD from a form — enter your steps and it outputs clean, correctly-typed markup with no JSON syntax to fumble. Just go in knowing it won't change your Google appearance; it's semantic metadata, not a rich-result play.
Bottom line
HowTo schema is valid but no longer earns a Google rich result — so keep it if you have it, skip it if you're adding markup purely for SEO, and invest instead in clearly numbered, self-contained steps that any system can extract. If you want the markup for semantic reasons, generate it cleanly; just don't expect a search-appearance boost that Google retired in 2023.