HowTo Schema After Google's Changes

#01What changed, and when?

Google's August 2023 post announced it was limiting How-to rich results to desktop as part of simplifying search results. A 14 September 2023 update said that as of 13 September, Google Search no longer shows How-to rich results on desktop either, so the result type is deprecated. Google said it would drop the How-to search appearance, rich result report and Rich Results Test support after 30 days, and Search Console API support after 180 days (Google). Google's documentation changelog records the removal of the How-to structured data documentation for the same reason (Google).

The later dates are approximate, based on the 30- and 180-day periods Google announced.

#02Is HowTo markup harmful now?

No. In the same post Google said there's no need to proactively remove structured data it no longer uses, because unused structured data doesn't cause problems for Search, though it also has no visible effect (Google).

#03Does anything still use HowTo?

HowTo remains a schema.org type for instructions, with steps, tools, supplies and time (schema.org). Other systems may parse it. We found no public statement from Google, OpenAI, Anthropic or Perplexity that HowTo markup affects AI answers, as of 30 Oct 2026. Google says no special markup is needed for its AI features (Google).

#04What actually helps step-by-step content in AI answers?

Our view: the visible structure of the page. Assistants answering "how do I..." prompts need steps they can follow and quote. That means:

1. State the outcome first. One sentence saying what the reader will achieve and roughly how long it takes.
2. List prerequisites. Accounts, permissions, tools and versions.
3. Use a numbered list. One action per step, starting with a verb.
4. Name exact UI labels. "Settings > Integrations > Slack", not "go to the settings".
5. Show the expected result. What the reader should see after each important step.
6. Cover failure cases. Common errors and how to fix them.
7. Date it. UI changes break instructions; show when the steps were last checked.

Google's people-first guidance asks whether content leaves readers feeling they've learned enough to achieve their goal (Google). Step content that works is the most direct way to meet that.

#05What does a well-structured how-to section look like?

An fictional example for a hypothetical product:

## How do I connect Acme to Slack?

Connect Acme to Slack in about five minutes to get alerts in a channel.
You need Acme admin access and permission to install Slack apps.

1. In Acme, open **Settings > Integrations**.
2. Select **Slack**, then **Connect**.
3. Sign in to Slack and choose the workspace.
4. Pick the channel for alerts and select **Allow**.
5. Back in Acme, select **Send test alert**. A message appears in the channel.

If you see "app not approved", ask a Slack admin to approve Acme.
Last checked: 30 Oct 2026.

#06Should you remove old HowTo markup?

#07Did video or other features replace How-to results?

Google didn't say How-to was replaced by another feature. Our view: tutorial videos with chapters remain a strong format for step content in Google; see Video content, YouTube and AI answers and Google's video SEO guidance.

#08How do you check whether your steps are being used?

Our view: run the task prompts your users ask in the assistants they use, such as "how do I connect Acme to Slack", and note whether the answer follows your steps, cites your page and gets the UI labels right. Record the tool, date and result. If assistants give outdated steps, check whether old versions of your instructions are still live on other URLs, in community forums or in cached help articles, and update or redirect them.

#09How should you maintain step content?

Our view: give every tutorial an owner and tie reviews to product releases. When a UI label changes, update the steps, screenshots and the "last checked" date together. Archive or redirect instructions for retired features rather than leaving them live, because assistants may keep repeating them. A short changelog note on the page helps readers and makes it clear the content is maintained.

#10Checklist

• Don't add HowTo markup for Google
• Remove markup that doesn't match visible steps
• Outcome, prerequisites, numbered steps
• Exact UI labels and expected results
• Error handling and "last checked" date
• Owner and review on each release

#11From MentionX data: how often docs are citedOriginal data

Method. Read-only aggregate queries over MentionX scans from 22 August to 29 October 2026 (UTC): 2,217 engine runs (2,154 completed) across 18 anonymised projects and six engines.

Step-by-step content often lives in docs and how-to articles. In the MentionX sample, articles are the largest cited type and docs a smaller one:

Brand-specific prompts, such as "how do I set up X in this product", mention the brand in every answer:

Our view: for brand-specific how-to questions, engines need accurate steps from somewhere. Clear visible steps on your own docs and articles give them the best source.

Limits. A convenience sample of mostly B2B software projects, run through engine APIs, which can behave differently from the consumer apps. Perplexity, Copilot and DeepSeek figures come from a single day (26 October 2026), so treat them as a snapshot, not a trend.

#12Worked example: Ledgerline rewrites a setup guide

Ledgerline is a fictional accounts-payable tool. Figures are illustrative.

Ledgerline's guide to connecting its app to an accounting system is a long paragraph with HowTo markup added years ago. AI answers to "how do I connect Ledgerline to my accounting system" give outdated steps.

The docs team rewrites it with a one-sentence summary, a list of prerequisites, numbered steps with one action each, the result to expect and a short troubleshooting section. Each step names the exact buttons and fields. It adds screenshots with descriptive alt text and a last updated date.

It leaves the old HowTo markup in place after updating it to match the new steps, since it does no harm, but doesn't add HowTo markup to new pages.

#13How many steps should a how-to have?

As many as the task needs, with one action per step. Our view: if a task needs more than about ten steps, split it into stages with subheadings, such as preparing, connecting and testing. Long, unbroken lists are hard to follow.

#14How do you handle steps that differ by plan or version?

State which plan or version the steps apply to at the top. If steps differ, give separate sections or tabs with the text in the HTML. Don't mix versions in one list. Link to the other versions so readers can find theirs.

#15How should screenshots be used?

Use screenshots to show where things are, not to replace text. Every step should make sense without the image. Add alt text that describes what the screenshot shows. Update screenshots when the interface changes, because outdated images confuse readers.

#16How do you write troubleshooting sections?

List the most common problems after the steps, each with its cause and fix. Use the exact error messages users see. Link to support for anything the guide can't solve.

#17How do you write a good summary sentence?

Start the how-to with one sentence that says what the reader will achieve and roughly how long it takes, such as "Connect Ledgerline to your accounting system in about ten minutes." Engines often quote this sentence for task prompts. Mention prerequisites straight after.

#18How do you test step content?

Follow the steps yourself on a clean account, exactly as written. Note anything unclear or missing. Ask someone unfamiliar with the product to try them. Run task prompts in AI assistants and check whether the steps they give match yours. Our view: steps that fail in testing will also fail when engines repeat them.

#19How do you structure a page with several tasks?

Give each task its own heading and its own numbered list. Add a short contents list at the top. If tasks are independent, consider separate pages so each can be found and cited on its own.

#20How do you link related how-to content?

Link each how-to to the task before and after it, such as setup, configuration and troubleshooting. Link from feature pages to the relevant how-to. Our view: a connected set of task pages helps readers follow a whole process and helps engines find the right page for each step.

#21How do you handle optional steps?

Mark optional steps clearly, such as "Optional:", and say when they're needed. Keep them in the same list if they belong to the same task, or move them to a separate section if they're for a different situation.

#22How do you handle video tutorials?

If you publish a video for a task, put the same steps in text on the page, with timestamps linking to each step. Text steps can be read and cited by engines; video alone is harder to use. Add captions and a transcript. Review the video and the text together whenever the interface changes, so the two stay in step.

#23Common questions

Is HowTo markup harmful now? No. It just doesn't produce rich results in Google Search.

Should we remove HowTo markup? Our view: there's no need if it's accurate. Focus on visible steps instead.

Do numbered lists help AI answers? Our view: clear numbered steps are easier for engines and readers to extract and follow.

#24Related

• FAQPage schema: still worth it?
• Schema markup for AI search