HowTo Schema Generator

What HowTo markup does now that Google has retired the rich result

HowTo is a schema.org type that describes an ordered sequence of steps for completing a task. It produces no rich result in Google and has not since 2023: Google announced the deprecation on 8 August 2023, stopped showing How-to results on desktop on 13 September 2023, and then removed the HowTo structured data page from its Search Central documentation altogether. There is no Google search feature to win here, and there has not been one for three years — treat any generator that still promises you a numbered step carousel as out of date.

The type itself is untouched by that. Schema.org still defines HowTo and HowToStep, the markup is still valid, and serving it costs nothing and risks nothing. Where it earns its place now is with everything that is not Google's rich result renderer: Bing, other search engines, and the retrieval crawlers behind AI answer engines, which lift a clean ordered list of instructions far more reliably from positioned HowToStep nodes than from prose. This generator outputs a HowTo node with a name, optional description and totalTime, and a step array of HowToStep items each carrying position, name, text and an optional image — the fields schema.org defines for the type.

When to use it

Use it for any content that is genuinely a sequence of steps: software setup guides, recipes without ingredient quantities (schema.org has a separate Recipe type for those), assembly instructions, troubleshooting walkthroughs, or internal runbooks you're publishing externally. Each step should be a discrete, independently completable action — if a "step" is really three actions bundled together, split it, since the machine consumers that still read this markup reward granularity.

Budget for it accordingly: with no Google rich result on the other end, HowTo markup is worth adding when you already have clean, ordered steps and want them machine-readable, not as an SEO task you schedule ahead of writing the steps themselves. Skip it for content that's advice or explanation rather than an ordered procedure; forcing narrative content into HowToStep nodes produces awkward, low-quality markup that helps nobody.

Example

For "How to Reset a Forgotten WordPress Admin Password," set totalTime to 10 minutes and add three steps: "Open phpMyAdmin" with text "Log into your hosting control panel and open phpMyAdmin for your site's database," "Find the users table" with text "Navigate to the wp_users table and locate your admin row," and "Update the password field" with text "Click Edit, paste a new MD5-hashed value into user_pass, and save." The generator produces a HowTo schema with three positioned HowToStep entries, ready to paste into the article's <head>.