How to Add HowTo Schema to Step-by-Step Guides

HowTo schema is structured code that tells search engines a page contains a step-by-step guide. It identifies the process being described, the individual steps, and any tools or materials required - in a format that machines can read directly.

Step-by-step guides are among the most useful content types for small business websites. They answer practical questions and build trust with readers who are trying to accomplish something specific. HowTo schema makes this content more accessible to search engines and AI-powered tools by labelling each step explicitly, rather than leaving search engines to infer the structure from the page layout.

This guide explains what HowTo schema includes, how to write it, and how to add it to your website.

For an overview of schema types and how schema markup works, read What is Schema Markup?

When to Use HowTo Schema

HowTo schema is appropriate for pages where the primary content is a step-by-step process - a guide that walks the reader through a series of actions to reach a specific outcome.

Good candidates for HowTo schema include:

• Guides that walk through a technical or practical task step by step
• Tutorial-style articles with numbered steps
• How-to articles where each step produces a distinct outcome

HowTo schema is not appropriate for informational articles that explain a topic without guiding the reader through a process. A page explaining what schema markup is would use Article schema. A page explaining how to add schema markup to a website, step by step, could use HowTo schema.

For content-cluster articles that contain both instructional steps and FAQ sections, HowTo schema can be combined with FAQPage schema in the same page. For guidance on adding FAQ schema, read How to Add FAQ Schema to Your Pages.

What HowTo Schema Includes

HowTo schema uses the HowTo type from Schema.org. The core fields are:

• @type: HowTo
• name: the name of the process - typically the article title
• description: a brief summary of what the guide covers
• step: an array of HowToStep objects, one for each step

Each step includes:

• @type: HowToStep
• name: a short label for the step
• text: the full instruction for that step, as plain text

Optional fields that add useful context:

• tool: tools or software needed to complete the process
• supply: materials or resources required
• totalTime: the estimated time to complete, in ISO 8601 duration format (e.g. PT30M for 30 minutes)

The HowTo Schema Template

Here is a complete HowTo schema template with three steps. Add or remove step blocks to match your guide:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Add Schema Markup to a Web Page",
  "description": "A step-by-step guide to writing JSON-LD schema and adding it to a web page via code injection.",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Write the schema code",
      "text": "Create a JSON-LD script block with the correct schema type and fields for your content. Use the appropriate template for Article, FAQPage, or HowTo schema."
    },
    {
      "@type": "HowToStep",
      "name": "Open the post code injection field",
      "text": "In your CMS, navigate to the individual page or post settings and locate the code injection section. Select the footer field."
    },
    {
      "@type": "HowToStep",
      "name": "Paste and save the schema",
      "text": "Paste the complete schema block, including the opening and closing script tags, into the footer field. Save or update the post."
    }
  ]
}
</script>

Replace the name at the top with the title of your guide. Replace the description with a plain-text summary. For each step, replace the name with a short label and the text with the full instruction.

Writing Step Text for Schema

The text field for each step should contain the complete instruction for that step, written as plain text.

Rules for writing step text:

Plain text only. No HTML tags, no formatting, no links. The text field is read as raw text by search engines. Any HTML included will appear as literal characters.

One step, one action. Each step should describe one discrete action. If a step contains multiple actions, consider splitting it into two steps.

Be specific. Vague step text like "complete the setup" does not help readers or search engines. Write the instruction clearly: "Click the Save button in the top right corner of the editor."

Match the visible content. The step text in the schema should accurately represent the steps visible on the page. They do not need to be word-for-word identical, but significant differences can generate validation warnings.

How to Add HowTo Schema to Ghost

HowTo schema is added through the Ghost post code injection footer, the same as Article and FAQPage schema.

Step 1. Open the post in the Ghost editor.

Step 2. Open post settings and navigate to Code injection.

Step 3. In the footer field, paste the HowTo schema block. If other schema blocks (Article, FAQPage) are already present, paste the HowTo block beneath them as a separate script block.

Step 4. Save or update the post.

Step 5. Validate the schema. Open Google's Rich Results Test, enter the post URL, and check that the HowTo schema is detected without errors. For a full walkthrough of the validation process, read How to Test Schema Markup with Google's Rich Results Test.

Combining HowTo Schema with Article Schema

Most step-by-step guide articles will benefit from both HowTo schema and Article schema on the same page.

Article schema identifies the page as an article with a headline, author, and publisher. HowTo schema identifies the specific process being described and labels each step. They serve different purposes and do not conflict.

Add both as separate JSON-LD script blocks in the post code injection footer. Google's Rich Results Test will detect and validate each block independently.

Building content clusters around how-to guides? For guidance on planning those articles, read How to Build a Content Cluster Step by Step.

Common Mistakes

Using HowTo schema on non-instructional content. HowTo schema is only appropriate for pages with a genuine step-by-step process. Using it on an informational article that does not guide the reader through discrete steps may result in the schema being ignored.

Including HTML in step text. The text field must be plain text. Any HTML tags in the field will be read as literal characters, which breaks the structured data.

Numbering steps in the text field. The steps are already ordered by their position in the array. Do not add "Step 1:", "Step 2:" to the text field - this creates redundancy in the schema and can look odd if search engines display the steps in a numbered format.

Steps that do not match the page. If the guide is updated and steps are changed, the schema must be updated to match. Schema that no longer reflects the page content is inaccurate.

Not validating after adding. HowTo schema has a specific structure that must be formatted precisely. Always run the page through Google's Rich Results Test after adding the schema to confirm it is valid.

Frequently Asked Questions

Can HowTo schema be used alongside Article and FAQ schema on the same page? Yes. All three can be present as separate JSON-LD script blocks in the footer. A step-by-step guide article with a FAQ section could legitimately use all three. Google's Rich Results Test will validate each block independently.

How many steps should a HowTo schema include? Include a step for every step in the guide. There is no minimum or maximum. A guide with three steps should have three step blocks. A guide with ten steps should have ten.

Does HowTo schema directly improve search rankings? No. Like other schema types, HowTo schema does not directly affect rankings. It helps search engines understand the content structure and makes the page eligible for rich result appearances in Google search, such as the expandable step format that can appear for how-to queries.

What is the ISO 8601 format for the totalTime field? ISO 8601 duration format uses the prefix PT for time durations. PT15M means 15 minutes. PT1H means 1 hour. PT1H30M means 1 hour and 30 minutes. This field is optional - only include it if you have a reliable estimate of how long the process takes.

Should every step-by-step article use HowTo schema? It is good practice for any article where the primary content is a step-by-step process. If the article is primarily informational - explaining a concept rather than guiding through a process - Article schema is more appropriate. Use HowTo schema when each section of the article represents a distinct action the reader takes.

Summary

HowTo schema marks a page as containing a step-by-step process, identifying each step individually so search engines can read the guide structure directly.

Use it on articles where the primary content guides the reader through a series of discrete actions. Do not use it on informational articles that explain a topic without a process structure.

Write step text as plain text only - no HTML. Each step should describe one action clearly and match what is visible on the page.

On Ghost, add the HowTo schema block to the post code injection footer. If Article or FAQPage schema is already there, add the HowTo block as a separate script block beneath them.

Validate the schema using Google's Rich Results Test after adding it.

For guidance on the other schema types used alongside HowTo schema, read How to Add FAQ Schema to Your Pages and What is Schema Markup?