How to Set Up HowTo Schema Correctly

HowTo schema marks up instructional content so search engines and AI models can extract and present it as a structured, step-by-step guide. When someone asks ChatGPT "how do I implement FAQ schema?" and your page has HowTo schema with clear steps, the AI can extract those steps directly and cite your page as the source. This guide walks through implementing valid HowTo schema — using HowTo schema to teach HowTo schema.

Step 1: Confirm your page is a genuine how-to guide

HowTo schema is for pages where the primary content is step-by-step instructions. Ask yourself:

• Is the page's main purpose to teach someone how to do something?
• Are the steps the central content, not a minor section?
• Would removing the steps make the page lose its primary value?

If yes, use HowTo schema. If the page is an article that includes a numbered list as supporting content, use Article schema instead. Using HowTo on non-instructional pages is a common misuse that Google may penalize.

Step 2: Structure the page with numbered steps as headings

Each step should be a heading with the instructions below:

<h2>Step 1: Identify the questions your audience asks</h2>
<p>Use Google Search Console and People Also Ask to find question-based queries. Select 3-8 questions directly relevant to the page topic.</p>

<h2>Step 2: Write concise question-answer pairs on the page</h2>
<p>Write each question as a heading and each answer as a 40-60 word paragraph. Answers must be factual, self-contained, and quotable.</p>

The visible steps on the page will become the HowToStep entries in your schema. Use the HTML Headings Checker to verify your heading structure.

Step 3: Create the HowTo JSON-LD structure with name and description

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Write FAQ Schema for AI Citations",
  "description": "A step-by-step guide to writing valid FAQ schema that increases your chances of being cited in AI Overviews, ChatGPT, and Perplexity."
}

The name should match the page H1. The description should summarize what the reader will accomplish — this is what AI engines use to determine if your guide answers a user's question.

Step 4: Add a HowToStep for each step on the page

Each step becomes a HowToStep with name (the step heading) and text (the full step instructions). The position property indicates order:

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Write FAQ Schema for AI Citations",
  "description": "A step-by-step guide to writing valid FAQ schema for AI visibility.",
  "step": [
    {
      "@type": "HowToStep",
      "position": 1,
      "name": "Identify the questions your audience asks",
      "text": "Use Google Search Console, People Also Ask, and keyword research tools to find the natural-language questions your audience searches. Select 3-8 questions that are directly relevant to the page topic."
    },
    {
      "@type": "HowToStep",
      "position": 2,
      "name": "Write concise question-answer pairs on the page",
      "text": "Write each question as a heading and each answer as a 40-60 word paragraph directly below it. The answers must be factual, self-contained, and quotable."
    },
    {
      "@type": "HowToStep",
      "position": 3,
      "name": "Create the FAQPage JSON-LD structure",
      "text": "Create a JSON-LD script block with @type FAQPage containing a mainEntity array. Each array item is a Question object with name and acceptedAnswer properties."
    }
  ]
}

Step 5: Add estimatedCost and totalTime if applicable

If your how-to has a known cost and time, add these optional properties:

"estimatedCost": {
  "@type": "MonetaryAmount",
  "currency": "USD",
  "value": "0"
},
"totalTime": "PT30M"

totalTime uses ISO 8601 duration format: PT30M = 30 minutes, PT1H = 1 hour, PT2H30M = 2 hours 30 minutes. These properties are optional but help AI engines provide more complete answers about the task.

Step 6: Validate with Google Rich Results Test or Schema.org Validator

Test the page URL in Google Rich Results Test or Schema.org Validator. The tool will show:

• Whether the HowTo schema is detected
• Any errors or warnings
• Whether the steps are correctly structured

Fix all errors before deployment. Common errors include missing position on steps, step name not matching the on-page heading, and missing text on steps. See schema markup for AI visibility and the technical SEO checklist for the broader context.

Common mistakes

• Using HowTo on non-instructional pages — HowTo is for step-by-step tutorials only. Using it on articles, listicles, or product pages is misuse and can trigger manual actions.
• Step names not matching on-page headings — Each HowToStep name must match the visible heading on the page. Mismatches reduce trust and cause validation warnings.
• Missing the position property — Each HowToStep needs a position integer (1, 2, 3...) to indicate order. Without it, the step order may be ambiguous to search engines.
• Including steps that are not visible on the page — Every step in the schema must appear on the page. Hidden or schema-only steps violate Google guidelines.
• Using HowTo and Article schema together redundantly — A page should use HowTo OR Article, not both, unless the content genuinely serves dual purposes. For most tutorials, HowTo alone is correct. See AEO vs SEO and the glossary for how HowTo schema fits into answer optimization. Explore AEO consulting for a systematic approach.