HowTo schema
The HowTo schema is a structured data format from the schema.org vocabulary with which you mark up a step-by-step guide in a machine-readable way. It enables search engines and AI systems to recognize individual steps, required materials, and tools. It makes your instructional content so unambiguous that machines understand it as a process rather than just running text.
Why HowTo schema matters for AI visibility
AI assistants like ChatGPT, Perplexity, or Google AI Overviews answer many questions in the form of instructions: "How do I do X?". This is exactly what the HowTo schema is made for. If you break your guide clearly into steps and mark it up in a machine-readable way, an AI system can grasp your content more easily, reproduce it correctly, and name you as a source. Without structure, the machine has to guess where a step begins and ends. This increases the risk that your guide is summarized incorrectly or not considered at all. Structured data is no ranking magic, but it lowers the barrier to reliably understanding your content, and understandability is the foundation of any citability.
How the HowTo schema works technically
You usually place the markup as JSON-LD, a small script in the page's source code. The basic framework is an object of the type "HowTo" with a name (the task) and a list of "HowToStep" entries. Each step has a text and, optionally, an image or an anchor to the matching spot on the page. You can add required materials ("HowToSupply"), tools ("HowToTool"), total duration, and estimated costs. Important: the marked-up content must exactly match what users actually see on the page. Invented or hidden steps count as a violation of the guidelines and can lead to a devaluation of the structured data.
Common mistakes
The biggest mistake is markup without matching content: you mark something as a guide even though the page shows no real steps at all. A second classic is incomplete steps that lack descriptive text, so that machines see empty shells. Confusing it with the FAQ schema is also common: FAQ is for question-answer pairs, HowTo for an ordered sequence toward a goal. Also note that Google has strongly scaled back the HowTo rich result in classic search. The benefit today lies less in pretty search-result blocks than in better machine readability for AI systems. Always check your markup with a validation tool before you set it live.
Relation to AI recommendations and GEO
Within generative engine optimization (GEO), that is, optimization for AI answers, the HowTo schema is one building block among many. It guarantees no mention, but it gives a language model a clean structure it can orient itself by. When an AI assistant generates a guide and draws on your page as a source, clearly organized, marked-up content helps ensure that steps are taken over correctly and in the right order. What remains decisive, however, is the substance: understandable language, genuine expertise, and topicality. See structured data as an amplifier of good content, not a substitute. Therefore combine the HowTo schema with a clean heading hierarchy and precise, independently citable paragraphs.
Example
A bike shop publishes the guide "Clean your bicycle chain in 5 steps". On the page, each step appears as its own paragraph with a photo: slacken the chain, brush off the dirt, apply cleaner, rinse off, re-oil. In the source code there is a JSON-LD block of the type HowTo with five HowToStep entries, the required tools (brush, cloth), and materials (chain cleaner, oil). If someone asks an AI assistant "How do I clean my bicycle chain?", it can grasp the clearly structured steps and name the shop as a source.
Common questions
Is the HowTo schema still worthwhile even though Google has reduced the rich results?
Yes. Even without the former instructional blocks in classic search, the value remains machine readability: AI systems and crawlers understand your steps more unambiguously. For AI visibility, a clean structure is still helpful, even if it guarantees no placement.
How does the HowTo schema differ from the FAQ schema?
The FAQ schema marks up individual question-answer pairs that stand independently of one another. The HowTo schema describes an ordered sequence of steps with a shared goal. Rule of thumb: if it is about a sequence to achieve a result, you use HowTo, otherwise FAQ.