HowTo Schema

Written by Cobus van der Westhuizen, reviewed by Wynand van der Westhuizen, fact-checked by Lenata Oosthuizen. Last reviewed July 2026. Editorial policy.

What Is HowTo Schema?

HowTo schema is a structured data markup type from the Schema.org vocabulary that tells Google a page describes a step-by-step process for accomplishing a specific task. When implemented correctly, it can trigger a HowTo rich result in Google Search, which displays the individual steps of the process directly in the SERP, often alongside optional images for each step. This is particularly valuable for "how to" queries, which consistently represent some of the highest-volume informational searches across South African Google search.

The markup is applied using JSON-LD and follows the Schema.org HowTo specification. The key properties include the overall name of the how-to process, an optional description, the estimated time to complete, optional tools and supplies required, and the individual steps. Each step is a HowToStep entity with its own name and text description. Steps can also include images, which Google may display in the rich result carousel on mobile search results.

For South African businesses, HowTo schema is most applicable to tutorial-style blog posts, help centre articles, and any service page that walks a potential customer through a process. A financial services company explaining how to apply for a home loan in South Africa, a legal firm detailing how to register a company with CIPC, or a digital marketing agency explaining how to set up Google Analytics on a website all have content that qualifies for HowTo schema. The structured data signals to Google that the page is well-organised and instructional, which can improve its extractability for both traditional search results and AI-generated answers.

HowTo Schema In Practice

The scenario below is an illustrative example, not a Juicy Designs client result. It indicates the kind of effect that HowTo schema work typically produces, so treat it as indicative rather than measured.

Imagine a Pretoria-based digital marketing agency that publishes a blog post titled "How to Set Up Google Search Console for Your South African Business Website". The article walks through five clear steps: creating a Google account, adding a property, verifying site ownership, submitting the sitemap, and reviewing the initial coverage report. Each step is written as a distinct paragraph with a clear heading and a practical screenshot.

The team then adds HowTo schema to the page, mapping each of the five steps to a HowToStep entity with the step name and description, and includes optional image URLs from the existing screenshots. Once Google recrawls the page, a how-to rich result could plausibly begin appearing for searches like "how to add a website to Google Search Console" and related queries. On mobile devices, the five steps might appear in a card format below the standard search listing, which would typically expand the page's SERP footprint and could lift the number of clicks from South African users setting up their first Search Console account. Whether and how the rich result displays is up to Google, and its handling of HowTo results has changed over time.

What HowTo schema is

HowTo schema is a type of structured data (schema.org markup, typically in JSON-LD) that identifies content as a set of step-by-step instructions for accomplishing a task, telling search engines that the content is a how-to guide with a sequence of steps, so that it can be understood and, where eligible, displayed as an enhanced result. By marking up a how-to guide with HowTo schema, a business tells search engines the structure of the instructions, the task, the steps in order, and optionally the tools, materials, time and images, which helps search engines understand the content and can, in some cases, enable a richer presentation of the steps in search results. HowTo schema is one of several content-specific structured-data types (alongside FAQ schema for question-answer content, and others) that convey the nature and structure of content to search engines. It suits genuine step-by-step instructional content, guides that walk the user through completing a task in ordered steps, and it should only be used where the content genuinely is such a how-to guide, since structured data should accurately reflect the content. It is worth noting that Google has changed how it displays various structured-data rich results over time, so the specific search appearance of HowTo (and other) markup can vary and evolve, and the value of the markup includes helping search engines understand the content as well as any rich-result display. Understanding HowTo schema matters because, for genuine step-by-step instructional content, marking it up with HowTo schema helps search engines understand its structure and can support enhanced presentation, so knowing what HowTo schema is, structured data marking content as step-by-step instructions, helps a business use the appropriate schema for its how-to content, as part of using structured data to help search engines understand its pages.

Using HowTo schema versus other schema

Using HowTo schema correctly means applying it to genuine step-by-step instructional content and choosing the right schema type for the content in question, since different structured-data types suit different content, and the markup should accurately reflect what the content is. HowTo schema is for content that genuinely provides step-by-step instructions to accomplish a task, a guide that walks the user through ordered steps, so it should be used on such how-to guides, marking up the task and its sequence of steps (and optionally tools, materials, time and step images), and not on content that is not genuinely step-by-step instructions. This distinguishes it from other schema types: FAQ schema (FAQPage) is for content presenting a list of questions and their answers, so it suits genuine FAQ content, whereas HowTo schema suits step-by-step task instructions, so the choice between HowTo and FAQ schema depends on whether the content is a set of question-answers (FAQ) or a sequence of instructional steps (HowTo), and each should be used on the content type it accurately describes rather than interchangeably. Using the schema type that genuinely matches the content is important, since structured data must accurately reflect the content, and misapplying a schema type (marking content as something it is not) is against structured-data guidelines and can cause problems. On the practical value and display: HowTo schema helps search engines understand the content's structure, and can, where eligible, support an enhanced presentation, though Google's display of HowTo and other rich results varies and has changed over time, so the search appearance may differ across contexts and evolve, and the markup's value includes the understanding it provides as well as any rich-result display. On mobile and regional behaviour, structured-data rich results and their display can differ by device and can change over time, so the specific appearance of HowTo markup on mobile search (in South Africa or elsewhere) depends on Google's current handling, which evolves, meaning the practical guidance is to implement accurate HowTo schema on genuine how-to content for the understanding and potential enhancement it provides, while recognising that the exact rich-result display is determined by Google and can vary and change. For a South African business, using HowTo schema means adding it to genuine step-by-step instructional content (how-to guides), accurately marking up the task and steps, and choosing HowTo schema for step-by-step content versus FAQ schema for question-answer content, so the right schema accurately describes each piece of content. Because structured data helps search engines understand content and can support enhanced results, using HowTo schema appropriately on genuine how-to content, alongside other suitable schema types for other content, is a sound part of using structured data well, provided it is applied accurately to the content it genuinely describes, which is the key principle in choosing and using HowTo schema.

FAQ