How-To Schema Generator

How-To schema is a specific type of structured data built around Schema.org's HowTo type. It describes a set of instructions for completing a task from start to finish. The markup breaks your content into discrete steps, and optionally includes the tools and materials needed, estimated time to complete, total cost, and images for individual steps.

Search engines use this data to generate rich results that display your steps in an expandable format directly in search results. Instead of a standard blue link with a snippet, searchers see a structured preview of your instructions, sometimes with images, step counts, and time estimates visible before they even click through.

The markup goes in a JSON-LD script tag on the same page as your how-to content. It mirrors what's already on the page in a machine-readable format, giving search engines a structured version of the instructions your visitors are already reading.

When Google renders How-To rich results, they typically appear as an expandable accordion below your page listing. Each step shows its name, and clicking or tapping expands it to reveal the full step description and an image if one is included in the markup.

Some variations display a more visual layout with step images inline, a total time estimate at the top, and a step count like "8 steps." The exact format depends on the query, the device, and how Google's algorithms choose to render results on any given day.

These rich results take up significantly more visual space than a standard listing. That added real estate draws attention and tends to produce higher click-through rates, especially for instructional queries where searchers want to preview the process before committing to a full page visit.

It's worth noting that Google has scaled back How-To rich results on mobile devices in some regions, while continuing to show them on desktop. The availability of rich results can shift over time, but having the schema in place means your content is ready whenever Google decides to display them.

The generator covers all the properties Google recognizes for HowTo rich results, plus additional Schema.org properties that add useful context.

Steps. Each step includes a name (a short title for the step), a text description (the full instruction), and an optional image URL. Steps are ordered sequentially, which is important because search engines display them in the order you define.

Total time. This breaks down into estimated total time to complete the task. The generator formats it as an ISO 8601 duration (like PT30M for 30 minutes or PT2H for two hours), which is the format Schema.org requires. Some tasks also benefit from separating prep time and active time if the distinction matters.

Tools. Any equipment the reader needs to complete the task. A tutorial on patching drywall might list a putty knife, sandpaper, and a mud pan. Each tool gets its own entry with a name and optional URL linking to more information or a product page.

Supplies and materials. Consumable items needed for the task, separate from reusable tools. For a painting tutorial, the paint and painter's tape are supplies while the brush and roller are tools. Making this distinction helps search engines provide more useful previews.

Estimated cost. If completing the task involves spending money, you can include a cost range with a currency code. This shows up in some rich result formats and helps searchers gauge whether the project fits their budget before clicking through.

Each step should describe one distinct action. Resist the urge to combine multiple actions into a single step for the sake of having fewer total steps. Search engines display step names prominently in rich results, and vague or overloaded step titles reduce the value of the preview.

A good step name is specific and actionable. "Sand the surface with 120-grit sandpaper" is better than "Prepare the surface." The name should give someone a clear idea of what they'll do in that step even without reading the full description.

Step descriptions can be longer and more detailed. This is where you include tips, warnings, measurements, and technique details. There's no strict character limit, but keep each description focused on that single step. If you find yourself writing multiple paragraphs for one step, it probably needs to be split into two.

Images on individual steps are optional but valuable. A photo or diagram showing the result of each step helps both searchers previewing your content in search results and visitors following along on your page. If you include step images, make sure they're relevant to that specific step and not just generic stock photos.

Yes, and this is a critical point. Google's structured data guidelines require that your schema markup reflects content that's actually visible on the page. You can't create How-To schema for steps that only exist in the JSON-LD and aren't present in the page content users see.

The text in your step names and descriptions should closely correspond to the headings and instructions on your page. They don't need to be word-for-word identical, but they need to describe the same actions in the same order. If your page has eight steps, your schema should have eight steps. If your page says to bake at 350 degrees, your schema shouldn't say 375.

Google actively checks for mismatches between structured data and page content. Violations can result in manual actions that strip your rich results entirely, and repeated violations can affect your site's eligibility for rich results across all pages.

You can, but you shouldn't. Schema.org has a dedicated Recipe type that includes properties specifically designed for cooking content, like ingredients, nutrition information, cuisine type, cooking method, and yield. Google's recipe rich results are also visually distinct and more feature-rich than How-To results, with dedicated carousels and filtering options.

If your content is a recipe, use Recipe schema. If your content is a general instructional guide that happens to involve food but isn't a recipe in the traditional sense, like "How to Set Up a Charcuterie Board" or "How to Organize Your Pantry," then How-To schema is the right choice.

The general rule is to use the most specific schema type available for your content. Recipe is more specific than HowTo for cooking content, so it should take priority.

Many how-to pages include an FAQ section at the bottom, and you can absolutely have both HowTo and FAQPage schema on the same page. They're separate schema types that describe different sections of your content, and Google can process both independently.

Just make sure each schema block only describes content that's actually present in its corresponding section. Your HowTo schema covers the step-by-step instructions. Your FAQPage schema covers the questions and answers. Don't mix steps into the FAQ or vice versa.

Having both types on one page can increase your chances of earning some form of rich result for a given query, since Google may choose to display either format depending on the searcher's intent and how the results page is composed.

Making each step an entire article. Steps should be concise, focused actions. If your step description runs several paragraphs long, break it into multiple steps. Overly long steps produce cluttered rich results that searchers skip over.

Using vague step names. "Step 1," "Step 2," "Step 3" as step names waste the most visible part of your rich result. Each name should describe the specific action being taken. Searchers scanning the SERP should be able to understand your process just from reading the step names.

Skipping optional properties that add value. Total time, tools, and estimated cost aren't required, but they make your rich results more informative and help your listing stand out. If the information exists in your content, include it in the schema.

Marking up content that isn't instructional. How-To schema is for content that teaches someone to complete a task. It's not appropriate for listicles, opinion pieces, or product roundups, even if they have numbered sections. Google expects genuine step-by-step instructions when it sees HowTo markup.

Forgetting to validate after editing. Any change to your steps, whether adding a new one, reordering them, or updating a description, can introduce syntax errors or structural issues. Run the markup through a JSON-LD validator after every edit to catch problems before they go live.

Not updating schema when page content changes. If you revise your how-to article, add steps, remove steps, or change the process, your schema needs to be updated to match. Stale schema that no longer reflects the page content violates Google's guidelines and puts your rich results at risk.