Give your steps a structure AI can read
A free HowTo schema generator, real step-by-step instructions turned into valid JSON-LD, the format AI assistants parse when answering "how do I" questions.
- "How do I..." questions are common AI-assistant queries, and the answer is usually a real sequence of steps.
- HowTo schema states that sequence explicitly, instead of leaving an assistant to infer it from prose.
- Fill in your real steps below, copy the generated code onto the page that actually contains them.
Why prose alone leaves room for guessing
A page can absolutely explain a process well in plain paragraphs, for a human reading top to bottom. An AI assistant answering a "how do I" question is doing something different: pulling out a sequence it can restate as discrete steps. If that sequence only exists as flowing prose, the assistant has to infer where one step ends and the next begins. HowTo schema removes that inference, each step is its own labeled item in the markup, not something to be reconstructed from sentence structure.
This only matters for content that's genuinely a step-by-step process. A single tip, a narrative story, or a general explainer isn't a HowTo, and marking it up as one doesn't add real structure, it just adds schema that doesn't match the page.
Build your HowTo schema
Your HowTo schema
A real rule worth following
Only mark up a page as HowTo if it's genuinely a step-by-step guide. Padding a 3-step process into 7 to look more thorough, or forcing HowTo markup onto a page that's really a general explainer, doesn't make the content more useful to an AI assistant, it just adds structured data that doesn't match what's actually on the page.
Validate your HowTo schema
Already have HowTo JSON-LD on a live page? Paste it here to check it against the fields schema.org actually expects.
FAQ
Does HowTo schema help with AI citations specifically?
It gives an AI assistant an unambiguous, structured version of your steps instead of making it infer a sequence from prose. That doesn't guarantee a citation, but it removes a real source of ambiguity for any "how do I" question your content actually answers.
How many steps should I include?
As many as the real process actually has, no more and no fewer. Padding a 3-step process into 7 steps to look thorough just adds noise; collapsing a genuinely multi-step process into one vague step removes the structure you're trying to add.
Can I use HowTo schema on any page?
Only on pages that are genuinely a step-by-step guide. Don't add HowTo markup to a page that's really just prose with a numbered list for visual style, schema should describe what the content actually is.
Where do I put this code on my site?
Inside the page that actually contains the instructions, wrapped in a <script type="application/ld+json"> tag exactly as generated, one block per real guide, not one block trying to cover your whole site.
