Google's HowTo rich result is deprecated. The schema.org HowTo type is not. Google no longer shows a How-to appearance in Search, so HowTo markup will not earn you that result. The visible structure of your steps (numbered lists, clear step headings, one action per step) is what you control, and it matters whether or not you keep the JSON-LD.

What changed in 2023

Google announced on August 8, 2023 that How-To rich results would be limited to desktop users. On September 13, 2023 it said the change had been extended to desktop too, which made How-to rich results deprecated [1].

Google's documentation update log later said the How-to structured data documentation was removed because the rich result is no longer shown in search results on desktop or mobile [3]. The same log says the How-to search appearance, the rich result report and Rich Results Test support were to be removed after the deprecation [3]. It also notes that the How-to rich result case study was removed as deprecated [3].

What the vocabulary still is

Two separate things got conflated after the announcement:

ThingStatus
Google's HowTo rich resultDeprecated; no longer shown in Search [3]
Google's How-to structured data documentationRemoved [3]
schema.org HowTo typeStill defined as instructions that explain how to achieve a result by performing a sequence of steps [2]
step property on HowToStill defined; accepts HowToStep, HowToSection, text and other item types [2]

So "HowTo schema deprecated" is accurate for Google Search's rich result and inaccurate if read as "the type is gone." The markup can still describe your content. It just no longer buys a visible Google feature.

Google's structured data guidelines add a related point: markup is only eligible for rich result appearance if it follows Search content policies, and Google may decide a different feature or plain text result is more appropriate [4]. For HowTo there is now no rich result to be eligible for.

Should you keep it?

We can't point to vendor documentation saying that AI answer engines read HowTo markup, or that they ignore it. This article does not claim either. What follows is a decision framework, not a prediction.

Keep existing markup if:

  • Something else you run consumes it: an internal search tool, a content pipeline, a partner feed.
  • It is generated by your CMS template and already matches the visible page.
  • Removing it would cost developer time you would rather spend elsewhere.

Skip adding it to new pages if:

  • You were only adding it for the Google rich result. That result no longer exists [3].
  • You would have to maintain a second copy of the steps that can drift from the page.

Whichever way you go, the markup must match the visible steps. Mismatched markup is the one real risk; it adds nothing and can contradict your own page.

Structure that survives without any markup

The page itself is what any reader, crawler or model sees first. Google's style guidance favors numbered lists for sequences [5]. The rest is general practice:

  • One action per step, starting with a verb.
  • Parallel phrasing across steps ("Open…", "Select…", "Paste…").
  • The goal in the H1 or the first H2, so the task is unambiguous.
  • Prerequisites and tools listed before step 1, not buried in step 4.
  • Expected result stated after the last step.
  • For long procedures, a heading per step with the numbered list or short paragraph beneath it.

For heading mechanics, see H1, H2, H3: How Heading Structure Affects SEO.

Before and after

Before: the steps are bold paragraphs with no list semantics.

<div class="content">
  <p><strong>Step 1:</strong> So first you'll want to go into your settings and find the part about domains.</p>
  <p><strong>Step 2:</strong> Then add your domain, and after that there's a DNS thing you need to do.</p>
  <p><strong>Step 3:</strong> Wait a bit and check that it worked.</p>
</div>

Problems: no heading for the task, "Step 1" is text rather than structure, steps mix several actions, and "a DNS thing" and "a bit" are not extractable facts.

After: a task heading, prerequisites, a real ordered list and a stated result.

<h2>How to connect a custom domain</h2>
<p>Takes about 10 minutes plus DNS propagation. You need admin access and your DNS provider login.</p>

<h3>Before you start</h3>
<ul>
  <li>Admin role on the project</li>
  <li>Access to your DNS provider</li>
</ul>

<h3>Steps</h3>
<ol>
  <li>Open <strong>Settings → Domains</strong>.</li>
  <li>Click <strong>Add domain</strong> and enter <code>www.example.com</code>.</li>
  <li>Copy the CNAME record shown on the screen.</li>
  <li>Create that CNAME record at your DNS provider.</li>
  <li>Return to <strong>Domains</strong> and click <strong>Verify</strong>.</li>
</ol>
<p>When verification succeeds, the domain shows a green "Active" label.</p>

Each step can be lifted out alone and still makes sense. That property is what extraction depends on, with or without schema.

If you keep the JSON-LD

Mirror the visible steps exactly. Same order, same wording or a faithful shortening.

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to connect a custom domain",
  "step": [
    { "@type": "HowToStep", "name": "Open Domains", "text": "Open Settings → Domains." },
    { "@type": "HowToStep", "name": "Add the domain", "text": "Click Add domain and enter www.example.com." },
    { "@type": "HowToStep", "name": "Copy the CNAME", "text": "Copy the CNAME record shown on the screen." },
    { "@type": "HowToStep", "name": "Create the record", "text": "Create that CNAME record at your DNS provider." },
    { "@type": "HowToStep", "name": "Verify", "text": "Return to Domains and click Verify." }
  ]
}

The step property and the HowToStep type are both still defined by schema.org [2]. Validate that the JSON parses, and compare it to the page by eye.

For how HowTo sits alongside Organization, Article and WebPage markup, see Schema.org Markup for AI Search. The same "what does Google still show" question for FAQ markup is covered in FAQPage Schema in 2026.

What to do next

  1. List the pages on your site that carry HowTo JSON-LD.
  2. For each, check that the markup matches the visible steps. Fix or remove any that have drifted.
  3. Rewrite step content that is in paragraphs or "Step 1:" bold text into real ordered lists.
  4. Move prerequisites above the steps and add a one-line expected result below them.
  5. Stop adding HowTo markup purely for Google's old rich result.

The broader checks that sit around this are in the Technical SEO Checklist.